ambision Posted July 5, 2020 Posted July 5, 2020 in DCS, HOTAS Warthog Throttle Hat POV switch is not registering 'down' commands. It only happens while in game, and not in any other instance. Any advice? AMD Ryzen 3 3900X @5Ghz G.Skill 64GB RAM @3200Mhz nVidia GTX 980ti SAMSUNG 250GB SATA SSD Corsair H100i AIO Conductonaut thermal liquid metal Thrustmaster Warthog HOTAS & TPR Leap Motion
Lange_666 Posted July 5, 2020 Posted July 5, 2020 Saved Games folder DCS (or beta) Config Input F-16C_50 Keyboard remove the keyboard.diff.lua and setup your controls again. 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!
ambision Posted July 5, 2020 Author Posted July 5, 2020 unfortunately, nothing changed. still the same behaviour AMD Ryzen 3 3900X @5Ghz G.Skill 64GB RAM @3200Mhz nVidia GTX 980ti SAMSUNG 250GB SATA SSD Corsair H100i AIO Conductonaut thermal liquid metal Thrustmaster Warthog HOTAS & TPR Leap Motion
Flappie Posted July 5, 2020 Posted July 5, 2020 Hi, you need to determine if this issue happens only with the F-16C or not. I suggest you bind the same button to any command (let's say 'Open/Close Canopy') of the free Su-25T, and get back here to tell us what you find out. ---
ambision Posted July 6, 2020 Author Posted July 6, 2020 thanks for the reply m8, I've been able to reproduce the issue with all modules (I have most of them) and when I change the button's function it registers but doesn't execute it AMD Ryzen 3 3900X @5Ghz G.Skill 64GB RAM @3200Mhz nVidia GTX 980ti SAMSUNG 250GB SATA SSD Corsair H100i AIO Conductonaut thermal liquid metal Thrustmaster Warthog HOTAS & TPR Leap Motion
Flappie Posted July 6, 2020 Posted July 6, 2020 Hey, I was able to reproduce the exact same issue, and I got rid of it! :thumbup: It is tied to the ingame voice chat, even if the voice chat function is disabled. That is some pretty little bug! Please go to Options > Controls > UI layer and check what you have binded for "Voice chat push-to-talk mic. mode: On/Off voice transfer". I bet you a dollar you will find this: ---
ambision Posted July 6, 2020 Author Posted July 6, 2020 WOWWWWWW thanks man! that actually did the trick!! AMD Ryzen 3 3900X @5Ghz G.Skill 64GB RAM @3200Mhz nVidia GTX 980ti SAMSUNG 250GB SATA SSD Corsair H100i AIO Conductonaut thermal liquid metal Thrustmaster Warthog HOTAS & TPR Leap Motion
Lange_666 Posted July 6, 2020 Posted July 6, 2020 Hey, I was able to reproduce the exact same issue, and I got rid of it! :thumbup: It is tied to the ingame voice chat, even if the voice chat function is disabled. That is some pretty little bug! No so fast... Why don't i have that problem then? I have nothing assigned to the ingame voice chat (and i surely didn't remove it before hand). 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!
Flappie Posted July 6, 2020 Posted July 6, 2020 (edited) No so fast... Why don't i have that problem then? I have nothing assigned to the ingame voice chat (and i surely didn't remove it before hand). If you haven't bound any key to the voice chat push-to-talk command (see my screenshot), you won't have this issue. I had a key assigned to voice chat PTT, but it's a key that I don't use on any aircraft: in that case, no problem either. WOWWWWWW thanks man! that actually did the trick!! I'm glad it works for you. :) Edited July 6, 2020 by Flappie ---
ambision Posted July 7, 2020 Author Posted July 7, 2020 to be honest, that aforementioned stray key was bound to 'vr zoom' before. that was the issue AMD Ryzen 3 3900X @5Ghz G.Skill 64GB RAM @3200Mhz nVidia GTX 980ti SAMSUNG 250GB SATA SSD Corsair H100i AIO Conductonaut thermal liquid metal Thrustmaster Warthog HOTAS & TPR Leap Motion
Flappie Posted July 7, 2020 Posted July 7, 2020 OK, so let's sum it up for ED devs: The "UI Layer" bindings category is completely independant from the others, which means: 1. There are no warnings emitted when a key is used in both "UI layer" category and any other category, which can lead to conflicting bindings. 2. When such conflicting bindings happen, only the "UI layer" commands do work ingame. ---
Recommended Posts