Dualshock 4 crash
Started by FaustianFrontrunner




6 posts in this topic
FaustianFrontrunner
Member


0
2 posts 2 threads Joined: Aug 2020
08-14-2020, 04:38 PM -
#1
So I am attempting to connect my Dualshock 4 controller to my computer for usage with RPCS3 and I'm getting the Fatal error when I go to switch my controller- can anyone make some sense of this and let me know what I need to do to repair it? 






[Image: Error.png]
Ani
Administrator
*******


16
4,386 posts 106 threads Joined: Aug 2017
08-16-2020, 04:04 PM -
#2
This usually happens when you're using a bad cable that can't properly transmit data, or when you have third party input tools interfering with input
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux
Gamester
Member


0
10 posts 2 threads Joined: Dec 2018
08-17-2020, 04:21 AM -
#3
I suggest doing what I did and ditch the old DS3 program and use the ScpToolkit application instead to connect your PS4 Controller via Blutooth to your PC and then just use the Xinput setting within the RPCS3 Gamepad Device settings instead.
Ani
Administrator
*******


16
4,386 posts 106 threads Joined: Aug 2017
08-18-2020, 10:23 PM -
#4
That's also tremendously wrong. There are native DualShock 3 and DualShock 4 input handlers, do not use third party 'map to XInput' tools.
This post was last modified: 08-18-2020, 10:23 PM by Ani.
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux
Gamester
Member


0
10 posts 2 threads Joined: Dec 2018
08-18-2020, 10:57 PM -
#5
(08-18-2020, 10:23 PM)Ani Wrote: That's also tremendously wrong. There are native DualShock 3 and DualShock 4 input handlers, do not use third party 'map to XInput' tools.

Odd, I've always used the Xinput option and have never had any controller issues yet.
Ani
Administrator
*******


16
4,386 posts 106 threads Joined: Aug 2017
08-19-2020, 04:27 PM -
#6
The XInput option is for other controllers. There's a reason why we implemented native handlers. For one, you won't have any SIXAXIS support if not using the native handlers. Also it doesn't make any sense to go the worst path when there's literally a native option.
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux
Gamester
Member


0
10 posts 2 threads Joined: Dec 2018
08-19-2020, 10:40 PM -
#7
I use my PS4 controller mainly for all my PC games via Xinput, so I assumed RPCS3 would need that setting to work being connected via bluetooth through SCPTool drivers, but good to know that it supports controllers native too though. Also, I'm not a fan of SIXAXIS, so I prefer that being off actually. :-)


Forum Jump:


Users browsing this thread: 2 Guest(s)