VKB Gunfighter Mk II B and MCG-Pro Conflict with Razer Synapse
Posted: Sat Dec 15, 2018 21:50
Just FYI, in case anyone else has experienced similar and this post could be of aid. I do not need assistance. The [TL;DR] is: either deactivate Synapse or don't have Razer devices on same hub as your VKB gear, if you experience randomness.
I have the Gunfighter Mk II (B connector) with a Dec 2017 first US batch MCG-Pro (Cyrillic). I am still on VKBDevConfig 0.87.05, and firmware 1.94.9 -- not sure if those are the most current, but I seem to be ok and won't update typically unless I have problems or I read there are significant new features to take advantage of. The rest of my control scheme is an X-56 throttle (the older Saitek build), new Slaw Viper RX pedals, KB and mouse obviously (both Cougar, running their UIX software, 700M and 700K), and I also have an Orbweaver Chroma running the Razer Synapse SW v2. The Orbweaver and VKB joystick (through its black box of course) are plugged into the same powered hub, and the X56 throttle is plugged into its own independent USB hub as that device tends toward a lot of random button press issues if underpowered.
The Slaws are new, and I just finished phase 1 of my chair build and was redoing all my control schemes in Elite Dangerous, with the addition of the pedals for yaw now instead of previous use of the Gate Cntl hat. It's immaterial to this post, but to show off the chair because I gotta:
(Yes, I know my desk is a complete mess right now.)
Anyway, as I was testing bindings playing tutorials I kept having random events trigger that were not associated with controls on the throttle - but on the VKB stick. In game it was things like silent running, ship lights, etc. So I exited out of the game and went into the VKB Button Tester program. The throttle tested fine, no random presses as I actuated it and wiggled finger hats and such. Ditto the new Slaws (no buttons to press just axes). But the VKB stick was randomly throwing buttons 9, 18, and 23 usually as a group, all down then up but maybe not in the same order, as I actuated the stick axes. There was no clear correlation like it was always after max X deflection or a particular arc around the compass, seemed perhaps a bit more related to speed of traverse or associated with a direction reversal / center crossing, if anything. 9,18, and 23 just happen to be the "click down" of 3 different 4-way-plus-press hats: Reset (thumbrest), PC (stick heat bottom center), and Gun/PC (index finger on right side). I was initially worried I had an issue with a loose cable and/or needed to upgrade firmware, but then I decided to just close Razer Synapse and try again.
Buttons stayed totally silent with stick actuation. (Work when I press them intentionally though - obviously.)
So....in this case, I suspect simply software conflict. It may be ok to simply move the plug of the Orbweaver off to a different location than the same hub the VKB stick is on but leave Synapse runnning, but as I don't use the Orbweaver when flying anyway (that's more for shooter games when I stow the HOTAS) turning off Synapse is a small price to pay when I decide to fly.
Hope this post might help someone.
I have the Gunfighter Mk II (B connector) with a Dec 2017 first US batch MCG-Pro (Cyrillic). I am still on VKBDevConfig 0.87.05, and firmware 1.94.9 -- not sure if those are the most current, but I seem to be ok and won't update typically unless I have problems or I read there are significant new features to take advantage of. The rest of my control scheme is an X-56 throttle (the older Saitek build), new Slaw Viper RX pedals, KB and mouse obviously (both Cougar, running their UIX software, 700M and 700K), and I also have an Orbweaver Chroma running the Razer Synapse SW v2. The Orbweaver and VKB joystick (through its black box of course) are plugged into the same powered hub, and the X56 throttle is plugged into its own independent USB hub as that device tends toward a lot of random button press issues if underpowered.
The Slaws are new, and I just finished phase 1 of my chair build and was redoing all my control schemes in Elite Dangerous, with the addition of the pedals for yaw now instead of previous use of the Gate Cntl hat. It's immaterial to this post, but to show off the chair because I gotta:
(Yes, I know my desk is a complete mess right now.)
Anyway, as I was testing bindings playing tutorials I kept having random events trigger that were not associated with controls on the throttle - but on the VKB stick. In game it was things like silent running, ship lights, etc. So I exited out of the game and went into the VKB Button Tester program. The throttle tested fine, no random presses as I actuated it and wiggled finger hats and such. Ditto the new Slaws (no buttons to press just axes). But the VKB stick was randomly throwing buttons 9, 18, and 23 usually as a group, all down then up but maybe not in the same order, as I actuated the stick axes. There was no clear correlation like it was always after max X deflection or a particular arc around the compass, seemed perhaps a bit more related to speed of traverse or associated with a direction reversal / center crossing, if anything. 9,18, and 23 just happen to be the "click down" of 3 different 4-way-plus-press hats: Reset (thumbrest), PC (stick heat bottom center), and Gun/PC (index finger on right side). I was initially worried I had an issue with a loose cable and/or needed to upgrade firmware, but then I decided to just close Razer Synapse and try again.
Buttons stayed totally silent with stick actuation. (Work when I press them intentionally though - obviously.)
So....in this case, I suspect simply software conflict. It may be ok to simply move the plug of the Orbweaver off to a different location than the same hub the VKB stick is on but leave Synapse runnning, but as I don't use the Orbweaver when flying anyway (that's more for shooter games when I stow the HOTAS) turning off Synapse is a small price to pay when I decide to fly.
Hope this post might help someone.