Ru55ell Posted October 22, 2021 Posted October 22, 2021 Since the update I'm having issues with the throttle bind to my X-56 I've noticed that in a few aircraft (Spitfire, P-51, UH-1H only checked so far) that there is a red exclamation against the throttle axis and I am unable to get rid of it despite me clearing my existing keybinds. I've done some testing and found that disabling the warthog throttle lua files (adding .old to the end of it) has worked with the P-51 As I can only see the devices I have in the keybinds this seems to be the only workaround to clear the conflicts for throttle and collective. I'll have to edit the other devices so that only the ones I have are in the input folder of the relevant aircraft edit disabling the lua files for the throttle devices I don't have worked for the UH-1H too, so the workaround is to disable the input lua files of devices that I don't have as I can't get access to devices that are not connected, and these devices seem to have the conflicts and the cause of the issues.
Lange_666 Posted October 24, 2021 Posted October 24, 2021 I guess you have an Oculus headset attached. There's no need to disabling the lua files. Just remove the compromized throttle binding, restart (!) DCS, bind the throttle again and you're good to go. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
Ru55ell Posted October 25, 2021 Author Posted October 25, 2021 lol yes I have an Oculus CV1 and touch controllers. I did try to remove the binding, but didn't restart DCS (DOH!) I'll re-enable the lua files and give it a go. Thanks Also I'm having to double check the pitch and roll a they are bound by default as well, but they are easy to sort out.
Recommended Posts