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
{{ message }}
This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
When using XCI on a Windows web build, getting trigger input with multiple controllers plugged in will not work properly. What might happen is that trigger input will go though only if all triggers on all controllers are pressed down, but your mileage may vary.
The reason this is a limitation and not a bug is because of the way Microsoft implemented DirectInput. It severely limits trigger input on Windows.
XInput is usually seen as the solution to this problem, except it won't work for web builds. XInput is already implemented for native builds because native builds support plugins while web players don't.
The good news is that having one controller plugged in doesn't seem to have any issues with any input, including triggers.
The text was updated successfully, but these errors were encountered:
When using XCI on a Windows web build, getting trigger input with multiple controllers plugged in will not work properly. What might happen is that trigger input will go though only if all triggers on all controllers are pressed down, but your mileage may vary.
The reason this is a limitation and not a bug is because of the way Microsoft implemented DirectInput. It severely limits trigger input on Windows.
XInput is usually seen as the solution to this problem, except it won't work for web builds. XInput is already implemented for native builds because native builds support plugins while web players don't.
The good news is that having one controller plugged in doesn't seem to have any issues with any input, including triggers.
The text was updated successfully, but these errors were encountered: