Problem with wired Rock Candy wired XB1 controller

[Grimmsqueaker]

Bit of a bizarre issue, D Pad is fine and all menus work as they should but when ingame the camera is wildly spining round the main character, if I hold left trigger down it slows slightly and spins opposite direction.

I do have a wireles 360 pad which is getting on a bit now and can occasionally drift but otherwise works fine.

Anyone got any ideas?

[Enverex]

It's because it doesn't read the inputs properly. If you hold in both triggers EXACTLY half way in (which puts them to 0 on the trigger axis) you'll find the camera stops spinning and levels out. Obviously that's not viable and the menu has no way to remap these controls.

It seems this has been an issue since release and no-one's found a fix (and the devs clearly don't care about properly supporting gamepads).

[Grimmsqueaker]

I was thinking as much, at least I know not the only one it is happening to. Wonder if the official XB1 controller is the same.

[Trehek]

Heh, looks like many threads are up with this problem.

Playstation uses DirectInput for its controllers, and they didn't add XInput support when they ported this game to PC. XBox controllers use XInput, so unless your controller has the option to switch to DirectInput (some controllers have a switch in the back), your options are using another controller or picking up a driver update to your controller and trying if that makes it more compatible.

[Grimmsqueaker]

I do have one of the Logitech pads with the switch, use it for the older games where characters spin on the spot like Urban Chaos, flick the switch and Direct Input is fine.

The 360 wireless controller is fine, just the XB1 controller that is funny.

[Trehek]

Originally posted by Ferral:

I do have one of the Logitech pads with the switch, use it for the older games where characters spin on the spot like Urban Chaos, flick the switch and Direct Input is fine.

The 360 wireless controller is fine, just the XB1 controller that is funny.

There's been a lot of discussion about this before, but solutions seem a bit sketchy. Apparently a driver update can help with some controllers but not all of them (possibly depending on your version of Windows). Check out this thread for possible solutions:

http://steamcommunity.com/app/331600/discussions/0/520518053436741110/

[Enverex]

DirectInput (instead of XInput) is fine, it's what almost all games used to use. The problem with this game is that it doesn't actually let you remap the controls properly, which renders it impossible to use with some (most?) controllers.

In my situation, I'm trying to play the game under Wine on Linux with official XBox 360 controllers, but the camera keeps spinning as it seems to have mapped the camera to the triggers rather than the right analog stick and doesn't let you remap it.

[Trehek]

DirectInput is all that Playstation uses, so the devs were probably used to it. PC also has DirectInput, so maybe they were expecting it to work. The game lets you remap everything except the sticks, and assuming a DirectInput controller, where else would you even want to remap them? On the other hand, considering a M+KB, the option to remap those controls should've been there! Some inexperience and unfortunate assumptions on part of the devs there probably, but also a shame they didn't work out a patch.

I mostly blame Microsoft for the whole problem, though. They did a poor job designing XInput. There are unnecessary changes from DirectInput (which is also a Microsoft product so why become incompatible for no reason?), and more importantly, unnecessary and foolish limitations which DirectInput doesn't have at all! (such as limiting the number of possible input devices, limit of only using controllers, limit on the number of control axes and buttons etc.) Basically, there's only ONE benefit in XInput compared to DirectInput: independent analog axes for triggers. So why didn't they just update DirectInput which has remained the same since DirectX 8?

With how it is now, it's always one camp having problems. With this game it's the XInput camp. With the Dark Souls series, for example, it's the DirectInput camp.

[Trehek]

I may have stumbled upon a possible solution, a utility called XInput Plus. A tutorial on how to install and use it, as well as links to a download site, can be found here:

http://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/

The utility allows you to remap every control binding on your controller, but it also has a feature for enabling DirectInput output for a XInput controller. This should solve the problem. I don't have a XBox controller to test it out myself, but if you wanna give it a try, using the utility's DirectInput tab to set up a profile for OPPW 3 should be able to give the game the controller input it expects.