Input: Difference between revisions

From Unreal Tournament 2004 MiA Wiki
No edit summary
mNo edit summary
Line 15: Line 15:
Notes:
Notes:


StartupBorderless - is intended to make the game open up a borderless window. It doesn't appear to do so.
* StartupBorderless - is intended to make the game open up a borderless window. It doesn't appear to do so.
InhibitWindowsHotkeys - does not appear to do anything. Intended to stop alt-escape. alt-tab, ctrl-escape and ctrl-tab from operating when full screen?


WinPosX and WinPosY - where to open a windowed screen
* InhibitWindowsHotkeys - does not appear to do anything. Intended to stop alt-escape. alt-tab, ctrl-escape and ctrl-tab from operating when full screen?
Console command "SAVESCREENPOS" sets WinPosX and WinPosY to where the window is.
 
* WinPosX and WinPosY - where to open a windowed screen - however this does not appear to work.
 
Console command "SAVESCREENPOS" sets WinPosX and WinPosY to where the window is - however you do not appear to be able to move a window any longer

Revision as of 22:42, 15 March 2026

If command line contains safe, UseRawHIDInput and UseDirectInput are turned off

In UnrealEd, and UseDirectInput is set, it will switch to RawHIDInput for the session - but only if EnableEditorRawHIDInput is set. Otherwise it will drop to legacy input modes as noted below.


Input system priority:

  1. UseRawHIDInput wins if set. You get Windows Raw Input- unfiltered device input directly from hardware.
    • RawEnhancedPointerPrecision - enables (True)/disables (False) mouse acceleration using Windows EPP - see EPPCustomCurvePoints
  2. UseDirectInput is next priority. You get Windows DirectInput from DirectX 8
    • DirectEnhancedPointerPrecision - enables (True)/disables (False) mouse acceleration using Windows EPP - see EPPCustomCurvePoints
  3. If UseLegacyCursorInput is set then drops to a Legacy Win32 Input Handler
  4. Otherwise, the game uses a Windows Win32 Input Handler

Notes:

  • StartupBorderless - is intended to make the game open up a borderless window. It doesn't appear to do so.
  • InhibitWindowsHotkeys - does not appear to do anything. Intended to stop alt-escape. alt-tab, ctrl-escape and ctrl-tab from operating when full screen?
  • WinPosX and WinPosY - where to open a windowed screen - however this does not appear to work.

Console command "SAVESCREENPOS" sets WinPosX and WinPosY to where the window is - however you do not appear to be able to move a window any longer