-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support outputs #6
Comments
I assume by "output support" you mean the ability to have a host PC send status/information back through USB to a JoystickXL device which can than be used to drive LEDs, etc. I believe this requires custom drivers for the operating system as well as support for the device within the application - the LCD info display on the Logitech X52 is a good example. This is beyond my current programming knowledge (and time constraints) at the moment, so will likely not end up in JoystickXL any time soon. That being said, if you have any specific information/links on how this can be accomplished, I would be happy to have a look and possibly re-evaluate. Depending on the application you're trying to get feedback from, there may be other ways to get real-time status. Microsoft Flight Simulator has the SimConnect API, and Elite Dangerous has the Player Journal. I have personally used E:D's player journal (see EDMC-Telemetry) to relay in-game status to a Raspberry Pi that controls RGB LEDs and a couple of 1.8" LCD displays built into a custom controller that uses JoystickXL (through a separate CircuitPython board) to send input to the game. |
Honestly, I was just hoping to get player number LEDs to work. There's also a haptics one, which could map to rumble. |
The player number LEDs would be really handy and shouldn't require any custom drivers, though I imagine the game in question would still have to support them. I'm not sure how soon I'll have a chance to look at it, but I'll definitely put it on the list of potential enhancements. |
It would be cool to have output support, like LEDs or speakers for status.
The text was updated successfully, but these errors were encountered: