Virpil Mongoose CM2 Throttle Issues

[Cunumdrum]

Hi all, I am having issues with setting up my CM2 throttle and hope someone can help me solve the issue. The problem I have is that the throttle axis are not registering in DCS so the throttle will not work at all. Below is what I have done to set it it:

 

• Downloaded Virpil VPC Software Setup [20200325]
  
• Updated firmware for the CM2.
  
• Configured the throttle axis in Virpil software and the throttle works all ok.
  
• Saved the profile in the Virpil software.
  
• Windows can see the throttle and all axis work ok.
  
• DCS can see the CM2 as Left VPC Throttle in three columns.
  
• I can not re assign the correct axis in DCS to the throttle though the buttons on the throttle are recognized in DCS and work.
  
• Moved the CM2 to different USB ports on the PC with no difference.
  

Does anyone have any idea as to what could be the issue or what I have missed?

[bad_turbulence]

DCS can see the CM2 as Left VPC Throttle in three columns.

 

Can you screen print this for clarification. Also, are you in Sim mode or Game mode? And does DCS show the throttle movement in the controls setup and just not work in-flight or does it not show the little horizontal bar moving when you work the throttle fore and aft?

[HC_Official]

watch this and do not tick the 32 button split tick box when creating profile

Edited May 16, 2020 by HC_Official

[Cunumdrum]

I am in SIM mode and the control panel would not assign the throttles to RX.RY values. I have sorted most issues now.

The three profiles in DCS was because I enabled the split virtual device by 32. ( I think)

 

I have uninstalled the Virpil software and reinstalled and followed your tutorial by the letter. I did not select split by 32 and now have only one column in DCS.

 

Both throttles are working now but I have to invert their axis for every aircraft in DCS control panel, Axis Tune. Is that normal? DCS recognizes each throttle.

One last question, I have the latest CM2 so do I have to change anything in the Virpil software in the double axis lock? My default: Button 8 which is the slider for locking the throttles. Button mode is on, SA is 1, DA is 2, and DZ is 4. Really appreciate your help getting this sorted and you tutorials are great.

Edited April 20, 2020 by Cunumdrum

[HC_Official]

Yep, how DCS handles axis is ass backwards sadly

Leave the the throttle handles lock button ID as is, if you want to learn more, watch more of the tutorials

DZ only matters if you are unlocking the handles and want to keep them close together

[Cunumdrum]

Thanks for the guidance it's much appreciated. I have all you tutorials booked marked to go through. Thanks for putting them together they are a great help.

Cheers and stay safe.

[SVgamer72]

HC_Official is the hero we need!!

 

 

Sent from my iPhone using Tapatalk

[Gman109]

HC_Official is the hero we need!!

 

 

Sent from my iPhone using Tapatalk

 

Agreed, Havoc Clan has been instrumental in getting so many new (and old) Virpil product users up and running, as well as helping longer term users with new software and hardware info.

[bad_turbulence]

I am in SIM mode and the control panel would not assign the throttles to RX.RY values. I have sorted most issues now.

The three profiles in DCS was because I enabled the split virtual device by 32. ( I think)

 

I have uninstalled the Virpil software and reinstalled and followed your tutorial by the letter. I did not select split by 32 and now have only one column in DCS.

 

Both throttles are working now but I have to invert their axis for every aircraft in DCS control panel, Axis Tune. Is that normal? DCS recognizes each throttle.

One last question, I have the latest CM2 so do I have to change anything in the Virpil software in the double axis lock? My default: Button 8 which is the slider for locking the throttles. Button mode is on, SA is 1, DA is 2, and DZ is 4. Really appreciate your help getting this sorted and you tutorials are great.

yep, split by 32 not only replicates the columns x3 in controls but it will also affect throttle axis percentages requiring re-calibration.

[HC_Official]

yep, split by 32 not only replicates the columns x3 in controls but it will also affect throttle axis percentages requiring re-calibration.

 

 

any creation and saving of a new profile to the device will require re-calibration as it wipes the device calibration upon profile being sent to the device

[Bear21]

Please not the latest version of the software also writes to devices when you creat a new profile. Don't think the old versions did and this caught me off guard.

 

Have watched all your videos HC, they are indispensable!

[HC_Official]

This is not a problem I am at a loss why you think it is

[ViFF]

Has anyone experienced problems with physical buttons of the hats and rotaries all of a sudden returning incorrect physical buttons?

 

It seems intermittent and I can't find where this is coming from. Everything is working fine for a while until all of a sudden some of the hat buttons and rotaries go into "crazy mode" and will stay like this for some time through multiple unplugging and plugging back in.

 

Example: everything is working fine and all of a sudden physical button 16 starts to return physical buttons 17, 20, 21.

 

Another example is the rotaries returning both physical buttons when rotated in whichever directions.

 

As far as I can tell the transfer to the logical buttons (what windows sees) is working properly i.e. the problem is carried over, but does not seem to be the source of the problem.

 

I reinstalled the VPC Software Suite, flashed the firmware and created a new profile including re-calibrating all the axis as per the instructions for updating firmware.

 

Watching this closely now if it will repeat.

 

As a side note, I got the throttle a couple of weeks ago and it arrived pre-installed with a default profile and the latest firmware (v200325) so I was pleased to discover that after I had installed the VPC software suite prior to connecting for the first time, everything was working and beautifully calibrated from the get-go.

 

Appreciate if anybody could share from his experience.

 

Cheers!

Edited August 25, 2020 by ViFF

[imacken]

In my experience of several Virpil devices, what happens with physical button activations in the software is a mystery at times, and largely irrelevant. What is important is what Windows sees, i.e. the logical buttons.

As long as that is behaving correctly, you are good to go!

[HC_Official]

Has anyone experienced problems with physical buttons of the hats and rotaries all of a sudden returning incorrect physical buttons?

 

It seems intermittent and I can't find where this is coming from. Everything is working fine for a while until all of a sudden some of the hat buttons and rotaries go into "crazy mode" and will stay like this for some time through multiple unplugging and plugging back in.

 

Example: everything is working fine and all of a sudden physical button 16 starts to return physical buttons 17, 20, 21.

 

Another example is the rotaries returning both physical buttons when rotated in whichever directions.

 

As far as I can tell the transfer to the logical buttons (what windows sees) is working properly i.e. the problem is carried over, but does not seem to be the source of the problem.

 

I reinstalled the VPC Software Suite, flashed the firmware and created a new profile including re-calibrating all the axis as per the instructions for updating firmware.

 

Watching this closely now if it will repeat.

 

As a side note, I got the throttle a couple of weeks ago and it arrived pre-installed with a default profile and the latest firmware (v200325) so I was pleased to discover that after I had installed the VPC software suite prior to connecting for the first time, everything was working and beautifully calibrated from the get-go.

 

Appreciate if anybody could share from his experience.

 

Cheers!

odd behaviour indeed, what the the device plugged into ? USB on motherboard (best) or thru a HUB?

I would suggest trying a different USB port first to see if there is some weird power issue causing this (motherboard if not already using the motherboard USB)