Bungle_uk Posted August 30, 2017 Posted August 30, 2017 (edited) Hi all. I'm having trouble assigning a number of controls. The box to assign them is simply not selectable. With some controls, I can assign keyboard controls but not button controls (HOTAS) and with other controls, I can assign Buttons but cannot select the keyboard to assign a keypress. Example is the weapon selector rotate clockwise / counterclockwise. Is it worth me compiling a list of controls that I cannot assign or is this something that is in-progress so to speak. Apologies if this has been brought up already. Version 1.5.7.8899.335 Edited August 30, 2017 by 214th_bungle_uk
Knock-Knock Posted August 30, 2017 Posted August 30, 2017 Related to this perhaps? https://forums.eagle.ru/showthread.php?t=192747 - Jack of many DCS modules, master of none. - Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS. | Windows 11 | i5-12400 | 64Gb DDR4 | RTX 3080 | 2x M.2 | 27" 1440p | Rift CV1 | Thrustmaster Warthog HOTAS | MFG Crosswind pedals |
Bungle_uk Posted August 30, 2017 Author Posted August 30, 2017 Related to this perhaps? https://forums.eagle.ru/showthread.php?t=192747 I don't think it is as this isn't something that has just appeared with the latest patch. Also, I have tried putting in those files as well but the issue remains.
Rudel_chw Posted August 30, 2017 Posted August 30, 2017 I had the same problem initially, but using this Mod solved the problem: https://forums.eagle.ru/showthread.php?t=181720 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Bungle_uk Posted August 30, 2017 Author Posted August 30, 2017 I had the same problem initially, but using this Mod solved the problem: https://forums.eagle.ru/showthread.php?t=181720 Thx Rudel. Might be something to look at as a workaround. I think it would be good if this issue can be fixed before the module comes out of beta though. I should point out that I have not tried any of this in 2.x so its possible it could just be a 1.57 issue.
Recommended Posts