Pulse Button Center of Flip Trigger Travel
Posted: Sun Oct 14, 2018 20:09
Hi,
I have a Mk2 Gunfighter with MCG-Pro that I purchased, and set up as a helicopter cyclic. I was able to program the trigger through the DevCfg software to provide a pulse button when flipped to allow for the switching of triggers in the DCS Ka-50 that is pretty realistic.
I have a second Gunfighter, Mk1 model, that I have had for a little longer, with a separately purchased MCG-Pro that I have set up for flying fighters.
I wanted to setup the Mk 1 model the same way as the Mk2, albeit with a completely separate Black Box. When I flashed the firmware, and loaded the profile, everything seems to work fine, except the trigger function. There is no pulse (button 24 on my config), and button 25 remains constantly on if the trigger is flipped down, unlike the Mk2. Also, the trigger on the Mk1 feels a lot more spongy, without a distinct click, unlike the newer MCG I have that works fine.
I've tried re-calibrating, as well as taking snapshots with DevCfg with the working stick up, and then matching the config exactly with the other plugged in.
I'm wondering at this point if something is wrong with the trigger on the older MCG-Pro.
I have a Mk2 Gunfighter with MCG-Pro that I purchased, and set up as a helicopter cyclic. I was able to program the trigger through the DevCfg software to provide a pulse button when flipped to allow for the switching of triggers in the DCS Ka-50 that is pretty realistic.
I have a second Gunfighter, Mk1 model, that I have had for a little longer, with a separately purchased MCG-Pro that I have set up for flying fighters.
I wanted to setup the Mk 1 model the same way as the Mk2, albeit with a completely separate Black Box. When I flashed the firmware, and loaded the profile, everything seems to work fine, except the trigger function. There is no pulse (button 24 on my config), and button 25 remains constantly on if the trigger is flipped down, unlike the Mk2. Also, the trigger on the Mk1 feels a lot more spongy, without a distinct click, unlike the newer MCG I have that works fine.
I've tried re-calibrating, as well as taking snapshots with DevCfg with the working stick up, and then matching the config exactly with the other plugged in.
I'm wondering at this point if something is wrong with the trigger on the older MCG-Pro.