|
PS5 Dualsense controller (drifting?) problem in machine selection (aka main) screen.
#391749 - 08/29/21 07:09 PM
|
|
|
Hi there.
I'm writing because I'm experienced some kind of drifting problem, whenever I plug my Dualsense controller, but only in the machine selection portion of MAMEUI.
The list of games keeps scrolling by itself if the controller was connected previously of running MAMEUI (if the controller is connected after, the problem is not present). I just bought a second controller to verify that the first one wasn't broken, but the problem is still there.
Does anyone have encountered this problem; and if so, do you know how to fix it?
Finally, I wanted to say that this doesn't happen with other controllers such as the Dual Shock 4, or the XBox Elite controller 2. I'm using Windows 10 Pro, MAMEUI 0.235 by the way.
|
|
|
|
Re: PS5 Dualsense controller (drifting?) problem in machine selection (aka main) screen.
[Re: The Cimmerian]
#391855 - 09/12/21 02:10 PM
|
|
|
> Hi there. > > I'm writing because I'm experienced some kind of drifting problem, whenever I plug my > Dualsense controller, but only in the machine selection portion of MAMEUI. > > The list of games keeps scrolling by itself if the controller was connected > previously of running MAMEUI (if the controller is connected after, the problem is > not present). I just bought a second controller to verify that the first one wasn't > broken, but the problem is still there. > > Does anyone have encountered this problem; and if so, do you know how to fix it? > > Finally, I wanted to say that this doesn't happen with other controllers such as the > Dual Shock 4, or the XBox Elite controller 2. I'm using Windows 10 Pro, MAMEUI 0.235 > by the way.
I"m not sure if this is the same issue, but I'm running an old DualShock 3 with some 3rd party drivers and I ended up turning off the axes for the internal motion controls as it was causing input setup issues with emulators (i.e., I couldn't ever get it perfectly flat - not sure if it was me or a driver issue).
The other issue would be setting up the deadzone for the axes (i.e., the % between pushing the stick and the application actually picking up the input).
|
|
|
|