Anyone got a clue with this Virpil control panel?

[Panzerlang]

Control Panel #2, the one with the landing-gear lever. In the Virpil config it very clearly shows it as having three positions (aka, 'button' presses). They are both logical and physical. 40, 41 and 42, corresponding to the three possible positions of the lever. Yet IL2 key-mapping shows the up and down positions as being "B29".

What am I missing here or is something broken/bugged?

TIA. ?

[dburne]

7 hours ago, Hetzer-JG51 said:

Control Panel #2, the one with the landing-gear lever. In the Virpil config it very clearly shows it as having three positions (aka, 'button' presses). They are both logical and physical. 40, 41 and 42, corresponding to the three possible positions of the lever. Yet IL2 key-mapping shows the up and down positions as being "B29".

What am I missing here or is something broken/bugged?

TIA. ?

 

Are the logical button numbers the same as the physical ones?

 

[Charon]

I'm betting Il-2 sees them as 28, 29, and 30. When you try to bind it, you leave the middle state (29), and Il-2 sees this button release before it sees the new button press.

 

Try binding 'up' by going from 'up to 'middle' rather than 'middle' to 'up', and likewise for the down position.

[VilsonFarias]

I removed the middle button action from mine. Now it's just up and down. The center position is "neutral" without any action assigned. 

[Yogiflight]

Il-2 does this with control panels. I am experiencing this issue with my VKB SEM module, which does have such levers and turning knobs with three or four positions. IL-2 doesn't recognize these several positions. Additionally I use the landing gear and the flaps lever as buttons for opening/closing the canopy and feathering the engines, but no matter how I set them, IL-2 always puts them to the direction, I don't want them to be.

[Panzerlang]

7 hours ago, Charon said:

I'm betting Il-2 sees them as 28, 29, and 30. When you try to bind it, you leave the middle state (29), and Il-2 sees this button release before it sees the new button press.

 

Try binding 'up' by going from 'up to 'middle' rather than 'middle' to 'up', and likewise for the down position.

You absolute star, it works. ?

Yes, moron moment, the middle position is "B29", so all I was doing was activating that each time I moved to UP and DOWN in the mapping.

Vilson, how does one remove a function? That was going to be my next attempt.

Thank you guys. ?

[Sokol1]

Leave assigned in that way, both up and down to B29.

Then open the current.action file in \Data \Input folder and change

Up for B30

Down for B28

 

flaps_up,                                         Joy#_b30,                                            0| // Flaps up
flaps_dn,                                         Joy#_b28                                             0| // Flaps down

 

Joy# = replace the # with the number the game assigned for the button panel, what is write before the _b29

[VilsonFarias]

20 hours ago, Hetzer-JG51 said:

Vilson, how does one remove a function? That was going to be my next attempt.
 

Use the Virpil Configuration Tool. In the Button section, select the button you want to remove, edit it and then remove the mapping information. You can use this video as reference: 

 

Although the latest version might be different, most of the concepts are still the same. Go to 4min 50sec, that's the mapping screen where I reset the mapping data.

 

 

One more thing that you might be interested: The only thing I still can't map are the rotary encoders. 

 

I tried both links below, I was able to create a virtual axis that works very well but I was not able to assign in the game because the Virpil control was also triggering the buttons involved in virtual axis creation. What does it mean? Let's suppose that when you turn the rotary encorder the buttons 50 and 51 are triggered (you can see they blinking on VPC tools). When you create the virtual axis these buttons will be monitored in order to increase or decresa the axis. Once you have the virtual axis created, if you turn the knob clockwise the axis will increase and if you turn it counter-clockwise you will reduce its value. It works perfectly, the movement is smooth and the values increase and decrease in the expected way (you will read in the forum that other approaches do work but you need to turn the knob over and over and over just to see small increments, it's useless). The problem is that when you turn the knob these buttons 50 and 51 are also triggered, so you have two different things going on: an axis changing and a button emitting the press/release events. Because of that, when you try to assign the axis in the game, the game always assign the key press to the control instead of the axis. I tried to assign the axis by editing the config files but I couldn't figure out what was the name for the axis. I tried different names but still no luck. Let me know if you figure out how to do that.

 

 https://forum.virpil.com/index.php?/topic/850-setting-delta-encoder-wheel-as-virtual-axis-and-hardcoded-axis-precision/&tab=comments#comment-9171  and the 

 

and 

 

Edited March 24, 2022 by VilsonFarias