VKB-SIM

Hi Everyone,

I have an MCG Ultimate without the twist adapter (most current version) that I love. I recently bought the T-Rudders and have read the forum about the maximum number of axis in Windows. My issue is that when I flash the grip with the latest universal config file it always shows up in the DevCfg software as the MCG Ultimate Twist? I have the T-Rudder system working as a stand alone using it's own Black Box Mk3 but would prefer to have it use the the MCG's Blackbox. Since it shows up as a "twist" version I am maxed out on axis.

My question is if it should be showing up as the "twist" when it's not and if so what can I do to either make it show up correctly or disable the "phantom" twist axis that is there?

I've tried manipulating the profile in DevCfg with no luck.

Thanks in advance for any insight anyone can offer!

Regards

What version of BlackBox is used with GF MCGU? Show me the photo.

Hi and thanks for the reply,



It is the latest version that came with the GF system a couple weeks ago. Attached is a pick

With pedals connected to BlackBox GF, reset them to default using the button in the configurator and show a screenshot of the Global-External tab.

Second pic just in case you needed it.

Thanks

Select the pedals and take a screenshot. And show the Profile-Axes tab.
Try updating the firmware and configurator from here.

Will do the firmware and configurator now and report back.

Thanks

When I ran the config this time from the download site you sent it said something about "twist axis is missing or blocked do I want to correct it?" so I said yes. Then I flashed with the latest cfg file I could see in that list.

Here is what it looks like now. I tried the rudders and they still do not show the axis moving.

Change 11 to 7, write it to the controller with the Set button and it should work.
If it doesn’t work, reset it to default on the new firmware (2.17E) and try to calibrate again.

Thank you Ron61!

That worked perfectly and the T-Rudder axis now works in the test tab.

I'll assume I should just keep using the 2.17E firmware until an update officially comes?

Thanks again,

Jim

That is great.