Unable to calibrate anything other than X and Y on GF MCG PRO

[ogaruu]

Just like the title says.

I just got my Gunfighter Mk.III MCG PRO EN.
I hooked it up and started reading the calibration steps from here: https://vkbcontrollers.com/?p=7982.
I'm able to see inputs in VKBDevCfg-C.exe in the Axes1 tab just for Axis X and Axis Y.

Moving the MASTER MODE ministick on the MCG’s head through its full range gives no response.
Moving the GATE CONT ministick on the MCG’s head through its full range gives no response.
Squeezing the BRAKE lever fully and letting go of it gives no response.


Most worrying is that in the External Devices tab the grip has a 100% communcation error and is RED
The GF base has 0% and is GREEN

I've tried restarting the device through the Restart button in the Action tab, unplugging the black box, unplugging the base, restarting my computer, no luck.

Since all of that failed I flashed it using _BlackBox_MK2_GF_MCG_PRO_v2_02_5.vkb

Same results, no changes.

What is going on?

Please help.

[admiki]

Did you try to re-seat the grip? Push on it while tightening the screw

[ogaruu]

Between my post and your reply admiki I did just as you suggested. I then changed the springs, took the grip out to do so and I'm in the same spot again. I'll reseat the grip once again though I'm scared of pushing too hard...

[Drano]

Do the three contract pins inside the grip handle spring back after a light push? I like the eraser end of a pencil for that. Pretty safe. The rubber won't damage anything and you can use it to clean off the pins too. They should all feel springy. If they don't they might not make contact with the pads on the base. Looks like some sort of connection issue.

[CruzerDog]

I had the same issue as OGANUU did.
I tried pressing down on the stick to the base as I tightened the bolt.
No help.
I went back to the config to make sure I had the right firmware.

I flashed gunfighter_gf_mcg_ultimate twist v2_055. This gave me the error as above.

I then flashed gunfighter_mk2_mcg_ultimate_twist v2.055, and this fixed the issue.

It looks like flashing the right firmware is in order here…

I hope this helps…
Gary