ravenzino Posted November 12, 2019 Share Posted November 12, 2019 @BIGNEWY @Nineline It has been occurring for multiple times both on this forum and community groups that some may find that certain keys doesn't work in game although those bindings look and work alright in the CONTROLS setup page. It was later on confirmed that all such issues are due to the key bindings in UI Layer override those module specific ones. https://forums.eagle.ru/showthread.php?t=251744 https://forums.eagle.ru/showthread.php?t=254805 Once such conflict happens, DCS provides no mechanism to notify its user. Some poor guys might have to either not be able to use that key or end up reinstalling the entire DCS World, causing a lot of frustrations. Now, can ED extend DCS' existing key binding conflict detection mechanism to include those under UI Layer as well? Or if it is too hard, can ED at least put some static text on the CONTROL settings page to remind users of manually checking for such potential conflict? i9-9900K, G.Skill 3200 32GB RAM, AORUS Z390 Pro Wifi, Gigabyte Windforce RTX 2080 Ti, Samsung 960 Pro NVMe 512G + 860 Pro 1T, TM Warthog HOTAS, VKB T-Rudder, Samsung O+ F/A-18C, F-16C, A-10C, UH-1, AV-8B, F-14, JF-17, FC3, SA342 Gazelle, L-39, KA-50, CEII, Supercarrier Preordered. (Almost abandoned: CA - VR support please?) PG, NTTR Link to comment Share on other sites More sharing options...
Recommended Posts