VPC Configurator Software

[Bear21]

Just want to give a heads up. I have Virpil stick, throttle, and pedals and have used a software version from 2020. It has worked fine, but I noticed since ED reworked controls that the dialog, in game especially, was laggy. When I recently bought the Varjo Aero and started using VR again, it was so laggy it was not useable. Turned out the culprit was old Virpil software; updated, and imported profiles, and now everything works fine. Just for info.

[dburne]

20 minutes ago, Bear21 said:

Just want to give a heads up. I have Virpil stick, throttle, and pedals and have used a software version from 2020. It has worked fine, but I noticed since ED reworked controls that the dialog, in game especially, was laggy. When I recently bought the Varjo Aero and started using VR again, it was so laggy it was not useable. Turned out the culprit was old Virpil software; updated, and imported profiles, and now everything works fine. Just for info.

 

Always good to stay updated with the Virpil software.

[Guest]

On 10/14/2023 at 11:06 PM, Bear21 said:

Just want to give a heads up. I have Virpil stick, throttle, and pedals and have used a software version from 2020. It has worked fine, but I noticed since ED reworked controls that the dialog, in game especially, was laggy. When I recently bought the Varjo Aero and started using VR again, it was so laggy it was not useable. Turned out the culprit was old Virpil software; updated, and imported profiles, and now everything works fine. Just for info.

I am happy all works great now and all, but the question is how did you manage to import profiles from 2020 software into current software? I thought profiles created in the older software had different file extensions so they could not be imported in the new software. Am I missing something?

[imacken]

Yep, I was thinking the same thing but didn’t want to ask!

[Double Dutch]

hello,

Last version of the software I have installed was v20220720_patch1.exe.

Can I install the 20230328 version of the software without breaking things (or in DCS)?

[imacken]

There is a new version out. 20240124.

Re 'not breaking things', I have never had an issue updating VPC software many times over the years, but there have been a couple of people who had their device IDs changed, and that does break the DCS binds.

I use JoyPro to get round that issue if it ever occurs - for reasons other than software update in my case - as it can restore your previous IDs or change DCS binds to the new one with a single button press.

[Snacko]

On 2/1/2024 at 4:02 AM, imacken said:

I use JoyPro to get round that issue if it ever occurs - for reasons other than software update in my case - as it can restore your previous IDs or change DCS binds to the new one with a single button press.

I just download the 0092 version of JoyPro for the first time.  But it looks like it has all of the source code in it?  And it crashed when merged simple rudder pedal relations.  And the log referred to a folder that is not on my system (D:\Dropbox\Programmierung\c#\JoyPro\JoystickProfiler\JoyPro\JoyPro\..)   That download has over 387 files...  Where can I download a package release for end users??

[imacken]

The builds are here

https://github.com/Holdi601/JoystickProfiler/tree/master/Builds

[hornblower793]

On 2/1/2024 at 9:02 AM, imacken said:

There is a new version out. 20240124.

Re 'not breaking things', I have never had an issue updating VPC software many times over the years, but there have been a couple of people who had their device IDs changed, and that does break the DCS binds.

I use JoyPro to get round that issue if it ever occurs - for reasons other than software update in my case - as it can restore your previous IDs or change DCS binds to the new one with a single button press.

This definitely makes JoyPro worthwhile - I have just had it happen changing the setup of the AH-64D grip and was able to migrate all the bindings in a matter of seconds

[imacken]

1 minute ago, hornblower793 said:

This definitely makes JoyPro worthwhile - I have just had it happen changing the setup of the AH-64D grip and was able to migrate all the bindings in a matter of seconds

I’ve been singing the praises of JP here for a long time. In so many ways, it’s an incredibly useful piece of software. 

[Cyborg71]

If I missed this I apologise.

Is it possible to swap virpil collectives without losing the control button binds?

For this example I have a fully configured Ah64 collective, but occasionally may wish to swap back to the sharka50. 

Does the virpil/dcs software recall the binds - or are they gone once the hardware is swapped.

With thanks,

 

[imacken]

Different hardware will require a different profile.  You can swap them over once you have it saved initially.

[Glide]

Just a heads up for Classic rudder pedal owners to perform regular maintenance on that post at the back.  I had mine work itself almost completely off (after 4 years of kicking), and no amount of calibration would cure the crazy rudder inputs I was sending.  The Standard spring managed to disconnect as well, and for a surprisingly long time I didn't notice.  Now, I have both the Strong and Standard springs on the unit. 

[kaltokri]

I need help.

I buyed Throttle CM3, Panel2 and SharKa50 Panel in 2021.
I configured everything and didn't touch it since then.

Now I buyed a Virpil Collective from a friend. It had a firmware from 2022.
So my VPC configuration tool was not able to configure the Collective.

So I downloaded the newest configuraton tool and did an update off all components firmware.
I connected only one device at a time.

After that the devices had default configuration. So I imported the profiles I had safed in 2021.

All buttons are working fine and the colors of the buttons are right. But no axes is working.

In the column Axes Source is only a ---. This don't look right.

In the manual I can not find an information how I need to configure the axes for each devive.

Can anyone help me please.

null

[kaltokri]

Ok, importing old profiles is a bad idea.

If I flash the firmware, create a new profile and calibrate the axes my ShaKa50 is fully working.

Unfortunately the MT-50CM3 shows only 3 axes. The mini stick is not working. How can I get it back?

[kaltokri]

I forgot to select the variant in the centre of the profile. Now all axes work. I just have to set everything up again. It's really frustrating.

[flanker0ne]

@Cyph3r

VPC_Software_Setup v20241226

signaled as a Trojan:Script/Wacatac.B!ml 

from Win Defender

Edited December 29, 2024 by flanker0ne

[Elf1606688794]

On 9/4/2018 at 2:36 PM, Cyph3r said:

 

It's already fully functional in the software! I just haven't got around to typing it up yet - as many people have already figured it out, I focused first on the features that haven't been described/used already I'll aim to get the shift/mode dial sections typed up by the end of the week.

Almost 7 years later and we still haven't made it to the end of the week. 

[julpeuz]

Hi guys,

I have a control panel 1, and I’d like to split one of the rotary knob axis into two separate axis : 1 axis from 0 to 50% of the physical position, and another one from 50 to 100%. So I can control the fluorescent lighting of the cockpit on one side, and the normal cockpit lighting on the other side. But so far no luck. Is that even possible ?

thanks in advance.

[Nightdare]

On 7/6/2025 at 6:33 PM, julpeuz said:

Is that even possible ?

thanks in advance.

 

In short: Nope

A rotary is not a pot, but basically 2 buttons, that are triggered twisting a knob their set direction

Unless you can find a 'click counter' in the Virpil software, to translate button presses to axis values, there is no way you can assign a 'value range'

You can us the rotary as a toggle though, <-Light 1 on/off | Light 2 on/off ->

 

 

[julpeuz]

On 7/7/2025 at 11:31 PM, Nightdare said:

 

In short: Nope

A rotary is not a pot, but basically 2 buttons, that are triggered twisting a knob their set direction

Unless you can find a 'click counter' in the Virpil software, to translate button presses to axis values, there is no way you can assign a 'value range'

You can us the rotary as a toggle though, <-Light 1 on/off | Light 2 on/off ->

 

 

Thanks for the answer, but I mean the potentiometer axis, not the digital encoders.

[Nightdare]

2 hours ago, julpeuz said:

Thanks for the answer, but I mean the potentiometer axis, not the digital encoders.

 

Major difference in those 2 

 

Ok

few points:

• I still use an OLD version of VPC software, 2023 I believe, no idea if this woks with newer versions
• I tried this on my trusty Gen 1 T50 Mongoost, no idea if this works on newer units
• You probably want to calibrate axes prior to changing values
• I haven't tried this in game, because I don't wanna fiddle with THOSE setting, but it seems to do what I want in Windows Joystick

 

This is what I quickly came up with screwing around like a headless chicken methodical programming:

 

Step 1: copy the axis you want to use as '2-parter'

You'll get an error about DirectX not allowing 2 axes with the same name

Rename the new Axis to an unused element, In my example P6 'Dial' is the original, P7 'Y' the duplicate axis:

 

Keep the axis ID's the same:

 

values set for P6 "Dial":

 

Note: I'm unsure if you have to use 50% output, seemed logical to me as you use half of the physical axis per logical axis 

As I stated, what I tried seems to do what you intend, try and see I guess?

 

Values set for P7 "Y":

 

 

Now you can increase the difference between value end for P6 (7912) and P7 (7913) allowing a bit of a deadzone between the 2 (Hell, you might be able to overlap as well)

You might also be able to reverse P6 values, then center would be its respective lowest value, and in physical operation it should operate like a speaker balance knob

But I'll leave that to you to figure out 

 

 

Good lick fiddling!

[julpeuz]

Wow thank you so much for taking the time to explain. 
 

I tried the way you describe, but from what I understood from the Virpil built in graph, it actually does the opposite :

The logical axis travels from 0 to 50% when moving the physical axis from 0 to 100%. But I didn’t tried in game so I may have misunderstood the graphs.

I don’t have my computer on hand until a few weeks now, I’ll try again when I get it back.

Thanks again.

[Nightdare]

5 hours ago, julpeuz said:

Wow thank you so much for taking the time to explain. 
 

I tried the way you describe, but from what I understood from the Virpil built in graph, it actually does the opposite :

The logical axis travels from 0 to 50% when moving the physical axis from 0 to 100%. But I didn’t tried in game so I may have misunderstood the graphs.

I don’t have my computer on hand until a few weeks now, I’ll try again when I get it back.

Thanks again.

 

What I saw in my windows was P6 activating from zero position on the physical dial, then stopping when it's end value was passed

and P7 starting to activate halfway open once it's start value was passed

 

I'll see if I can give it another whirl later today