Dark Souls PTDE

Flowey · May 23, 2016

So I wanted to play Dark Souls Prepare to Die Edition. Since I can't play SoulsBorne games without a remote, I, as usual, connected my PS4 controller to my PC. It's been working pretty well since I started using inputmapper, can play a few games with it. Now, for some GOD DAMN REASON when I load the game the camera spins around outta control and the buttons are mapped weirdly. I've tried pretty much everything that forums had in stoe, from the bat file to connect the remote exclusivly, to using DS4Windows, blablabla. Not working.

Anyone else had these issues and fixed them? Cause it's pissing me off so much! Succ a trivial thing being so complex, I know the port was shit but come on FROM, at least give us something to work with!

Geekavenger · May 23, 2016

Do you have any other control devices plugged in? For some reason Dark Souls PTDE was doing the same thing for me. I had my HOTAS, or my G13 plugged in, and somehow one or both of those would screw things up. Basically I had to unplug all Input peripherals besides my keyboard, mouse and Steam Controller.

sqwidee · May 23, 2016

DS4windows is an antiquated program. Use InputMapper and have it emulate an Xbox pad. If you're using Windows 10, a lot of input programs will not properly use the controller in "exclusive mode", which means you'll get the XInput emulation layered on top of the raw inputs that the PS4 controller already supports for windows. I had this problem for a while when I was using older DS4 programs. InputMapper will tell you if it manages to actually get the controller into "exclusive mode", and if it does, you're good. If it only goes to "shared mode" you'll get the same problem as before, but there are fixes that work with InputMapper to get around this.

Flowey · May 24, 2016

9 hours ago, sqwidee said:

DS4windows is an antiquated program. Use InputMapper and have it emulate an Xbox pad. If you're using Windows 10, a lot of input programs will not properly use the controller in "exclusive mode", which means you'll get the XInput emulation layered on top of the raw inputs that the PS4 controller already supports for windows. I had this problem for a while when I was using older DS4 programs. InputMapper will tell you if it manages to actually get the controller into "exclusive mode", and if it does, you're good. If it only goes to "shared mode" you'll get the same problem as before, but there are fixes that work with InputMapper to get around this.

Oh I've tried boh inputmapper and DS4 windows, sorry, should have precised that first. Doesn't work with Input mapper as well, and now I've fucked so much with the settings that when I check devices xbox 360 controller ain't there anymore, just the xinput one.