You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even if custom ranges for the axes are set, the raw (HID) values that are reported seem to be still in the fixed range of -32767 to 32767. This is sometimes problematic for software that works with raw values directly and not with DirectX normalized ranges... For example, some games using the Unity default input handler get confused with the negative part of the range. I realize that those issues should be better fixed on the game side, but it is not likely... Moreover, it sometimes affects Windows calibration, as it also works with raw values.
Could we have an option that the raw values are reported in the range that is set for the axis? For example, if I set the X axis range to 0 65535, that is exactly what is reported in raw values?
The text was updated successfully, but these errors were encountered:
Alternately, the default reported range could be changed from -32767 to +32767 to the default DirectX range 0 to 65535, that way there would be no discrepancy between raw reported values and the system values. As per the HID specification:
'Traditionally, a joystick driver applies its own scaling to values returned from a joystick. That is, the driver simply linearizes and translates the range of values generated by the stick into normalized values between 0 and 64K, where 32K is centered. The application (game) then interprets the normalized values as necessary'.
That is why some games will have problems with HID reports which have axes in negative values.
Even if custom ranges for the axes are set, the raw (HID) values that are reported seem to be still in the fixed range of -32767 to 32767. This is sometimes problematic for software that works with raw values directly and not with DirectX normalized ranges... For example, some games using the Unity default input handler get confused with the negative part of the range. I realize that those issues should be better fixed on the game side, but it is not likely... Moreover, it sometimes affects Windows calibration, as it also works with raw values.
Could we have an option that the raw values are reported in the range that is set for the axis? For example, if I set the X axis range to 0 65535, that is exactly what is reported in raw values?
The text was updated successfully, but these errors were encountered: