VKB key presses not seen

[No601Jab]

Installed a new mother board, disk, operating system etc, and reinstalled IL-2.

 

When I start the game a little window comes up saying I have a VKB joystick, I had one before on the previous instillation and would I like to use the same VKB settings? To which I respond yes!

 

Incidentally this approach worked with the Kanttorin Kone throttle.

 

However, though the key press settings for the VKB joystick are listed as before in the previous instillation, the game does not see the joystick, i.e. planes don't respond to any joystick inputs and I can't click and re do the functions to joystick buttons, as the game's settings page does not see any inputs from the VKB joystick.

 

Any, pointers, tips or suggestions would be very gratefully received.

 

Kind regards,

Jab

 

 

 

  

[-332FG-Gordon200]

I too have a new system with Windows 10 Pro and IL2 along with latest drivers and updates no mods. Game settings allow me to bind VKB joystick but has no effect in game. No response for pitch or roll.

[czech693]

Have you activated the VKB joystick through the VKB software?  Does it calibrate in the software?

[LukeFF]

I would also ask about this on VKB's Discord. They are very active there in helping to resolve these sorts of issues.

[czech693]

Since you did some major reinstalls, check you data/input/devices.txt to make sure you haven't a duplicate VKB joystick or exceeded the max limit on number of controllers (8 max).

Edited September 11, 2023 by czech693

[No601Jab]

Thank you Czech, thank you all for your suggestions to check out.   

[No601Jab]

Update 5 minutes later, thank you Czech , I had 7 lines in the devices.txt, but two of them related to an unused in IL-2 Razer Orbweaver, I deleted those two lines and it's all running smoothly.

 

Cheers Czech ?

  

[Hoss]

Just delete everything in the devices.txt file, it will all re-generate when you start the game again. Delete file, "REBOOT" check file is empty, start game, if it asks questions; answer them correctly. quit the game, and ensure the correct number of controllers are on the list for what you physically have plugged in. If it's good, go check that it actually works now. Try the "Global" tab and see if it accepts inputs,    then go and do tailored profiles for the planes you want to fly. You may need to go and redo all of them anyway, especially if you fly more than one plane.

This is my devices.txt file.... if I forget to start TARGET it will see my Stick and Throttle as individual devices, and stick/throttle will show up in the list. So if you are running a HOTAS software program, ensure you ALWAYS start it before you go in the game, especially if it combines your controllers into one device like TARGET does. Also, when you go to check your settings make sure the device columns in the keymapping GUI only show the devices you have plugged in and connected. Joy1, 2, 3, 4..... etc...

 

my devices.txt file

configId,guid,model|

0,,|

1,%220e2280d0-c0fa-11e9-0000545345440180%22,MFG%20Crosswind%20V2|

2,%22d53184a0-c0fa-11e9-0000545345440580%22,Thrustmaster%20Combined|

3,%225f4a10a0-2568-11ee-0000545345440280%22,Trimm%20Box_K51|

4,%22797235a0-f385-11eb-0000545345440180%22,Joystick%20V2.04 (BlackHog)

Now, if I forget to turn on TARGET the stick and throttle (separately) will be added to this list, as devices 5 and 6.

 

 

My in-game settings, in the keymapping column (Global)

I'll see

Joy 1 =  Crosswinds

Joy 2 =  is stick/throttle controls/combined

Joy 3 = K51 Trim box

Joy 4 = BlackHog

 

Joy2-button1.... guns (Stick)

Joy4-button6.... eject... etc... (blackhog)

Joy2-button-4.. battery ON... (Throttle)

 

Now if you mess up and any of those device.txt names change, it will make the game see another controller. So whichever device you mapped it to, will have changed.  If I forget to turn on TARGET Joy 2 settings may or may not work because I now have devices #5 and #6 on devices.txt, and joy 5, and 6 in the game keymapping GUI.... see what I mean.. device #2 will no longer respond, only 5 & 6 will, and they are not mapped in-game.... yet. I always go and clear this (device.txt) when I have a brain fart and start the game without starting TARGET. It's harder to accomplish in the other sim if you mess it up, but not impossible. and it has a different column for each device...

 

 

Good Luck. 

 

 

 

 

Edited September 11, 2023 by Hoss

[dburne]

Maybe if these guys are doing a re-write of some things they will scrap that controller setup and put something nice together. Identifying the devices by name would be a start, along with button assignments that can easily be found - press a button in the GUI and see what you previously assigned it to. Good first steps and more could be done. Raising button limit to 128 might help in some cases.

Edited September 11, 2023 by dburne

[czech693]

When you delete the devices.txt file it will regenerate, but the controller ID numbers will usually change.  That messes up the existing key mapping as the joystick number is changed.  Not a problem if you are using Target as that software will show the controller image and you select the button you are programming.  If you are assigning key fuctions to the controller in the sim it may force you to re-assign all the key settings. 

 

Whenever I get that pop-up message about keeping previous settings I close down the sim and go to the devices.txt file to see what has changed to cause that message.  Sometimes it is a controller that I added, but most often it is a duplicate of a previous controller and it's best to just delete the line for the latest controller and re-start and see if everything is back to normal.  You usually won't get the pop-up message after doing that.

Edited September 12, 2023 by czech693

[JG1_Vonrd]

22 hours ago, dburne said:

Maybe if these guys are doing a re-write of some things they will scrap that controller setup and put something nice together. Identifying the devices by name would be a start, along with button assignments that can easily be found - press a button in the GUI and see what you previously assigned it to. Good first steps and more could be done. Raising button limit to 128 might help in some cases.

+1 this!