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

T16000M users having problems #88

Open
arithex opened this issue Jan 16, 2023 · 1 comment
Open

T16000M users having problems #88

arithex opened this issue Jan 16, 2023 · 1 comment

Comments

@arithex
Copy link
Collaborator

arithex commented Jan 16, 2023

Looking at the code, I think we select Stock xml templates based on the product-string, never the GUID (the PID/VID).

I'm seeing a lot of problems from Thrustmaster T.16000M hotas combo users... one of their DeviceSorting.txt files says:

{B687044F-0000-0000-0000-504944564944} "TWCS Throttle"
{B10A044F-0000-0000-0000-504944564944} "T16000M"

I note, the throttle is top line and the stick is second.

I think this happens because "TWCS Throttle" has a stock xml match .. but "T16000M" doesn't. (The stock xml file is named "T.16000M".)

I don't know if Thrustmaster changed their product-id string at some point.. eg. in a firmware update or minor hardware update.

I also don't fully understand why having these out of order is causing so many problems .. but maybe that is a different issue.

@arithex
Copy link
Collaborator Author

arithex commented Jan 16, 2023

Workaround might be as simple as copying the stock xml file (or hardcoding a little lookup-table of aliases)...

I have an older T.16000M stick (only) and it enumerates as
{B10A044F-0000-0000-0000-504944564944} "T.16000M Joystick"

That's a 3rd name for the same PID/VID product-GUID, B10A044F. :\

But a better solution might be to key off the product-GUID instead of product-name. Are there known cases where different devices identify as same product-GUID but have physically different button layouts? (I think VKB Gladiator NXT standard-vs-premium might be such a case. Not 100% sure about that tho.)

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