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
I was just wondering.. While there are a number of limitations and expectations by the DInput and WinMM, is there not a thing that certain axes supported by these API's are treated with different expectations, namely Sliders ? (or rudders and/or maybe other types of analog inputs that I might've never heard of.. )
With this in mind, is there a possibility that we could have an additional predefined Controller Mapping where the Triggers of the XInput compatible device would translate into "Slider 1" and "Slider 2" respectively and DInput/WinMM would have expectations from these type of axes to be reporting a value of zero by default ?
I know I had been using "XInput Plus" for a couple of years with "ToCa Race Driver 3" as one example, where I've been using such a setup for the Triggers. While I understand that the game itself might have expectations of extreme value/s being reported as default axes states, I can't help but wonder if this is just a game specific thing, or are the Sliders "axes" (?) treated different at API level by DInput or WinMM.. ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I was just wondering.. While there are a number of limitations and expectations by the DInput and WinMM, is there not a thing that certain axes supported by these API's are treated with different expectations, namely Sliders ? (or rudders and/or maybe other types of analog inputs that I might've never heard of.. )
With this in mind, is there a possibility that we could have an additional predefined Controller Mapping where the Triggers of the XInput compatible device would translate into "Slider 1" and "Slider 2" respectively and DInput/WinMM would have expectations from these type of axes to be reporting a value of zero by default ?
I know I had been using "XInput Plus" for a couple of years with "ToCa Race Driver 3" as one example, where I've been using such a setup for the Triggers. While I understand that the game itself might have expectations of extreme value/s being reported as default axes states, I can't help but wonder if this is just a game specific thing, or are the Sliders "axes" (?) treated different at API level by DInput or WinMM.. ?
Cheers!
And a Happy New Year!..
Beta Was this translation helpful? Give feedback.
All reactions