Virpil CM3 Throttle : Flaps Lever Issue

[Mungee]

Is there anyone out there who has the Virpil CM3 throttle and who has got the (specific) 'flaps lever' axis to work in IL-2 : Great Battles?

 

After finding that IL-2 : Great Battles' Key Mapping doesn't "see" the 'flaps lever' axis when moved backwards/forwards, I used the Virpil software to create a simulated button on either end of the 'flaps lever' axis - I still can't get it to "see" the simulated buttons (the Virpil software definitely shows the "simulated buttons" on either "end" of the 'flaps lever' axis).

[dburne]

3 hours ago, Mungee said:

Is there anyone out there who has the Virpil CM3 throttle and who has got the (specific) 'flaps lever' axis to work in IL-2 : Great Battles?

 

After finding that IL-2 : Great Battles' Key Mapping doesn't "see" the 'flaps lever' axis when moved backwards/forwards, I used the Virpil software to create a simulated button on either end of the 'flaps lever' axis - I still can't get it to "see" the simulated buttons (the Virpil software definitely shows the "simulated buttons" on either "end" of the 'flaps lever' axis).

 

There are two steps to adding a button.

First is the physical button, then you have to add a logical button to the physical button. The logical button is what windows and the game will see.

Check out this tutorial, it should be covered in there.

 

Edit: Look like it starts around the 27 minute mark.

 

 

Edited February 24, 2021 by dburne

[Mungee]

I’ve created the emulated/simulated buttons on either end of the flaps lever axis (on the Virpil throttle) - the Virpil software “sees”” these, and I can bind them to the “flaps up” and “flaps down” buttons in IL-2 Sturmovik: Great Battles - but when I move the flaps lever (on the Virpil throttle), when I’m in the sim, the flaps don’t move!

[Sokol1]

In what plane, some have different flap operations, so may you are testing in the wrong plane fo this set.

- Press once for Down or Up : IL-2, Spitfire...

- Press and hold until desired angle:  Lagg-3, Bf 109...

- Press sequential (flaps with more than two defined positions)- Ju 87 Stuka, Fw 190...

Edited February 28, 2021 by Sokol1

[Mungee]

I was trying to activate flaps in the LaGG-3.

 

With my previous throttle (Saitek X-55) I could hold down a particular toggle switch and the flaps would lower until I reduced the pressure on the toggle switch - pushing it up raised the flaps for as long as I was exerting upward pressure on the switch.

 

I would have thought that when my Virpil flap lever axis is in the 0% - 20% zone (or the 80% - 100% zone on the opposite end of the axis) - with (flap) buttons emulated/simulated on either end of the axis = the flaps would move and when it came out of that area the flaps would stop moving - but they don't move at all when in these two zones (the extreme sections of the flap lever axis movement)

Edited February 28, 2021 by Mungee

[Sokol1]

I test setting (in JoyToKey) my stick throttle axis for press keys (arrow up and down) at end or axis course and use this keys for "Flaps up" and "Flaps down" commands 

and work well for LaGG3 flaps.

 

Look if in VirPil software you have set the axis bands for press a physical  button, e.g. #50 and then in right white table set the correspondent logical  button, that can by #50 or any other not used up to 64 (Bo"X" limit).

 

The logical button is the that will do action in game controls.

 

 

[gnat]

For anyone else who was stumped like me, the key here (if you've already created the logical/simulated button for the desired physical button) is that you can't have more than 64 logical buttons (per device?). I had to delete several preexisting logical buttons in the VPC configuration tool to make room for the logical buttons I created for my flaps axis. In my case, I deleted the logical buttons that were assigned to the different mode selector settings. To test whether IL-2 is reading your logical button correctly, make sure that you see the correct button number in the IL-2 settings menu (e.g., if the logical button is "Button 20" in the VPC configuration tool but you see "POV-90" in the IL-2 key-binding menu, then something is wrong).

[Hoss]

the button press has to be held down for flaps, cowls, radiators for as long as you need to adjust them.  See if your flaps work with the Mustang, it's a momentary press because the flaps are incremental.

 

[ericandi]

On 11/28/2021 at 5:30 PM, gnat said:

For anyone else who was stumped like me, the key here (if you've already created the logical/simulated button for the desired physical button) is that you can't have more than 64 logical buttons (per device?). I had to delete several preexisting logical buttons in the VPC configuration tool to make room for the logical buttons I created for my flaps axis. In my case, I deleted the logical buttons that were assigned to the different mode selector settings. To test whether IL-2 is reading your logical button correctly, make sure that you see the correct button number in the IL-2 settings menu (e.g., if the logical button is "Button 20" in the VPC configuration tool but you see "POV-90" in the IL-2 key-binding menu, then something is wrong).

This must be the cause of my issue with the Virpil CM3 throttle. Most of the buttons and switches on the throttle base are working in the aircraft even though they are being recognized in the IL-2 key bindings set up screen. I definitely have more than 64 logic buttons between all of the HOTAS hats, buttons, switches, and dials on the throttles plus everything on the base. 

[Sokol1]

Quote

I definitely have more than 64 logic buttons between all of the HOTAS hats, buttons, switches, and dials on the throttles plus everything on the base. 

 

The 64 (logical) buttons limits is per USB controller.

 

Virpil throttle don't surpass this number in Mode 1, but surpass when other modes (2-5) are used.

 

[Dallas88B]

On 11/29/2021 at 8:30 AM, gnat said:

deleted the logical buttons that were assigned to the different mode selector settings.

That is an excellent idea... thank you for that.

So I did what you suggested and then I have created a IL2 Profile that I load for IL2 and this stays within the 64 logical buttons limits.

Plus a different profile for DCS that takes advantage of the 128 logical button limit DCS uses.

Excellent. Thanks again.

[Panzerlang]

It would be nice if the devs (a dev) could re-visit the key-mapping part of the game and revamp it so that twist-buttons and axis controls could be made to mirror correctly (eg, a real control in a cockpit can be mapped realistically to a hardware device etc). Example, the ability to map an axis lever on my Saitek quadrant to the canopy crank-wheel in the FW190 cockpit. So much stuff on my Virpil gear remains useless, which is a shame.

But yeah, it's very niche and probably not worth the devs' time and resources, I get that.

Upping the limit from 64 to a 128 would be handy though. Easy? Dunno.

[Dallas88B]

On 2/25/2021 at 2:53 AM, Mungee said:

Is there anyone out there who has the Virpil CM3 throttle and who has got the (specific) 'flaps lever' axis to work in IL-2 : Great Battles?

 

I realise your post was a while ago, but did you get this sorted out?

 

 

[gnat]

4 hours ago, Dallas88B said:

 

I realise your post was a while ago, but did you get this sorted out?

 

 

You have to give the flaps lever ranges and assign simulated buttons to those ranges. IL2 doesn't have a flaps axis, so whatever you bind in game must function as a button press.

[Dallas88B]

1 hour ago, gnat said:

You have to give the flaps lever ranges and assign simulated buttons to those ranges

 

Yep that's it!

Sorry my post was ambiguous, I didn't know if you had sorted it.

I was going to write up the method with some screenshots and so on - if you had not been able to get it sorted. But you have - so Yay !

[dburne]

Yeah Virpil's axis to button feature is a wonderful thing.

[Mungee]

On 4/28/2022 at 4:48 AM, Dallas88B said:

 

Yep that's it!

Sorry my post was ambiguous, I didn't know if you had sorted it.

I was going to write up the method with some screenshots and so on - if you had not been able to get it sorted. But you have - so Yay !

I really would appreciate you writing up the method (with screenshots etc) - I did try configuring the flaps lever using the Virpil software but didn't succeed!

[Dallas88B]

15 hours ago, Mungee said:

I really would appreciate you writing up the method (with screenshots etc)

 

@MungeeOK, this is what I did and it works fine for me for the Tempest, Spitfire and LA5 FN

 

See this https://forum.il2sturmovik.com/topic/69886-virpil-cm3-throttle-flaps-lever-issue/?do=findComment&comment=1064488 where @Sokol1 points out that different planes have different flap operations

 

I am using latest firmware 20220304 and this corresponds to the VPC configuration too software too. Previous versions have a different Graphical User Interface.

 

At the risk of stating what you already know, it is really worthwhile using the VPC Configuration Tester to export known copies of the configuration of the device, just in case you need to go back to a known good state if you screw things up by mistake.

 

I have profile copies like this example list shown below. Note the file name is meaningful and I included a text file in the supporting folder (readme.txt) that is just an explanatory note to myself for later. (I have profiles for DCS too... DCS can support 128 buttons and I use all the mode settings....  plus I have separate profiles for IL2)

 

 

So, first thing, in the VPC configuration tool, select PROFILE and then EXPORT PROFILE TO FILE to save the current state of the Virpil throttle.

 

Then, you can't have more than 64 logical buttons (per device ie: per USB controller) in IL2. (see Note 1 below)

I had to delete several preexisting logical buttons in the VPC configuration tool to make room for the logical buttons I created for my flaps axis. In my case, I deleted the logical buttons that were assigned to the different mode selector settings for mode S2, S3, S4 and S5.

In my config I kept mode 1 and assigned it to push buttons as I wanted. (Lights Nav, Lights Landing, SRS radio Dialog, Park brake etc)

To do this start the VPC configuration too. Make sure the correct device is selected from the list (at top left - mine has only one VPC device "L-VPC Throttle MT ....." ) Then click on "BUTTON" and on the list at the right you can delete  the logical buttons that were assigned to the different mode selector settings to free up keys in the button range up to 64. (Highlight the entry right click choose delete)

Once that is done choose "AXIS" and select the rz axis (maybe just move the flaps lever to confirm you have selected the correct axis) it will now be highlighted in blue

Double click the highlighted row and then in the axis to button section put a tick in the 0-20% range and another in the 81 -100 percent range

Now hit ESC key close this dialog to go back.

 

You will see the new buttons assigned (here physical 73 and 64). As you can see in the list, these correspond to Logical Buttons 57 and 58

Click on SAVE VPS Device to send this configuration to the CM3 throttle.

Open and then use the VPC Joy Tester app to check that the logical buttons are being produced when you move the flaps lever. Map these buttons to IL2 using the games keymapping dialog.

 

 

Don't forget select PROFILE again and then EXPORT PROFILE TO FILE to save the new profile to a new suitably named file.

 

Note1: you can use Joystick gremlin or the like to get around this but that is another story - I have not found the 64 limit an issue in IL2 and I connect the CM3 throttle and VKB GF stick direct.

 

 

 

 

Edited May 3, 2022 by Dallas88B