Unsure if bug or not, but can anybody give their feedback on this?

[Miko]

My keybindings are malfunctioning suddenly. I've reset and redone them all since the new features had no bindings, but what I've noticed since the update is combinations such as holding Circle (PlayStation) and clicking the Left Stick is triggering boosts, which shouldn't happen. Even if I do not press circle again, but only click the Left Stick, it triggers as if I'm pressing Circle separately. Same with my binding for night vision being Triangle and Left Stick. It tries to activate the frameshift drive over and over if ai toggle the night vision on and off by clicking the Stick to complete the combination. It never used to do this with a combination press.

Anybody else having control issues?

 

[JonLuis69]

If you choose default settings the most important new settings are mapped, just do that and tinker is all we can do.

 

[Miko]

That's not what I'd asked. I'm aware of how to set up my bindings, but I'm talking about the combination of two buttons now being treated as if both buttons are also being pressed sperately at times.

Toggling Night Vision in Supercruise for example can give me a "Too fast for safe exit" and drops me out causing damage because it thinks I pressed Triangle separately twice when in fact I held triangle once and only pressed the Left Stick twice, which as a combination should toggle Night Vision only.

 

[Miko]

I've changed my controls to prevent clashing with more important functions. But this thread still stands to question why the controls play up in that way. Bug or not. Hopefully the bindings can be tweaked to tighten up this kind of thing.

 

[Buster Bob]

I also am having issues with controls. Although initially everything appears fine, for some reason I appear to be lose all controls, including the 'ESC' to bring up the exit menu! Pushing random keys sometimes brings up a Boost, but apart from that it appears to go haywire. I end up having to do a hard shutdown of the program by closing with app in Windows 10. Going back in corrects everything, then it happens again! Still looking to try and make some sense out of it.