Z-Axis, Z-Rotation Issue (new 4 axis Xbox driver issue)

[wiidesire-2]

In older Xbox One controller drivers, the triggers LT and RT shared the same Z-axis rotation to split movement on the Z-axis.
-> LT and RT did not operate independently of each other

However in Windows 10 and the newer Xbox One (Elite) Controller driver, LT and RT operate independently, each with it's own axis.

For example I just got my Xbox One Elite Controller (so I can't install old drivers) and Maniaplanet doesn't understand that LT and RT are now independent from each other. The result is, that my car automatically throttles even if I don't press any button. Tried everything (just selecting an axis for analog throttling, analog breaking etc.).

Any fix for this coming?

________
For anyone who doesn't understand what's happening and has the same problem:
With the old 3 axis configuration in the drivers, if you didn't press LT or RT z-axis was at 50%. If you did press LT it went to 0% and if you press RT it went to 100%.

Now with the new 4 axis configuration, Z-Axis (LT) is at 0%, if you press it, it goes to 100%. Z-Rotation Axis (RT) is at 0%, if you press it, it goes to 100%.

[wiidesire-2]

If the issue was unclear, here is quote from a different forum:

For those who want to play ... with an XBox One controller be warned. On windows 10, both triggers are mapped independantly on 2 separate axis (the Z axis and the Rotation Z axis). Pressing the left trigger bring the "Z axis" to 0 while releasing it send it to its maximum value. Pressing the right trigger bring the "Rotation Z axis" to 0 and releasing it send it to its maximum value. Grandia 2 uses only one of these axis. So the screen will always rotate, because the value is either 0 or its maximum value.

This problem does not exist with the XBox 360 controller because both triggers are mapped to the same Z axis. Pressing the left trigger bring the Z axis to 0, pressing the right trigger send the Z axis to its maximum value, and pressing no trigger place the Z axis in the middle.

[wiidesire-2]

Is Nadeo even active in this subforum?

[TMarc]

they are reading, but currently they are not doing anything on Maniaplanet, there will not be any bugfix or new release this year.
You have to find a different solution for the time being, like remap to other triggers.

Did you try the options in the launcher's advanced input configuration?
Perhaps "Freeze unused axis" is set and blocks you now.
And also try "Alternate method".

[wiidesire-2]

Did you try the options in the launcher's advanced input configuration?
Perhaps "Freeze unused axis" is set and blocks you now.
And also try "Alternate method".

Thanks, I tried that, didn't work though.

they are reading, but currently they are not doing anything on Maniaplanet, there will not be any bugfix or new release this year.

The bigger problem with this is that the same issue will be present in Trackmania Turbo unless Nadeo acknowledges it.

[TMarc]

The bigger problem with this is that the same issue will be present in Trackmania Turbo unless Nadeo acknowledges it.

Not necessarily. The things they have done with TMT might not be merged back to maniaplanet at the moment.
After all, they are not yet ready, otherwise they would have met the original release date...

[Dommy]

The funniest thing you forgot to point out is that TrackMania doesn't support analog acceleration and braking - even if you bind analog inputs for them, they work as digital buttons (0%-50% - not pressed, 50%-100% - pressed).

Btw, with my Logitech F510 controller I can switch to DirectInput mode, where analog triggers work as separate digital buttons. But still personally I'm using (A) for accelerating and (X) for braking. \LT\ I set for net analyzer and /RT/ for reverse camera. Even rumble feature works only in DirectInput mode for me.