MCG Pro Trigger problem
Moderator: AdminGroup
-
- Posts: 15
- Joined: Thu May 06, 2021 0:53
- Has thanked: 2 times
Re: MCG Pro Trigger problem
I'm afraid that I do not see the trigger axis with this profile. To be clear, I started VKBDevCfg-C.exe and then pushed the Default button. I then loaded this profile and pushed the SET button to load it into the device. I then closed VKBDevCfg-C.exe and started JoyTester.exe. I selected the MCG Ultimate device (since I have two other joystick devices on the same system) and then exercised the stick. I see X and Y movement but nothing from the brake lever or trigger axis.Screenshot below shows only the X and Y axes moving even though I moved all four.
- ZERO_Thunder
- Posts: 42
- Joined: Thu Apr 25, 2019 5:04
- Has thanked: 3 times
- Been thanked: 8 times
- Contact:
- ZERO_Thunder
- Posts: 42
- Joined: Thu Apr 25, 2019 5:04
- Has thanked: 3 times
- Been thanked: 8 times
- Contact:
Re: MCG Pro Trigger problem
Sorry I gave you wrong profile. Try this one
- Attachments
-
- MCG U trigger test.zip
- (1.17 KiB) Downloaded 128 times
-
- Posts: 15
- Joined: Thu May 06, 2021 0:53
- Has thanked: 2 times
Re: MCG Pro Trigger problem
OK, I put the trigger in the Armed position, pushed Default, and then loaded the profile and pushed SET. Then ran JoyTester. This time I was seeing the axis but the results were weird. With the trigger in either Safe or Armed the output level was zero. As I moved it from Armed to Safe it would go smoothly upwards to 65535 but would reach that level before the trigger got all the way to "Safe." Instead the output jumped discontinuously to zero and stayed there until the trigger reached the Safe position. Moving the trigger in the opposite direction did the same thing in reverse, that is, output of zero for the first part of the trigger movement, then a sudden jump to 65535, then tapering back to zero as the trigger reached the armed position. Screen shot is below. Note that I moved the trigger 7 times, not 14, to generate this scan. The 7 extra jumps are in the middle of each trigger movement, closer to the Safe end of the range of travel..
I also tried this starting everything with the trigger in the Safe position. When I did that the output level started at and remained pegged at 65535 no matter how much I moved the trigger. I haven't bothered to post a screenshot of that since there was nothing to see except constant output at 65535. Keep in mind that the problems I've been having are all occurring when the device boots up with the trigger in the Safe position.
I also tried this starting everything with the trigger in the Safe position. When I did that the output level started at and remained pegged at 65535 no matter how much I moved the trigger. I haven't bothered to post a screenshot of that since there was nothing to see except constant output at 65535. Keep in mind that the problems I've been having are all occurring when the device boots up with the trigger in the Safe position.
- ZERO_Thunder
- Posts: 42
- Joined: Thu Apr 25, 2019 5:04
- Has thanked: 3 times
- Been thanked: 8 times
- Contact:
-
- Posts: 15
- Joined: Thu May 06, 2021 0:53
- Has thanked: 2 times
Re: MCG Pro Trigger problem
OK. That helped with the weird axis behavior. See screenshot below.
However if afterwards I restart the device with the trigger in the SAFE position then the axis gets stuck on 65535 and won't move.
However if afterwards I restart the device with the trigger in the SAFE position then the axis gets stuck on 65535 and won't move.
- ZERO_Thunder
- Posts: 42
- Joined: Thu Apr 25, 2019 5:04
- Has thanked: 3 times
- Been thanked: 8 times
- Contact:
Re: MCG Pro Trigger problem
Every time you restart it on Safe the axis get stuck?
And every time you restart it on Armed the axis works?
And every time you restart it on Armed the axis works?
-
- Posts: 15
- Joined: Thu May 06, 2021 0:53
- Has thanked: 2 times
- ZERO_Thunder
- Posts: 42
- Joined: Thu Apr 25, 2019 5:04
- Has thanked: 3 times
- Been thanked: 8 times
- Contact:
Re: MCG Pro Trigger problem
Hi,
I had the same problem. @Ron61 pointed to me in another toppic to this place. My MCG folding trigger was set to "safe" and "armed" virtual buttons 28 and 25. Worked as intended but did not fit my demands. So I checked the "pulse" box and the buttons were not detected by DCS or Devcfg button testing. But I did not check at this point if powering up the blackbox with the folding triger set to active position makes a diference. I did check it today and yes, the same behaviour as in this tippic already described.
I made a last attempt to solve the problem. Luckily I have stored the default configuration as shipped from OEM. So I have loaded the default configuration and have send it to the blackbox.Then I made all changes again ( POV 1 as 4 way, tempo B, relative / POV 2 as 4 way, tempo B, relative / some changes to dedzone of the ministick POV 2 and setting the folding trigger to safe, armed and pulse options ). Then I calibrated both the base and MCG. It works now, for some reason, probably by my own fault there was an inteference somewhere caused by my experimenting.
It is worth folowing this path as the last resort. Hope it would help someone.
I had the same problem. @Ron61 pointed to me in another toppic to this place. My MCG folding trigger was set to "safe" and "armed" virtual buttons 28 and 25. Worked as intended but did not fit my demands. So I checked the "pulse" box and the buttons were not detected by DCS or Devcfg button testing. But I did not check at this point if powering up the blackbox with the folding triger set to active position makes a diference. I did check it today and yes, the same behaviour as in this tippic already described.
I made a last attempt to solve the problem. Luckily I have stored the default configuration as shipped from OEM. So I have loaded the default configuration and have send it to the blackbox.Then I made all changes again ( POV 1 as 4 way, tempo B, relative / POV 2 as 4 way, tempo B, relative / some changes to dedzone of the ministick POV 2 and setting the folding trigger to safe, armed and pulse options ). Then I calibrated both the base and MCG. It works now, for some reason, probably by my own fault there was an inteference somewhere caused by my experimenting.
It is worth folowing this path as the last resort. Hope it would help someone.
Re: MCG Pro Trigger problem
I am having this same issue with my Ultimate. I followed all the instructions here with the same results. Is there any resolution to this issue.
Re: MCG Pro Trigger problem
same problem here
- Attachments
-
- VKBSim Gunfighter Modern Combat Pro profile 1.zip
- (4.19 KiB) Downloaded 56 times
-
- Posts: 15
- Joined: Thu May 06, 2021 0:53
- Has thanked: 2 times
Re: MCG Pro Trigger problem
ZERO_Thunder wrote:We contacted our software engineer. Looking for the issue
More than a year since this problem was reported and a statement made that VKB would look into it. But still no information or resolution. I've had to just learn to live with the problem.
Who is online
Users browsing this forum: No registered users and 102 guests