Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offer Xidi for XInput->DirectInput fixes #336

Open
BinToss opened this issue Aug 10, 2022 · 0 comments
Open

Offer Xidi for XInput->DirectInput fixes #336

BinToss opened this issue Aug 10, 2022 · 0 comments

Comments

@BinToss
Copy link
Member

BinToss commented Aug 10, 2022

https://docs.microsoft.com/en-us/windows/win32/xinput/xinput-and-directinput#using-the-xbox-controller-with-directinput
https://github.com/samuelgr/Xidi

Ideally, players should be able to do the following with any controller—not just those which predate Windows Vista. This is not the case when using an XInput controller e.g. anything made during or after the Xbox 360 era.

Xidi solves this by replacing Windows' built-in XInput-DInput wrapper when loaded into an application. It provides multiple control scheme presets and even allows custom mappings.

Linux Compatibility

Wine's input wrapper behaves the same as Microsoft's XI->DI wrapper. Very disappointing.
JediMasterChief found that this can be remedied via Steam Input

I can look into it. I have a 360 controller I can test with.

My Dualsense worked out of the box, though its triggers had a similar issue. I was able to work around it by adding the exe to Steam as a non-Steam game and using Steam Input to change the triggers to the Start and Back buttons. It still runs through wine, since I did not force it to use Proton.

I guess that works for Linux players, but a more universal solution would be preferable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant