Virpil MT-50 CM2 4-way hats always trigger push function in parallel

[shagrat]

I got my Virpil MT-50 CM2 and when I try to configure the buttons all push hats will always "press" the push button together with any of the 4 directions so I get up+push, right+push, down+push, left+push and push, instead of up, right, down, left and push.

Unfortunately this means I cannot use the push button, as it would trigger everytime I use the hat.

I checked the cabling etc., but all seems ok. The fact any documentation or manual to the configurator does not make it easier to troubleshoot this.

 

It would be nice to have the manual included in the Confuguration Tool installer!:book:

[RogueSqdn]

That's just the physical button showing in VPC's config tool. If you look at the joystick tester, that doesn't happen.

[shagrat]

That's just the physical button showing in VPC's config tool. If you look at the joystick tester, that doesn't happen.

It did, actually show in the tester, the Direct Input Viewer and DCS, until I updated to the newest software release, 20 min ago and started over!

Seems the version from July shown on the download page messed something up.

Now with the one from 30 Sep 2019 it works as described... :doh:

 

Anyway thanks for the heads up and quick response.

[RogueSqdn]

It didn't occur to me it might've been in an older FW. I'm using 1105.

 

My problem now is trying to figure out an easier way to move the Barometric Pressure knobs MUCH faster than the default. In Nevada it takes FOREVER to get to say, 28.15 from 29.92.

 

I'm fiddling with Joystick Gremlin right now, but I think I may end up having to go with Autohotkey. I unfortunately lost my AHKs in a hard drive crash a few months back.

[randomTOTEN]

Why would you use QFE in Nevada? They're probably using QNH out there anyways.

[RogueSqdn]

Well, I believe pressure is set wrong in all these Nevada missions. To get the altimeter to show 0 at field level you have to go all the way down to 28.15 or so (and tower tells you that level). But if QNH is being used, the tower should be reporting that. I'll have to look up the Nellis altitude above sea level.

 

I have rebuilt an AHK script to help with this. I use the push function of an encoder knob as a modifier in DCS so that the vJoy buttons only move the knob in DCS if I'm pushing the knob AND turning it.

 

This script requires CvJoyInterface.

 

#include CvJoyInterface.ahk
#SingleInstance, force
#Persistent

; Create an object from vJoy Interface Class.
vJoyInterface := new CvJoyInterface()

; Was vJoy installed and the DLL Loaded?
if (!vJoyInterface.vJoyEnabled()){
; Show log of what happened
Msgbox % vJoyInterface.LoadLibraryLog
ExitApp
}

myStick := vJoyInterface.Devices[1]

; End Startup Sequence
Return

; Hotkeys


2Joy31::
Loop, 650
{
myStick.SetBtn(1,1)
Sleep, 5
myStick.SetBtn(0,1)
}
  return
return



2Joy32::
Loop, 650
{
myStick.SetBtn(1,2)
Sleep, 5
myStick.SetBtn(0,2)
}
  return
return

 

 

 

EDIT: So upon further inspection, it appears the issue is that the tower's reporting QFE instead of QNH. It looks like the QNH is still shown in the briefing screen, though, so I'll have to go with that. I still plan to keep this script active at system startup though, in the event I need it.

Edited December 8, 2019 by RogueSqdn

[RackMonkey]

QNH is the norm

 

Why would you use QFE in Nevada? They're probably using QNH out there anyways.

 

You right, we use QNH here. I've lived in Las Vegas for 30 years and flow in and out of every airport and base in the valley and I have never heard of anybody using QFE.

[Andy t]

I remember reading somewhere to set the rotaries to "bufferred" in the button assignment. That should make the keypresses fire faster.

[RackMonkey]

I remember reading somewhere to set the rotaries to "bufferred" in the button assignment. That should make the keypresses fire faster.

 

That doesn't make it fire any faster, but if you turn the encoder 20 clicks, all 20 are in a buffer and the bug will move 20 degrees. In the unbuffered state the bug would stop moving as soon as you stop turning the encoder.

 

The trouble with buffered is that you can end up way past the heading you intended to set and have to come back the other way.

[Costas_Ch]

@shagrat did you solve this issue? I just got my WarBRD with Constellation Alpha and the MT-CM3 and I have exactly the same behaviour as you described. The Joystick Tester shows only only key press but DCS recognises the physical button middle press as well (exactly as you described).

Thanks.

[shagrat]

vor 6 Stunden schrieb Costas_Ch:

@shagrat did you solve this issue? I just got my WarBRD with Constellation Alpha and the MT-CM3 and I have exactly the same behaviour as you described. The Joystick Tester shows only only key press but DCS recognises the physical button middle press as well (exactly as you described).

Thanks.

For me the root cause was the wrong/old software version.

See my other post:

https://forums.eagle.ru/topic/219917-virpil-mt-50-cm2-4-way-hats-always-trigger-push-function-in-parallel/#elControls_4091131_menu

[MIghtymoo]

Got the CM3 Throttle for Christmas and have the newest FW and software installed. All in all very satisfied.

But, have the same problem as the original poster. Very annoying to not be able to use the hat push buttons.

If you map the push button in DCS and use the hat, it register the push button when returning the hat to center.

Workaround is unmapping the push button from logical windows button.

Would love to see if someone has a solution for this.

[Rongor]

This also happens on my Virpil collective pitch grip hats and it seems to be a bad design of the mechanical contacts. It's simply hard to not accidently push the center down while moving the hat in one of its directions.

As said, the only solution seems to not use (not bind) the depress input.