gavagai Posted February 9, 2016 Posted February 9, 2016 2.0.1 says radar pipper range is double mapped, and I checked and rechecked 4x, and I am certain it is not double mapped. Therefore I cannot change the radar pipper range without the mouse. I even tried clearing the category filled in with red, but then it still showed the control as double mapped. No such problem in 2.0. Thanks. P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria
Frederf Posted February 9, 2016 Posted February 9, 2016 This is a common problem with many modules when the controls change in a patch with a simple fix. The controls in DCS are defined by two files, the .lua that defines all the control entries and their defaults and a diff.lua which saves how your particular control preferences are different from default. It's super clever except... During patching the diff.lua from an old version can be differences from a control .lua which is totally different now. Thus the red errors that can't seem to go away. How to fix it? You can edit the exact lines in the diff.lua file that's giving you problems or more reliably delete them and customize your controls again for that module. C:\Users\_user_\Saved Games\DCS\Config\Input\ka-50\ is the one I'm working on right now due to a similar bug on the ka-50 module. Whee! 1
gavagai Posted February 9, 2016 Author Posted February 9, 2016 Thankyou Frederf!:thumbup: P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria
Recommended Posts