Xbox series elite 2[Controller Request]:

[THEKINGFIGTHER]

Xbox series elite 2[Controller Request]:

[ndeadly]

This controller is already supported. If you can't connect it then one of these things is likely true:

• you have the updated Bluetooth LE firmware and need to downgrade to a legacy version
• you have a newer XBE2 model that shipped with the Bluetooth LE firmware and cannot be downgraded
• you haven't installed Mission Control correctly and are missing the binary patches that specifically enable this controller
• you haven't correctly followed the procedure for either installing Mission Control or pairing controllers

[THEKINGFIGTHER]

Excuse me, could you show me how to install the binary files for mission control since I searched and no one has used that control on the Nintendo switch El vie, 12 de abr de 2024 12:20 a. m., ndeadly ***@***.***> escribió:

…

This controller is already supported. If you can't connect it then one of these things is likely true: - you have the updated Bluetooth LE firmware and need to downgrade to a legacy version - you have a newer XBE2 model that shipped with the Bluetooth LE firmware and *cannot* be downgraded - you haven't installed Mission Control correctly and are missing the binary patches that specifically enable this controller - you haven't correctly followed the procedure for either installing Mission Control or pairing controllers — Reply to this email directly, view it on GitHub <#804 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHYFIK53A6YI3OM5TTY33GTY454JJAVCNFSM6AAAAABGCWWA36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGA3DENRZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ndeadly]

https://github.com/ndeadly/MissionControl?tab=readme-ov-file#installation

[THEKINGFIGTHER]

Thanks, I'll check it out! , Another question, are not all control motors compatible? I mean, only some of them work El vie, 12 de abr de 2024 12:47 a. m., ndeadly ***@***.***> escribió:

…

https://github.com/ndeadly/MissionControl?tab=readme-ov-file#installation — Reply to this email directly, view it on GitHub <#804 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHYFIK2O3MRR4JAXPUYMTGLY457QLAVCNFSM6AAAAABGCWWA36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGA4TOMZXG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ndeadly]

The issue tracker is not really the place for questions. In the future, direct questions to the discussions page, or discord.

Vibration motor support is only really implemented for major console console controllers, because they tend to be well understood and documented. Support for arbitrary controllers is possible, but people don't often provide me with the information to implement it. Output packets can't simply be observed on the console like we can for input data. One needs to make a packet capture of the vibration working on PC, or grab an HID descriptor in order to know the layout of the output data.

[THEKINGFIGTHER]

Ok, thanks for the clarification. El vie, 12 de abr de 2024 1:57 a. m., ndeadly ***@***.***> escribió:

…

The issue tracker is not really the place for questions. In the future, direct questions to the discussions page, or discord. Vibration motor support is only really implemented for major console console controllers, because they tend to be well understood and documented. Support for arbitrary controllers is possible, but people don't often provide me with the information to implement it. Output packets can't simply be observed on the console like we can for input data. One needs to make a packet capture of the vibration working on PC, or grab an HID descriptor in order to know the layout of the output data. — Reply to this email directly, view it on GitHub <#804 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHYFIK2CG2RL5P4E3VTZZFLY46HYJAVCNFSM6AAAAABGCWWA36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGIZDAOJVGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>