Controller trim binds not working (keys work)

[Bostjan42]

I have tried various options to bind trim controls to my controller (VKB Gladiator NXT) and it doesn't work. It works fine in DCS and in the joystick testing utility.

I have seen tips on the forum that I should bind both the axis and the switches, which I did. Not working.

Deleting the binds and rebinding doesn't work.

The default keyboard binds work fine.

Anyone with similar issue/experience?

[dburne]

I was getting IL-2 set back up with my newer controllers yesterday and also struggled some getting trim recognized.

All I can say is keep trying, I eventually got it but can not recall exactly what I did to get it.

[Virus*]

Same issue here with virpil cm3 throttle and virpil t50 cm2 base and grip.

[kissTheSky]

If you mean stick keys do not work for trim controls, I think they’re not meant to be other than a handful of twin engine planes unfortunately. 
 

I've gone through the same exercise two weeks ago and could only make axes work for trim for majority of the planes. I forgot the member’s name but there’s a thread with sortable controls per plane spreadsheet, in which you should be able to see the planes with incremental (button) trims (mostly twin engine planes).

 

For my case, game was accepting button assignment, but then nothing was happening while I was in the plane. Once I saw the spreadsheet and tried one of the planes with incremental trim controls, they all started working.
 

I’m not sure if the controls/key mappings were always like this, or if it is broken with a recent update (I only had a computer capable of running IL-2 couple of months ago), but that’s my recent experience. It doesn’t make sense to me and I may be doing something wrong since I’m new to IL-2 GB, but it made me think my controller was broken. 

[Sokol1]

On 6/10/2021 at 12:18 PM, Bostjan42 said:

I have tried various options to bind trim controls to my controller (VKB Gladiator NXT) 

 

 

Rotaries on NXT base are not analog axes (potentiometer), but encoders, that send momentarily button press. Probable is need adjust their sensitivity, using VKB DevCFG software.

 

Other, don't forget that IL-2:GB series has more than one type of trim, some planes accept only button/key press, others button/key press and analog axes (potentiometer).

[NrthrnLtspilotkid233]

I am having same issue. Using Thrustmaster Airbus edition. And an X56 throttle. No matter which controller i try, or keyboard. Pitch trim will not respond to key presses or controller button presses. Have tried several aircraft as well. Nothing........

[cardboard_killer]

Perhaps screenshots of your bindings for trim would be helpful? As well as a copy of your file devices.txt

[Bostjan42]

The weird thing is on my end the keyboard controls work, so I can check if the plane supports that trim... the wheel on the left bottom side of my BF109 cockpit rotates when using keys, but not when using the joystick buttons.

 

devices.txt

Edited June 12, 2021 by Bostjan42
cropped screenshot

[cardboard_killer]

36 minutes ago, Bostjan42 said:

the wheel on the left bottom side of my BF109 cockpit rotates when using keys, but not when using the joystick buttons.

If you can attach either the current.map or current.actions file, too, that might help.

 

Here's a picture of my devices.txt:

 

 

As you can see I have a Gladiator stick (the older mkII version), device 0, and a CH Throttle Quadrant, device 1.

 

Here is a picture of my current.actions file that has to do with pitch (elevator) trim.

 

 

I normally use the CH Quadrant (aka joy1) for trim, buttons b10 and b11 (joy1_b10 and joy1_b11), but I just now went into the game and added the Gladiator buttons b5 and b8. I started a solo scenario on the ground with a Yak and tested all three controls I have assigned to it's elevator trim tab. I tested them by selecting the outside view and watching the tabs as I engaged the buttons. All controls moved the tab when I held down the appropriate button/key.

 

Check it the same way, ensuring that the "// Elevator trim axis" in your current.actions file has the Gladiator buttons mapped, then load up a Yak on the ground and see if the tabs move when you hold down the right Gladiator button.

 

With you only having one device, ensure that the trim axis is joy0_b# in the current.actions file, not just showing in the game.

Sometimes it can get confused if you have had other devices and you'll see joy1_b# instead. If that's the case simply replace the 1 with a 0.

 

EDIT: are you using some kind of "shift" key to make it to button 40/41 on you gladiator stick? That might be an issue.

Edited June 12, 2021 by cardboard_killer

[Bostjan42]

It looks fine in current.actions:

 

rpc_pitch_trim,                                   key_rcontrol+key_down/key_rcontrol+key_up,        0| // Elevator trim axis
rpc_pitch_trim,                                   joy0_b41/joy0_b40,                                0|
pitch_trim_switch_up,                             key_rcontrol+key_down,                            0| // Elevator trim switch: up
pitch_trim_switch_up,                             joy0_b41,                                         0|
pitch_trim_switch_dn,                             key_rcontrol+key_up,                              0| // Elevator trim switch: down
pitch_trim_switch_dn,                             joy0_b40,                                         0|

 

What is weird though is that I see the axis and the POV hat defined as 1 instead of 0. But all the other buttons work fine, so I'm not sure if this matters in my case.

 

On the topic of switch buttons: yes, I'm using the switch mode for the trim, but I have also tried it on the vanilla buttons with the same result (or rather lack thereof).

 

I did swap out my old T.16000m with the VKB GNX so maybe something borked when I did that. Can I delete some files to restore to defaults without reinstalling the whole game (reset to default in-game didn't work)?

[Bostjan42]

I have renamed the extensions to txt so that I can upload them... but here are the actions and map files.

current.actions.txt current.map.txt

[Sokol1]

4 hours ago, Bostjan42 said:

Can I delete some files to restore to defaults without reinstalling the whole game (reset to default in-game didn't work)?

 

Rename the file "devices.txt" in game folder ...\IL-2 Sturmovik Battle of Stalingrad\data\input

 

Start the game and test.

 

If asked to use/migrate other controller key bind's say no.

[cardboard_killer]

3 hours ago, Bostjan42 said:

I have renamed the extensions to txt so that I can upload them... but here are the actions and map files.

 

I'm at a loss. Try what Sokol1 recommended to see if starting fresh will help.

[MilitantPotato]

If you're trying to use the encoders as trim/radiator control, I just put up some config files to fix this. The issue is the encoders act as buttons and not an Axis. Il-2 will ignore key presses that happen too quickly. The VKBs send a press that lasts .04-.06ms which Il-2 just either completely ignores or if you spin quickly enough sometimes picks up.

 

The way to fix this is to set the encoders as an Axis in the software. I have several settings files available and can modify them at anyone's request.

 

Two just fix the encoders with different sensitivities, and the other 4 add double buttons with a button press.

Here's the forum post. 

 

Edited June 12, 2021 by Ryanair_MilitantPotato

[cardboard_killer]

50 minutes ago, Ryanair_MilitantPotato said:

The VKBs send a press that lasts .04-.06ms which Il-2 just either completely ignores or if you spin quickly enough sometimes picks up.

 

@Sokol1 mentioned this upstream, which is why I used my own Gladiator to see if it worked for trim axes, and they did. However, as I wrote, I'm using the older model Gladiator, not the NXT.

[Sokol1]

1 hour ago, Ryanair_MilitantPotato said:

The way to fix this is to set the encoders as an Axis in the software.

 

But remember that not all game trims can use (analog) axis as control, only "Stabilizer Adjust" of Bf 109 and some other planes. 

[MilitantPotato]

29 minutes ago, Sokol1 said:

 

But remember that not all game trims can use (analog) axis as control, only "Stabilizer Adjust" of Bf 109 and some other planes. 

This is true, but with some hassle you can use the software to do an axis and keypress on the encoder. Getting it bound in Il-2 is a nightmare, so I just have a hat for the planes that don't use analog control for radiators/trim.

 

Using A2B you can have the upper/lower/mid ranges of the virtual axis be a button press, but you need to disable the A2B before binding the encoders as an axis, then re-enable it to bind the "button" press.

Using these A2B settings, 67 and 70 need to be to set to NoF (Not a function) so the middle of the axis doesn't show IL-2 a button press.

 

There's probably a way to make it press the virtual button repeatedly but I've not figured that out.

Edited June 13, 2021 by Ryanair_MilitantPotato

[Bostjan42]

Renaming devices.txt did not improve the situation. I have even tried renaming the whole input folder. Also this only worked if I did an offline start as it seems these settings are stored somewhere in the clouds. Anyway... it didn't work.

I was testing mainly on the BF109 though... when I changed to the Yak and the P51 the trim worked... but not on the BF109. So it may only be dependant on the BF109 or some other planes which share its trim mechanism.

Edited June 13, 2021 by Bostjan42

[Bostjan42]

I have found a suitable solution. I have programmed the stick buttons in VKB Config Tool as keyboard keys (so RCtrl+Up and RCtrl+Down) and it works fine that way. Sadly I couldn't do it inside IL2, but this also works.

[Sokol1]

9 hours ago, Bostjan42 said:

Renaming devices.txt did not improve the situation. I have even tried renaming the whole input folder. Also this only worked if I did an offline start as it seems these settings are stored somewhere in the clouds.

 

Using a Stem version of IL-2GB?

For some games Steam Cloud save the controls assignment, what can cause confusion if user are not aware of this, eg.IL-2:CloD.

[Bostjan42]

1 hour ago, Sokol1 said:

 

Using a Stem version of IL-2GB?

For some games Steam Cloud save the controls assignment, what can cause confusion if user are not aware of this, eg.IL-2:CloD.

No, using the direct-from-the-developers version.