Gunfighter Mk II and MCGPro Folding Trigger configuration
Posted: Fri Dec 29, 2017 5:34
Hello fine Sirs and or Madams.
New recipient of Gunfighter B (Mark II), with Modern Combat Grip Pro (MCG-Pro), in Texas, USA. Overall extremely impressed with the finish, layout, and hand feel. But I have a few questions about properly configuring the folding trigger to act as one or more buttons, including what I read to be a button "hold press" behavior with the trigger up. Mine appears to do this with the trigger folded down.
I'll attempt to follow your 7-step tech support instructions:
1. Device is Gunfighter, B-connector orientation, Mark II base, with MCG-Pro stick, Cyrillic lettering
2. Firmware reported by VKBDeviceConfig v0.83.85 (NJoy32 v1.91) is "v1.917" in the little window at the top of the software.
3. One each #10 spring installed per main joystick X and Y axis.
4. Cam #10 (default, soft center) preinstalled upon receipt and not changed.
5. Software being used is VKBDeviceConfig v0.83.85 (NJoy32 v1.91).
6. Question is not about 'axes' per se but travel operation of the folding trigger. I did load up VKB_Joytester but it does not show anything but small movements of the X and Y axis as I play with the folding trigger, instead it registers button presses in the lower window, so I am omitting these screenshots in favor of those in the next step along with my description of what is happening below.
7. (And query): My problem or confusion is that I have been told that the folding trigger should act like a held button press in the "up" configuration, release in the "down" but not squeezed operation, then have the option of button action(s) along the travel as you actually compress the trigger. What my joystick seems to register is that "folded down" is the held press, which means this continues to be held when I compress and hit the stops for the next 2 presses. What I want, ideally, is "fold up" to be a held press, "fold down" to release that, then a small amount of compression on the trigger acts as one button, while a larger amount of compression to the actual trigger stop actuates another button.
Here is how my TEST page looks with the trigger flipped down, but not squeezed:
And here is how it looks fully compressed. Note that the #26 light does come on partially along the travel, and the #3 comes on toward the end of travel.
Here is how the Common-n-Axes / Axes2Buttons Page is currently configured. Upon original 'get' of the configuration from the joystick only the top box and "Safe" in the highlighted regions were checked. After I checked the other two, I did "Set" them up to the joystick. Not sure if I hit anything else in the process accidentally, but there doesn't seem to be anything I can change that would reverse the "Safe" polarity, just the button number to which it is assigned.
If I pull the report, I see this, which I think explains why what is called #27 for full trigger pull is showing up as logical button #3 on the Test page, maybe. This also I guess is seen on the next screenshot.
Lastly, besides wanting to change the polarity on what seems to be the folding action (down being pressed, not 'up'), I don't know how to assign these as controls that external programs e.g. games will actually see, aside from the current full trigger pull which does show up. If I go to the Profile page, Buttons tab, I see #3 indicated in the Logical Layer for #24 position (circled blue). But 25 and 26 show little "not used" popups if hovered over, which I believe means they have a 'physical' mapping (the joystick knows if they've been pressed) but won't inform Windows of that fact (???)
Respectfully, Richard.
(p.s. I did download and am attempting to read the manual, but walking me thru this single example would probably do a world of help to my understanding....I also freely admit I did not "SAVE" the current configuration when I first loaded up VKBDevCfg, so if I accidentally rolled the mousewheel or otherwise altered settings while flipping thru pages, the blame is on me....)
Edits: Trying to get images to show up. Also, from rrhode's post about assigning a button press to the maximum squeeze of the brake lever I think I can muddle thru the logical assignments to get buttons to show up in other programs now. I just still don't understand why my folding trigger flip down is showing as a physical held button, not flip up.
New recipient of Gunfighter B (Mark II), with Modern Combat Grip Pro (MCG-Pro), in Texas, USA. Overall extremely impressed with the finish, layout, and hand feel. But I have a few questions about properly configuring the folding trigger to act as one or more buttons, including what I read to be a button "hold press" behavior with the trigger up. Mine appears to do this with the trigger folded down.
I'll attempt to follow your 7-step tech support instructions:
1. Device is Gunfighter, B-connector orientation, Mark II base, with MCG-Pro stick, Cyrillic lettering
2. Firmware reported by VKBDeviceConfig v0.83.85 (NJoy32 v1.91) is "v1.917" in the little window at the top of the software.
3. One each #10 spring installed per main joystick X and Y axis.
4. Cam #10 (default, soft center) preinstalled upon receipt and not changed.
5. Software being used is VKBDeviceConfig v0.83.85 (NJoy32 v1.91).
6. Question is not about 'axes' per se but travel operation of the folding trigger. I did load up VKB_Joytester but it does not show anything but small movements of the X and Y axis as I play with the folding trigger, instead it registers button presses in the lower window, so I am omitting these screenshots in favor of those in the next step along with my description of what is happening below.
7. (And query): My problem or confusion is that I have been told that the folding trigger should act like a held button press in the "up" configuration, release in the "down" but not squeezed operation, then have the option of button action(s) along the travel as you actually compress the trigger. What my joystick seems to register is that "folded down" is the held press, which means this continues to be held when I compress and hit the stops for the next 2 presses. What I want, ideally, is "fold up" to be a held press, "fold down" to release that, then a small amount of compression on the trigger acts as one button, while a larger amount of compression to the actual trigger stop actuates another button.
Here is how my TEST page looks with the trigger flipped down, but not squeezed:
And here is how it looks fully compressed. Note that the #26 light does come on partially along the travel, and the #3 comes on toward the end of travel.
Here is how the Common-n-Axes / Axes2Buttons Page is currently configured. Upon original 'get' of the configuration from the joystick only the top box and "Safe" in the highlighted regions were checked. After I checked the other two, I did "Set" them up to the joystick. Not sure if I hit anything else in the process accidentally, but there doesn't seem to be anything I can change that would reverse the "Safe" polarity, just the button number to which it is assigned.
If I pull the report, I see this, which I think explains why what is called #27 for full trigger pull is showing up as logical button #3 on the Test page, maybe. This also I guess is seen on the next screenshot.
Lastly, besides wanting to change the polarity on what seems to be the folding action (down being pressed, not 'up'), I don't know how to assign these as controls that external programs e.g. games will actually see, aside from the current full trigger pull which does show up. If I go to the Profile page, Buttons tab, I see #3 indicated in the Logical Layer for #24 position (circled blue). But 25 and 26 show little "not used" popups if hovered over, which I believe means they have a 'physical' mapping (the joystick knows if they've been pressed) but won't inform Windows of that fact (???)
Respectfully, Richard.
(p.s. I did download and am attempting to read the manual, but walking me thru this single example would probably do a world of help to my understanding....I also freely admit I did not "SAVE" the current configuration when I first loaded up VKBDevCfg, so if I accidentally rolled the mousewheel or otherwise altered settings while flipping thru pages, the blame is on me....)
Edits: Trying to get images to show up. Also, from rrhode's post about assigning a button press to the maximum squeeze of the brake lever I think I can muddle thru the logical assignments to get buttons to show up in other programs now. I just still don't understand why my folding trigger flip down is showing as a physical held button, not flip up.