The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Xbox One Controller Hates Windows 10 (Trigger/Axis issues)
Fiatil
Registered User regular
Registered User regular
I just picked up an Xbox One Controller to replace my 360 pad that is finally starting to fade. I saw they finally added bluetooth support and had excellent experiences with my 360 pad, so it seemed like a no brainer.
Unfortunately, the drivers seem to have a wacky configuration for the way the triggers behave. The result is that all games I've tested behave as if the triggers are constantly being held down. Using my functioning 360 pad as a reference, I went into the windows controller configuration tool and looked at how the axes were functioning. The Z axis in a neutral position is at 50%, and the left trigger moves it from 50-0 while the right moves it from 50-100. This results in everything working as expected with triggers in videogames. However, the Xbox One pad has an additional "Z rotation" field, in addition to the "Z Axis" existant on the 360 pad. However, the Z Axis when no buttons are pressed stays at 0, and moves from 0-100 with the press of the left trigger. The right trigger does the same for "Z Rotation".
It seems like this setup is why all games constantly think the trigger is held down -- in 360 pad world 0 on the Z axis means "I'm holding the left trigger down", while my One pad is at 0 on the Z axis when I haven't pressed any buttons. I have googled long and hard and haven't been able to find a solution though. I have the most updated drivers per both windows and the "X box accesories" app in windows 10. I have tried testing it both with bluetooth and with a wired connection -- the result in games and in the test tool is identical. I've seen a lot of stuff from 2015-2016 that indicates a Windows 10 update jacked this up, but the topics all end with everyone agreeing that it was fixed at some point in 2016, and that it can be solved with a wired connection. I've tried using the windows controller calibration tool, but it wont let me reassign what button controls what axis (left trigger always does Z axis, right trigger always does Z rotation)
It seems like from a hardware perspective the controller is fine. If I use x360ce, which emulates the One pad as a 360 pad, it works completely perfectly. Triggers are not constantly held down, and I can see from the GUI that all of the buttons are behaving as expected. Unfortunately I can't get x360ce to work with a majority of the games I need it for, or else I would be fine using it as a workaround. Does anyone have any idea what's going on? It seems like this can't be for all Windows 10 users with the pad, as it breaks playing just about any game with it. The only solution is to unbind the triggers, which isn't really ideal.
Unfortunately, the drivers seem to have a wacky configuration for the way the triggers behave. The result is that all games I've tested behave as if the triggers are constantly being held down. Using my functioning 360 pad as a reference, I went into the windows controller configuration tool and looked at how the axes were functioning. The Z axis in a neutral position is at 50%, and the left trigger moves it from 50-0 while the right moves it from 50-100. This results in everything working as expected with triggers in videogames. However, the Xbox One pad has an additional "Z rotation" field, in addition to the "Z Axis" existant on the 360 pad. However, the Z Axis when no buttons are pressed stays at 0, and moves from 0-100 with the press of the left trigger. The right trigger does the same for "Z Rotation".
It seems like this setup is why all games constantly think the trigger is held down -- in 360 pad world 0 on the Z axis means "I'm holding the left trigger down", while my One pad is at 0 on the Z axis when I haven't pressed any buttons. I have googled long and hard and haven't been able to find a solution though. I have the most updated drivers per both windows and the "X box accesories" app in windows 10. I have tried testing it both with bluetooth and with a wired connection -- the result in games and in the test tool is identical. I've seen a lot of stuff from 2015-2016 that indicates a Windows 10 update jacked this up, but the topics all end with everyone agreeing that it was fixed at some point in 2016, and that it can be solved with a wired connection. I've tried using the windows controller calibration tool, but it wont let me reassign what button controls what axis (left trigger always does Z axis, right trigger always does Z rotation)
It seems like from a hardware perspective the controller is fine. If I use x360ce, which emulates the One pad as a 360 pad, it works completely perfectly. Triggers are not constantly held down, and I can see from the GUI that all of the buttons are behaving as expected. Unfortunately I can't get x360ce to work with a majority of the games I need it for, or else I would be fine using it as a workaround. Does anyone have any idea what's going on? It seems like this can't be for all Windows 10 users with the pad, as it breaks playing just about any game with it. The only solution is to unbind the triggers, which isn't really ideal.
Fiatil on
0
Posts
https://support.xbox.com/en-US/xbox-on-windows/accessories/how-to-update-xbox-one-controller-windows-10
Edit: Aand I was just able to test it on my roommate's Windows 10 PC as well. Plugged it in, everything works great. Sooo I guess it's just my windows 10 PC that hates the controller, but I'm still totally stumped. Firmware up to date, drivers up to date, Windows 10 shows no updates to be installed, yet I get a "Z Rotation" on my PC and not on others. The other two PCs show no Z rotation, with both controllers controlling the Z Axis just like I want.
Tl:dr my PC and controller were stuck in 2016
I guess that explains. I was trying to replicate your issue with my Surface Pro (I don't have BT on my desktop), and left stumped.
I had no idea the "Creator's Update" was a thing until this saga. I had heard about all of the gaming mode stuff and was slightly puzzled as to why I didn't seem to have any of it yet, but it was never a big issue. I'm assuming it tried to install the update a couple of months ago, hit the instant restart error due to me having two hard drives and gave up. So hooray, I fixed a few problems at once.