Gladiator NXT combo axes in conflict in MSFS 2024

[valterg]

Hello.
I've a VKB SIM Gladiator NXT EVO Space Combat Edition + GNX NXT SEM + GNX THQ combo for use in MS Flight Simulator 2024 on Windows 11.
The VKB configuration system automatically split this setup into two virtual systems recognized by Windows and MSFS 2024: one with 8 axes and the other containing the additional axis.
However, this system causes a serious function conflict in MSFS 2024. In my case, the engine mixture lever (X-axis on VC2) directly conflicts with the ailerons (X-axis on VC1). Consequently, moving the mixture lever moves the ailerons.
Even if I remap the axes binding directly within MSFS, all settings are lost as soon as the program is closed and reopened.
I know that I could install the GNX USB Controller / HID-Main module to "isolate" the THQ's three axes, but I would prefer to try a solution via device configuration.
One idea would be to disable the two ministick axes (which I don't use) and assign the mixture axis to one of them, thereby eliminating the need for the second virtual controller.
Is this possible, or do you suggest another option? Please note that I have no technical knowledge regarding device programming or configuration.
Thank you very much.
Dr. Valter - Brazil

[Ron61]

Show screenshots from the configurator. The tabs you need are Global-External and Profile-Axes.
And attach your profile saved to disk in a zip file.

[valterg]

Hello.
Thank you for the reply.
I'm sending the requested screenshots and the profile saved in a zip file.
I took the screenshots labeled "_b" including the 9th axis.
Please let me know if any further information is needed.
Once again, thank you very much for your assistance.
Dr. Valter - Brazil

[Ron61]

I recommend updating the firmware and configurator from here, then all the changes will match the attached images.
If you have a Standard stick (not a Premium one), there's no option to replace the ministick with a button module. Therefore, we'll keep one stick axis (the 5th) and move the 9th axis from THQ to the 6th.
1. Disable the 6th axis of the ministick

2. Move the 9th axis to the 6th

3. Configure the 6th axis exactly to the same settings as the 9th axis and disable the 9th axis

4. Disable the 6th axis in POVs as well

5. Disable VC

6. Calibrate the 6th axis
7. We can make the remaining 5th axis relative, and it will work as a slider

That's it.

[valterg]

Dear Ron61,
I did exactly as you instructed, and your setup works well, moving the 9th axis to the 6th — as expected — and disabled VC2.
However, the POV stopped working.
There is no reaction when moving the POV button up or down.
Moving the POV button to the left causes the POV test arrow to point down, and moving it to the right also causes the POV test arrow to point down.
Can we fix this issue?
It's very important that the POV works well.
I'm sending the configuration file after the adjustments
Thank you very much.
Dr. Valter - Brazil

[valterg]

Dear Ron61,
Did you find a solution to the POV issue following the axis change?
I understand that this problem can be challenging and perhaps difficult to resolve, so I'd like to propose an alternative.
If it's not possible to identify and fix the cause of the POV's erratic behavior in the current setup, I suggest revert the ministick to its original configuration — thereby fully restoring the POV functions — and sacrificing the Gladiator's throttle axis (Z-axis) by assigning the 9th axis to that position instead, effectively eliminating VC2.
Disabling this physical axis, while inconvenient, wouldn't be a major issue, given that the GNX THQ already has a dedicated axis for the throttle function (Slider 1).
Once again, thank you for your kind support
Dr Valter

[Ron61]

Sorry, there was a misunderstanding. After reading that you're not using a ministick, I cut one axis.
But that's okay – the main thing is to understand the problem, and we'll find solutions.
Now, with the new data, I'll do the following.
Let's move the ministick axes from 5th and 6th to 9th and 10th (with all the necessary settings).
In the vacated space, we'll move the three THQ axes (also with all the settings).
In POVs, we'll set the hut to 9th and 10th axes.
VC2 remains disabled, but now we'll also disable the visibility of the 9th and 10th axes (Vs-off, only En-on).
The 8th axis remains empty (in reserve), and I've moved the axis names slightly so they're in order.

G1 is to prevent the switches from constantly glowing when pressed.

Now everything works, but the game will only see one controller.

[valterg]

Dear Ron61,
Unfortunately, the last setup didn't work. In fact, it made the problems much worse. Here's what happened:
a) The THQ's 2nd axis (the middle axis) no longer works and doesn't even appear on the "test->axes1" screen. When attempting to calibrate, the message "Ax.Y 8 DI Axis is inactive" appears.
b) The POV still isn't working. Moving the POV button up and down results in no reaction, but moving it right and left moves the Rot Y axis.
c) Calibration is erratic, resulting in a very limited range of motion for the axes that are still functioning.
I applied the new settings exactly as shown in the screenshots you sent.
Attached are some screenshots of the configurator and the configuration file after these adjustments.
Sorry for the trouble, but since I don't have any knowledge of configuration, I rely on your expertise to get the setup working. I especially rely on you to provide VERY detailed, step-by-step instructions for any modifications.
Thank you very much.
Dr. Valter

[Ron61]

The top line, in parentheses, shows the recommended firmware version for this configurator. You can use firmware with a higher number, but not with a lower one. Stick to this simple rule.
The correct numbers should look like this. Ignore the right SCG grip; your left one will have a different bus address.

[valterg]

Dear Ron61,
The axes are now in their proper positions, and the POV is working correctly again.
Thank you very much for your invaluable guidance.
However, the THQ's second throttle (Rot Z, the middle axis) is only registering half of its intended range of motion, even after calibration.
In other words, compared to the other THQ axes (Rot Y — the first axis, and Slider1 — the third axis), it only travels halfway.
The same issue occurs to Rot X, which is now mapped to the Gladiator's throttle control.
Please note that the same behavior is verified in MSFS, that is, I can't get the full range of motion of these axes in the plane's controls.
I think that there must be a specific setting that allows for the full range of motion on these axes, but I honestly don't know how to do it, and I'm afraid of messing up what has already been accomplished.
Thanks to you, I believe we are now very close to a complete solution of the issues.
Once again, thank you very much for your patience.
Dr. Valter

[Ron61]

Check the boxes in Settings like this, and now when you launch the calibration, you'll be able to select the desired axes.
Before calibration, set the levers to zero. Everything should calibrate.

[valterg]

No success.
The Rot Z axis still half way.
Please take a look at the VKB Joytester screenshot.
I'm also sending the last config profile.
Thanks

[Ron61]

You can try this: enable the Cn checkbox (in physics) for the desired axis and save it to the controller using the Set button.
But now, before calibration, you need to center the lever and move it in both directions during the calibration process.

[valterg]

Unfortunately, your suggestion didn't work.
However, through trial and error basis, in the "Profile-Axis" menu, I changed the HID Usage label for axis 6 from "Rot Z" to "Slider," and the axis is now behaving as it should, with full begin-to-end travel. Calibration was successful, too.
Now, all three THD axes are behaving correctly.
However, I couldn't achieve the same result with the Gladiator's throttle axis (axis 4/Rot X in VKB Device Config)— it still only travels halfway.
I tried other labels from the HID Usage drop-down menu, but the result was either no change in the axis's behavior or, worse, some labels caused this or other axis to disappear completely.
I also noticed that this is the only axis marked as analog.
I think this is the last issue to be fixed.
Any suggestions?
Many thanks.
Dr. Valter

[Ron61]

You're doing something wrong, I can't figure out what.
You can reset all the settings to the defaults, like when the THQ axes were on VC2, and calibrate them so they work at full range. Take a screenshot of the settings, and after transferring the axes, simply enter the numbers for each one manually. In other words, you need to transfer the settings from the working version to the modified one.