The controller does connect, but while I am playing the mapping of controls changes randomly. For example, RB changes between menu options but sometimes closes it when moving from one option to another.
The controller works well on other platforms.
I tried to update the controller, uplay and the game but nothing fix the problem.
Is there anything else I can try? Thank you and sorry for my english![]()
This isn't an issue I've heard of in the past, but I'm happy to look into this for you! Could you let me know what other buttons change? Does this issue happen with a wired controlled? What dongle are you using?
This is STILL an issue. Using a brand new XBox One controller on a PC and every other game works fine (played Division 2 since beta with no problems). But for Wildlands everything will be working fine, then you go hold X to pick something up and it launches the drone for some reason. You have to hit the UP directional pad to shut down the drone and then X is fine again for a while.
Can confirm. Having same issues with intermittent random button mapping. eg, when I press X or B, often it will launch the drone or the binoculars.
Using wireless xbox one controller, Windows 10. thanks. Oh, and using native bluetooth connection on Predator Helios 300 laptop.
Hey there! Does this same issue happen when you used the controller wired?
No, I think it only happens in wireless mode. I tried to play Ghost Recon Wildlands and the same happens with the Breakpoint bet.
Thanks for the answers and sorry for answering late, I've been very busy at work lately.
It also happens when I press the RT button to accelerate on the vehicle. Sometimes what it does is rotate the camera.
This is STILL an issue. Using a brand new XBox One controller on a PC and every other game works fine (played Division 2 since beta with no problems). But for Wildlands everything will be working fine, then you go hold X to pick something up and it launches the drone for some reason. You have to hit the UP directional pad to shut down the drone and then X is fine again for a while.
Sorry to necro this thread; but that is exactly what is happening to me. I thought I was going crazy!
I'm using an Xbox One controller via bluetooth and for some reason at unexpected intervals a button will suddenly be "remapped" to another action; the only thing that seems to reset it is to perform the action using the correct control. The exact scenario GoldenDBA described has happened to me - "B" suddenly starts toggling the binoculars; but using the "down" arrow fixes it and everything will be fine for a time.
Analog inputs also seem to switch, and I've experienced what Kansible has noted; my camera will start spinning wildly around my vehicle as its acceleration drops to zero. Futz with the right stick and suddenly everything is fine again for a while.
Has anyone found a resolution for this issue?
I found a solution on the Steam forum for Wildlands; apparently this is a known issue with other Ubisoft games.
Basically, you set up your Xbox controller to be handled by Steam's built in controller support, and it seems to take care of the issue. I also had to go into the controller configuration and shrink the control stick dead zones quite a lot - by default the dead zone is huge and it makes small aiming corrections difficult. It still doesn't feel quite a good as the Wildlands controller support, but the buttons do what they're supposed to do every time - so it's a net win.
I have a possible fix for this, works for me at least.
I had the same issue as above using Bluetooth, but not wired. & the problem was there whether Steam was running or not, so the issue is with UBI & the bluetooth controller, not Steam
Import GRW as a non Steam game into Steam
Add your Xbox controller to Steam if you haven't already
Go in to steam controller configuration on GRW (or whatever you have imported it as)
This is not just for Steam Controllers, works for Xbox, PS4, Nintendo pro etc
Default settings should be standard Xbox controller emulation
Leave as is and launch the game through Steam
Hey mbinks,
Thanks for sharing your workaround for this issue!