Button Mappings Issue

Hey there, Pelerge! Sorry to see any frustrations with setting up controller mapping! If you are using a standard controller instead of an elite controller, you will only be able to set up one configuration for your user. While you can set up the second
controller with another user or guest, those settings will be saved for your user account, not the controller itself.

For more information on controller mapping, you can check out our
Customize your Controller with the Accessories App page. This does a terrific break down of the differences between customizing your elite controller and customizing your standard controller.

Hello dempseyjosh,

Thank you for reaching out to us about your issue!

The Xbox Accessories app will allow you to map one of your paddles to the right thumbstick button and map the right thumbstick button to nothing. To un-map the right thumbstick button, you will have to map the paddle to the button first then remap the right thumbstick button to the "Unmapped" option.

Thank you for the answer it is not an elite controller so that answered why it defaults back due to it is a plain xbox one controller was just curious on why it kept defaulting back

You probably can't switch the assignments, as technically, the RB Button is a digital on/off button, whereas the RT Trigger is seen as an analogue axis. Switching these on a system level, would make multiple games unplayable. If a game like Overwatch allows
remapping, because they "know" that the new button/trigger mapping won't break anything.

But the console won't know if you don't start a driving game after your Apex session, which would cause your car to only allow full throttle or no throttle.

If you require hairtrigger precision in your shooter games that don't allow for remapping, you might want to invest in an

Xbox One Elite controller, which has a small switch, that will move the trigger boundary further to the front, so the trigger feels and acts like a digital button with less travel.

New September 22 update has fixed issue. Thanks for quick action Microsoft