SX controller triggers deadzone increased since latest firmware, or is it just me?

I have had this similar problem. Have you updated your controller to the latest firmware with the april system update? When this happened with me I would have to remove my batteries and restart the controller to fix the issue. Since the latest firmware has
been released I have not had this problem.

Hello IndyBenson! My name is Jeremy and I’m happy to help you with your question.

It is likely stick drift based on your description.

Every game has its own settings for what's known as "deadzone" this just refers to the amount of space you have to physically move the stick before the game will recognize the movement.

Some games have a larger deadzone and some games have no deadzone at all.

This decision is made by the developer.

Some games also have the option to increase or decrease the size of the deadzone, so you may want to look in the settings for the games that have the drifting 8issue to see if you can INCREASE the size of the deadzone.

Also, stick drift is covered under Manufacturers warranty if your controller is still within it.

Regards,

The other problem i have is the issue about the stick drift and the advise given by people on this forum....... the controller was promoted to be played with a certain game that allows full the input from the controller to be accepted, the advise of increasing
your deadzone is rubbish! Oh buy this controller its great oh but by the way you have to set the deadzone to large for it to not drift on the game we are promoting it for........

i found its most useful especially on the elite controller to set deadzones on the xbox accessories app if not id map one of your paddles to the right trigger for BF1

I just got my controller, and it has exactly the same issue: the shortest triggers just won't work. Updating the firmware doesn't help. I think it's because the default trigger dead zone is too large - it's even larger than the shortest trigger. And hence
the triggers simply fail. Hope this can be fixed by upgrading the firmware in the future but not a design flaw.