As I said in my previous post, you can’t bind it this way in MSFS. Sure, you can get it to work in other simulator, but that’s irrelevant, because MSFS designed to treats the hardware input differently.
I already watched your video, and the reason why you set it that way is exactly why you have the problem.
As I explained in my previous post, if you set both primary and secondary to separate axis, the sim receives inputs from “Both” of them at the same time. So if you move the Joystick Slider X, the sim receives the movement, but at the same time the sim is also receiving the input from your Joystick R-Axis Z which is at Center. That’s why it’s confusing, it’s taking input of both TURN and CENTER at the same time. Giving you the jittery pedal movement in the cockpit.
You might be confused with the CENTER position. MSFS does not treat CENTER as OFF. Or in other words, if your axis is neutral, it’s not feeding any input into the sim. That’s an incorrect assumption. The reality is, the axis is continously feeding the sim with an analog value between 0% to 100%. And the center point is actually feeding the command of 50% position all the time.
So if one axis is feeding the sim with 0% because you’re turning left. While the other axis is left alone, the other axis is feeding the sim with 50% input all the time. So it’s getting both 0% and 50% command at the same time, confusing it.
It’s not a bug, that’s how it’s always been designed.
If you want ground control, the only aircraft that allows you to separate the two axis is the FBW A32NX, it has a separate Rudder control, and the nose wheel tiller control separately. For that aircraft, you can bind the two axis separately, but they don’t go to the same Rudder command, there’s a separate axis that they use to control the nosewheel.
I hope this could help you understand how MSFS manage the control bindings.