snaketus

Hello. I know this is a five-year-old thread, but I just experienced this or something very similar today with Retroarch. My Dualshock 4, connected via Bluetooth as a D-input controller, suddenly gave me this message constantly: "Dualshock 4 configured in port 1." I tried everything in the last couple of hours, and it just kept saying that. Then I finally disabled Bluetooth in Windows settings completely and connected the controller via USB, and the message spam was gone. Okay, I re-enabled Bluetooth, and the message spam was on again when connecting the Dualshock 4 via Bluetooth. Then I noticed something weird flashing on my Bluetooth devices list. My Davinci Resolve Speed Editor keyboard constantly connected and disconnected via Bluetooth. Which is weird because I haven't even used it on this computer for almost a year. It's been connected to my editing PC in another room. I removed it, and finally, the message spam in Retroarch went away, and everything is working normally again. So, if you experience this with a Bluetooth controller, check if something else is behaving weirdly with your Bluetooth connection. Now, I'm just wondering why my Speed editor keyboard suddenly connected to this PC in my living room while I was playing a game.

So, I just dived into these 3D boxes and noticed the same thing! DualShock 4's right stick isn't recognized at all! This is almost three years later, and it still isn't fixed/implemented. Yeah, most people probably use just Xbox controllers, but many people prefer to use something else, and something else should work as well. I think it has something to do with DS4 being a Dinput device instead of an Xinput device, and Launchbox/Big Box just doesn't see it as a dual analog stick controller. Every other button works just fine, just not the right analog stick. I know I could just use something like DS4Windows, but I don't want to because I don't need it anymore on my system for anything else! DS4 just works with almost everything just as it is these days, except rotating boxes in Big Box. I guess I will just bind it to the left stick for now as a workaround, as someone else in this thread did. It's not a final solution, though.