I recently began using a VKB Gladiator NXT EVO joystick. Drivers and firmware are confirmed up-to-date, it is calibrated, and it works without issue in MSFS.

MCE recognizes the controller and the button via the MCE UI when I set buttons for ATC ([GAMEPAD] in mce.ini) and speech mute ([HARD_MUTE_JOY] in mce.ini).

The following are present in mce.ini:

[GAMEPAD]
JoyManID= VKBsim Gladiator EVO L  
JoyProdID= VKBsim Gladiator EVO L  
JoyButton=22
UseWithVoxATC=1    

[HARD_MUTE_JOY]
JoyManID=VKBsim Gladiator EVO L
JoyProdID=VKBsim Gladiator EVO L
JoyButton=4

However, I get the follow error messages when opening MCE and when attempting to modify the joystick button assignments via the UI:

I have confirmed that the joystick is connected to the computer and is working. Button inputs are recognized in the joystick's configurator software and in the Control Panel USB game controller menu. I have also done a series of restarts and even uninstalled/reinstalled MCE (via Add/Remove Programs).

I have other controllers connected (throttle and rudder pedals), but none of them have buttons assigned to MCE and they aren't present in mce.ini. Here is the Game Controllers menu from Control Panel:

Edited March 15, 20251 yr by AdequatelySuitable

On 3/15/2025 at 4:35 PM, AdequatelySuitable said:

I recently began using a VKB Gladiator NXT EVO joystick. Drivers and firmware are confirmed up-to-date, it is calibrated, and it works without issue in MSFS.

MCE recognizes the controller and the button via the MCE UI when I set buttons for ATC ([GAMEPAD] in mce.ini) and speech mute ([HARD_MUTE_JOY] in mce.ini).

The following are present in mce.ini:

[GAMEPAD]
JoyManID= VKBsim Gladiator EVO L  
JoyProdID= VKBsim Gladiator EVO L  
JoyButton=22
UseWithVoxATC=1    

[HARD_MUTE_JOY]
JoyManID=VKBsim Gladiator EVO L
JoyProdID=VKBsim Gladiator EVO L
JoyButton=4

However, I get the follow error messages when opening MCE and when attempting to modify the joystick button assignments via the UI:

I have confirmed that the joystick is connected to the computer and is working. Button inputs are recognized in the joystick's configurator software and in the Control Panel USB game controller menu. I have also done a series of restarts and even uninstalled/reinstalled MCE (via Add/Remove Programs).

I have other controllers connected (throttle and rudder pedals), but none of them have buttons assigned to MCE and they aren't present in mce.ini. Here is the Game Controllers menu from Control Panel:

At first, I thought could have something to do with thee number of buttons. I can confirm you can have multiple joysticks and up to 32 buttons per joystick.

You need to be aware that all joysticks that have buttons assigned MUST be connected before MCE is started.

Let us know if still unable to use those buttons.

 

Edited March 19, 20251 yr by FS++

On 3/18/2025 at 1:09 PM, FS++ said:

At first, I thought could have something to do with thee number of buttons. I can confirm you can have multiple joysticks and up to 32 buttons per joystick.

You need to be aware that all joysticks that have buttons assigned MUST be connected before MCE is started.

Let us know if still unable to use those buttons.

 

I confirmed that the joystick is connected prior to starting MCE, but I still get the error messages.

On further investigation, I do not get the error messages when I unplug the other two peripherals (T-Pendular-Rudder and TCA Q-Eng 1&2). When only the VKB joystick is plugged in, there is no error and the assigned buttons work as they should. However, if I plug in either or both of the other two peripherals (T-Pendular-Rudder and/or TCA Q-Eng 1&2) while keeping the joystick plugged in, I do get the error messages.

Up until a week ago or so, I had a different joystick (Thrustmaster) with buttons programmed for ATC and speech mute. The T-Pendular-Rudder and TCA Q-Eng 1&2 were plugged in at the same time as the old Thrustmaster joystick. I changed the button assignments for ATC and speech mute (and confirmed them in the config file) after plugging in the new VKB joystick. The only thing that has changed in my setup recently is the VKB joystick, so MCE must have an issue with having two of the "old" peripherals in use in combination with the new VKB joystick.

20 hours ago, AdequatelySuitable said:

I confirmed that the joystick is connected prior to starting MCE, but I still get the error messages.

On further investigation, I do not get the error messages when I unplug the other two peripherals (T-Pendular-Rudder and TCA Q-Eng 1&2). When only the VKB joystick is plugged in, there is no error and the assigned buttons work as they should. However, if I plug in either or both of the other two peripherals (T-Pendular-Rudder and/or TCA Q-Eng 1&2) while keeping the joystick plugged in, I do get the error messages.

Up until a week ago or so, I had a different joystick (Thrustmaster) with buttons programmed for ATC and speech mute. The T-Pendular-Rudder and TCA Q-Eng 1&2 were plugged in at the same time as the old Thrustmaster joystick. I changed the button assignments for ATC and speech mute (and confirmed them in the config file) after plugging in the new VKB joystick. The only thing that has changed in my setup recently is the VKB joystick, so MCE must have an issue with having two of the "old" peripherals in use in combination with the new VKB joystick.

If the VKBsim evo joystick is wireless ensure it didn't go to sleep prior to starting MCE. You can set a USB port to never go to sleep in Windows device settings.

I suggest you try each joystick separately and try assigning buttons in each to see if MCE has no issues interacting with them.

Check the assignments aren't lost with each.

Finally, have the VKBSim joystick plugged alone, re-assign buttons. 

Restart MCE to check assignments not lost.

Then re-plug the others and confirm whether the issue is still there.

Are all of your joysticks wireless?

 

 

 

2 hours ago, FS++ said:

If the VKBsim evo joystick is wireless ensure it didn't go to sleep prior to starting MCE. You can set a USB port to never go to sleep in Windows device settings.

I suggest you try each joystick separately and try assigning buttons in each to see if MCE has no issues interacting with them.

Check the assignments aren't lost with each.

Finally, have the VKBSim joystick plugged alone, re-assign buttons. 

Restart MCE to check assignments not lost.

Then re-plug the others and confirm whether the issue is still there.

Are all of your joysticks wireless?

 

 

 

None of my peripherals (joystick, throttles, or rudder) are wireless. They are all connected via USB. 

After further experimentation, it appears that the only time MCE starts without the previously mentioned error messages is when only the VKB joystick is connected (the rudder pedals and throttle quadrant are unplugged). If I have any combination of the rudder pedals and/or throttle connected at the same time as the joystick (rudder + joystick, throttle + joystick, or rudder + throttle + joystick), then I get the "joystick disconnected" error messages.

I did discover that if I start MCE with only the joystick connected, then plug in the rudder pedals and throttle quadrant after MCE is open, I do not have any problems. After performing these steps, I find that if I attempt to modify the ATC joystick button via the UI (see screenshot below), MCE doesn't even recognize buttons I press on the throttle quadrant. It will only recognize different buttons that I press on the VKB joystick. For example, I can change to any other button on the joystick via the UI, but the button assignment window below doesn't recognize any inputs from the throttles.

It seems to me as if MCE is "prioritizing" one peripheral over the others by MCE. Whenever two or all three peripherals are connected before starting MCE, the joystick seems to take a lower priority and is not recognized by MCE, resulting in the "joystick disconnected" errors. However, if I have only the joystick plugged in before starting MCE, then connect the other two peripherals after MCE is open, the joystick inputs are recognized and there are no error messages.

As a side note, all three peripherals (joystick, rudder pedals, and throttle quadrant) all work together at the same time without issue in MSFS.

Edited March 20, 20251 yr by AdequatelySuitable

On 3/20/2025 at 11:49 PM, AdequatelySuitable said:

None of my peripherals (joystick, throttles, or rudder) are wireless. They are all connected via USB. 

After further experimentation, it appears that the only time MCE starts without the previously mentioned error messages is when only the VKB joystick is connected (the rudder pedals and throttle quadrant are unplugged). If I have any combination of the rudder pedals and/or throttle connected at the same time as the joystick (rudder + joystick, throttle + joystick, or rudder + throttle + joystick), then I get the "joystick disconnected" error messages.

I did discover that if I start MCE with only the joystick connected, then plug in the rudder pedals and throttle quadrant after MCE is open, I do not have any problems. After performing these steps, I find that if I attempt to modify the ATC joystick button via the UI (see screenshot below), MCE doesn't even recognize buttons I press on the throttle quadrant. It will only recognize different buttons that I press on the VKB joystick. For example, I can change to any other button on the joystick via the UI, but the button assignment window below doesn't recognize any inputs from the throttles.

It seems to me as if MCE is "prioritizing" one peripheral over the others by MCE. Whenever two or all three peripherals are connected before starting MCE, the joystick seems to take a lower priority and is not recognized by MCE, resulting in the "joystick disconnected" errors. However, if I have only the joystick plugged in before starting MCE, then connect the other two peripherals after MCE is open, the joystick inputs are recognized and there are no error messages.

As a side note, all three peripherals (joystick, rudder pedals, and throttle quadrant) all work together at the same time without issue in MSFS.

Just to make sure MCE is tracking all connected joysticks and the respective buttons, please perform this test.

With all of them connected prior to staring MCE, assign ATC PTT to a different joystick.

Assign hard mute to yet another joystick (other than the VKBsim.

Restart a few times and check all is go.

Eventually disconnect the VKBsim joystick and check MCE doesn't complain.

Once the VKBsim is confirmed to be the root of the issue, we'll see what can be done.

From past experience that joystick name which comes from the device driver may have trailing characters (maybe invisible) that cause failure when MCE checks for the exact name.

Thank you.

Edited March 22, 20251 yr by FS++

On 3/22/2025 at 3:25 PM, FS++ said:

Just to make sure MCE is tracking all connected joysticks and the respective buttons, please perform this test.

With all of them connected prior to staring MCE, assign ATC PTT to a different joystick.

Assign hard mute to yet another joystick (other than the VKBsim.

Restart a few times and check all is go.

Eventually disconnect the VKBsim joystick and check MCE doesn't complain.

Once the VKBsim is confirmed to be the root of the issue, we'll see what can be done.

From past experience that joystick name which comes from the device driver may have trailing characters (maybe invisible) that cause failure when MCE checks for the exact name.

Thank you.

I performed the tests as described and the other controllers (throttle quadrant and rudder pedals) work without issue when the ATC and mute buttons are assigned to them and everything is still plugged in. No error messages after restarting MCE.

It would appear that the VKB joystick is the issue, as the error messages only appear when the ATC and mute functions are assigned to it while the other two controllers are connected. I will note that the VKB joystick works without issue (no error messages) when it is the only controller connected. 

Thank you again.