TheAverageJoe93 Posted August 13, 2024 Posted August 13, 2024 My keybinds are not loading automatically in the Hog. I have to go to controls, then hit cancel, then my keybinds are working again. I don't have this issue on any other plane. Tried disabling hotplug, re-enabling. Saved Presets, Deleted, then loaded presets. Etc.
LeCuvier Posted August 13, 2024 Posted August 13, 2024 Sounds strange! Have you done any LUA editing? When you scroll through the lines in Options/Controls, do you see any warning flags, or lines of code highlighted in a reddish or orange colour? LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Yurgon Posted August 13, 2024 Posted August 13, 2024 Might be worth a try to start fresh. First, I'd go with a long and slow DCS Repair from the new Launcher. Then go to Saved Games\DCS\Config\Input\ and rename the A-10C II folder or move it to a different location altogether. When you next launch DCS, set just a handful of keybinds, restart DCS (or maybe even reboot the PC) and check if the problem is still there. Does that solve the problem?
TheAverageJoe93 Posted August 23, 2024 Author Posted August 23, 2024 Moving the filed from the folder, no A10CII folder at all. Then, loading into instant action, setting a few binds, then restarting DCS. This worked, my controls automatically loaded and everything was fine. I then took my .lua files from the folder I moved to the desktop into the new A10CII folder DCS made in the Input folder, and the issue showed itself again. At this point, I might just have to rebind everything in that new folder.
Yurgon Posted August 23, 2024 Posted August 23, 2024 10 hours ago, TheAverageJoe93 said: At this point, I might just have to rebind everything in that new folder. If that means that everything works without hassle, it's probably worth it. 2
Recommended Posts