VKB-SIM

I wonder if anyone can tell me why hasn’t anyone posted a guide on how to set up
A VkB throttle with MSFS 2024 there must be people out there like me who can’t get their throttle to work in the new sim

What exactly is difficult, what doesn’t work?

I am not the OP, but I got a problem with my Gladiator EVO + GNX-THQ Combo in MSFS2024, but I think it is a problem with MSFS24, because it worked in 2020.

If I understand the modules correctly, they are combined in the software VKBDefConfig but are then transmitted to the sim as two controllers because of Windows-related limitations on number of buttons and axis, right?
Both transmitted controllers show up in MSFS 2024 with the same name and that seems to be the problem. Because I configured the aileron-axis to my joystick, but when I configure mixture to the right lever of the gnx-thq that overwrites my setting for the joystick. Is there a way to change the names of the transmitted controllers?

[img][/img]

Thanks, mo

Show the Global tab from the configurator.
Perhaps you have a division into 2 controllers with 32 buttons each and that is why you have this situation.
Set "No" here and you will get one controller with 128 buttons, which are perfectly visible in FS2024.

Thanks for your reply, but I'm afraid thats not working.
I updated the DeviceConfig to the newest version, because your screenshot looked different then mine.
While updating I also flashed the newest firmware to the EVO-THQ-Combo, which is not working correctly (see other thread).
I downgraded the firmware to 2.184 which fixed the missing axis of the joystick.

Now to my initial problem:
When I set the "VC" to "No" as you suggested, I cannot calibrate and find the last lever on the THQ, which was only shown on the second controller.
I had hoped, that the new firmware would just put all axis on one controller, instead of reserving two axis (Rot X and Y) for the analog hat of the premium stick (I only have the standard grip, where the hat is just buttons...)

How do I configure the combo to be only one controller with all the axis available on both devices?
I managed to deactivate the axis for the hat, but how can I configure the axis 9 to be on VC1?



Thanks, mo

Yeah, I see. Then you need to put 1 there to capture the 9th (or first on 2 VC) axis.
And then in the Global-External tab you can understand how and where each axis is.
I have the WWII knob on my second THQ, so they also take up the 10th and 11th axes.


p.s.
If we have 2 VC, then there will definitely be 2 devices with the same names in the game. Since you have Standard, then there is another way.
You just need to specify a new location for the 9th axis on any empty one (5 or 6), write 1-5 or 1-6 instead of 2-1. And disable the second VC (set to No).
Duplicate all the settings for the ninth axis in the new location and recalibrate. You will have one more free space left for the virtual axis.

Nope, can't get it to work.

You can't map an external axis to 1-9 - it automatically reverts it to 1-8. Makes sense, since a controller can only have 8 axis.
The manual says this too.

I then tried to map the thq to 6,7,8 on VC1, and set the original external axis 5 and 6 from the stick (the POV-Hat) to the second VC to make room for the THQ.
Doesn't work either.
I then set the Hat Controller to Discrete, because on that page there was a mapping to axis 5 and 6 too...
Then I set the logical axis 6,7 and 8 to the same values, nothing changed.

I am a little bit frustrated. I really like a product where you can make deep customizations. But it is neither self-explanatory, nor does the manual do a good job telling you how to remap an axis.









Any Ideas where my brain takes the wrong turn?

Thanks, mo

For those who have an SCG Standard grip (not Premium) and a THQ module, I will describe the procedure for transferring the 9th THQ axis to the place of the missing ministick on the grip.
This will allow you to get a single device in games, instead of 2 identical ones by name:
1. you should change 1 to 3 and then select None on the SCG grip
2. move the 9th axis (2-1) to the 6th (1-6) or do it in order (1-6,1-7,1-8)
3. disable the second VC (there was the 9th axis), setting No
4. duplicate the settings of the 9th axis in the new place Logical (DzLo, DzHi) and Physical (ACn, Curve=Off)
5. in POVs make a push-button HAT (Discrete)
6. in Buttons from the switch button (uSSw) make a simple one or the one needed on request
7. write to the controller with the Set button and then calibrate all the axes
8. you can reassign the names in the HID Usage column so that the axes follow the system order (not necessary)

Thanks, I finally got it working!

I would add the following steps, without them it did not work for me:

After Step 2: Write to the controller with the Set button.
(else the settings from the External Device Configuration are lost when you go to the Common Page)

For me Step 8 was neccessary to show all axis in the Test Window!
Before Reordering the HID Usage there were only 7 Axis shown and the right lever still didn't work.

Here are my final settings for future reference:



Thanks again for your support!

mo

Just in case, I draw attention to the line in the "header" of the configurator. It indicates the recommended version for this particular configurator (in brackets). Higher - yes, lower - no.

Yes, ok. But: viewtopic.php?f=25&t=8310&hilit=calibration
There is a confirmed bug with V2.18.9 and my combo - that's why I had to downgrade the firmware...
I did not know, that I should have downgraded VKBDevConfig too.

- mo -

Hello, I'm brand new to VKB and just received the NXT EVO and THQ... after nearly thowing these out my window in frustration I found that the new firmware was bugged. Reverted back and it's working now.

But now I have the issue listed above... my last throttle shows up as a separate control in MSFS 2024. The solution given is for the Standard grip, but I have the Premium grip. Is there a solution for the Premium grip?

Thanks!

The solution is the game to get fixed, so virtual controllers would work the same as they were working in MSFS2020.
There's no other way for you to go around that, as Windows has a 8 axes limitation and your device has 9 axes, so one of those axes has to get transferred on an additional virtual device.

In order not to wait for fixes in the game, we can actually try to customize your configuration to get a single controller with almost the same functionality (with some limitations).
There are several options, but in any of them you will have to sacrifice something.
Since we need space for the 9th axis on VC1 (virtual controller), then either disable the twist or gas axis, which is not very desirable.
Or replace the ministick on the handle with a button module, thereby freeing up its two axes (5th and 6th) and moving the 9th in their place. Which is also not desirable.
There is a third option - to abandon the ministick switch function (uSSw), which allows you to switch it to HAT or axes and leave only HAT.
As a result, we will have only one virtual controller with 3 THQ axes.
The setup process is not much different from the above, the whole task comes down to the initial setup and calibration and only then disabling VC2.
First, we transfer the ministick axes to VC2 (2-1, 2-2), not forgetting to make changes in the POV tab, at the same time disabling activation and leaving "Always".
Disable the "uSSw" stick switch in the Buttons tab, make a simple button or whatever you come up with.
Configure the THQ axes and set them up according to your preferences. The 5th axis is disabled, remains in reserve, you can configure the virtual one.
Calibrate all (I emphasize) axes until you get similar numbers, as in the screenshots.
Check the work and only now disable VC2. That's it.

In fw v2_18_D there is an attempt to detect the presence of ministick ( SCG grip) when GNX (+EVO) is autoconfigured.
In the case of the THQ kit, the module is placed on axis 5-6-7 and axis 8 is left free.