BigShane Posted September 17 Share Posted September 17 I'm having an issue with BigBox/LaunchBox both will stop responding to my bluetooth controller after launching Xenia. Even if I close Xenia, I have to power cycle controller to get it working again. Anyone seen this problem before? Quote Link to comment Share on other sites More sharing options...
BigShane Posted September 17 Author Share Posted September 17 (edited) After more research, I found the below forum post that appears to be my issue, I made a post in it, but someone deleted it for some reason. The issue appears to be a launchbox controller support issue and not an Xenia issue. Since launchbox does not support SDL2, any modern bluetooth controller will stop functioning in launchbox if an emulator switches it to enhanced mode until you power cycle the controller. There should be at least some note about this somewhere as I spent several hours troubleshooting this issue. The controller I'm using and bought for launchbox is an 8Bitdo Ultimate Bluetooth controller. https://forums.launchbox-app.com/topic/75716-big-box-dualshock-4-issue/ Edited September 17 by BigShane Quote Link to comment Share on other sites More sharing options...
Sbaby Posted September 17 Share Posted September 17 I confirm that I had a similar problem with the active configuration of SDL2 on an earlier version of PCSX2, now I have disabled the SDL2 in PCSX2 and I am using with xinput, for me nothing changes and so I don't know if this problem has been solved, however it would be useful to investigate this for a use of the new excellent SDL2 driver for controllers Quote Link to comment Share on other sites More sharing options...
JoeViking245 Posted September 17 Share Posted September 17 1 hour ago, Sbaby said: I confirm that I had a similar problem with the active configuration of SDL2 on an earlier version of PCSX2, now I have disabled the SDL2 in PCSX2 and I am using with xinput, for me nothing changes and so I don't know if this problem has been solved, however it would be useful to investigate this for a use of the new excellent SDL2 driver for controllers I couldn't catch if you were saying switching the emulator to use xinput resolved the issue. Or you tried it, and it didn't work. If that did work, one can do the same thing with Xenia. Edit "xenia.config.toml" with any text editor. Look for the section [HID] Below that, change hid = "any" to hid = "xinput" And if I misunderstood, never mind. 😊 Quote Link to comment Share on other sites More sharing options...
Sbaby Posted September 17 Share Posted September 17 27 minutes ago, JoeViking245 said: I couldn't catch if you were saying switching the emulator to use xinput resolved the issue. Or you tried it, and it didn't work. If that did work, one can do the same thing with Xenia. Edit "xenia.config.toml" with any text editor. Look for the section [HID] Below that, change hid = "any" to hid = "xinput" And if I misunderstood, never mind. 😊 Hi @JoeViking245 😉 I just wanted to clarify that I don't have any issues myself because I've configured all my emulators to use XInput, including PCSX2 and Xenia, exactly as you mentioned. I only stepped in to try and help the user, and if they manage, they could consider switching to XInput by disabling SDL2. Additionally, I wanted to share something I've experienced: when I leave SDL2 enabled, my controllers work fine when launching the emulators directly, but if I launch them through LaunchBox, some conflict arises and the game doesn’t run properly. I hope this information will be useful to others and to the Launchbox team as well, in any case I have no problem with it, at least in this context 😅 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.