356thFS_Melonfish Posted October 6, 2019 Posted October 6, 2019 (edited) HELP! I've just build a new pc, windows 10 and all shiny bits and bobs. i've plugged all of my devices into my pc as normal and they're detected in windows and so on, they're all connected directly, no hubs. i've loaded up IL2 and mapped all of my keys including my VKB Gladiator mkII, all the buttons and axis register when you click it for an input. BUT... when adjusting curves nothing is detected and in game NONE of the buttons are working. but i can map them just fine. my logitech throttle quadrants are registering and working fine, my TWCS and rudder pedals are fine. it's just the VKB. it's detected as Joy10 but maps just fine. what on earth is going on? i've test flown in clod and elite dangerous to make sure it was not the joystick and they're detecting and flying just fine (much to my relief) I literally built my pc so i could get decent frames in IL2 and now I can't fly in it. Help me Il2 kenobi, you're my only hope! Pete EDIT: Sorted it, hit the default button on IL2 and it zero'd everything then restarted windows properly. now everything has a different assignment but at least it detects and works! so If you get similar, Hit Default on the key map options. close Il2, do a shutdown /r on windows and then when rebooted remap your controls and fly like your pants are on fire. good hunting! Edited October 6, 2019 by Melonfish
Sokol1 Posted October 6, 2019 Posted October 6, 2019 Of just delete the file "devices.txt" in \data\imput\ folder, and start game for new controller detection. BTW - When you change Gladiator mode (1/2) the buttons assume new numbers. Example: in default mode (Red LED) trigger is button # 14, in mode 2 (Green LED) is # 16 and if "pinky" button is pressed # 15 and # 17. So if you start game with mode in 2 (Green LED) may think that buttons are unassigned.
356thFS_Melonfish Posted October 7, 2019 Author Posted October 7, 2019 16 hours ago, Sokol1 said: Of just delete the file "devices.txt" in \data\imput\ folder, and start game for new controller detection. BTW - When you change Gladiator mode (1/2) the buttons assume new numbers. Example: in default mode (Red LED) trigger is button # 14, in mode 2 (Green LED) is # 16 and if "pinky" button is pressed # 15 and # 17. So if you start game with mode in 2 (Green LED) may think that buttons are unassigned. Thanks for that, i'll try the devices.txt next time button wise yeah, regardless of what i mapped under either combat or navigation mode it wasn't registering. somewhat odd, but thankfully all working now. Pete
Sokol1 Posted October 7, 2019 Posted October 7, 2019 5 hours ago, Melonfish said: button wise yeah, regardless of what i mapped under either combat or navigation mode it wasn't registering. Did you test the buttons in Windows Game Controllers (joy.cpl) or VKB button tester? The only reason for joystick buttons not work in games is if they are not visible for Windows.
356thFS_Melonfish Posted October 7, 2019 Author Posted October 7, 2019 12 minutes ago, Sokol1 said: Did you test the buttons in Windows Game Controllers (joy.cpl) or VKB button tester? The only reason for joystick buttons not work in games is if they are not visible for Windows. it worked in windows just fine and as per the initial post in Clod and Elite dangerous too.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now