Frederf Posted April 20, 2021 Posted April 20, 2021 (edited) It's just an example of a .diff.lua adding a key to a .lua as a change layer correctly. Default .lua has NO KEY for trim nose down and .diff.lua changes that to add key JOY_BTN_9. That's a valid thing to do. Your .diff.lua is saying hey, remove POV1_U from trim nose down. It can't because there is no such thing in the .lua to remove. That's the error. Your .diff.lua is asking for a change which makes no sense. We can speculate how this came to be but the answer to getting the error to go away is to remove the offending lines from the .diff.lua which ask the impossible. Edited April 20, 2021 by Frederf 1
imacken Posted April 20, 2021 Author Posted April 20, 2021 Just to add guys, I have no keyboard folder in the C:\Users\username\Saved Games\DCS.openbeta\Config\Input for any module. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
GottHold Posted April 20, 2021 Posted April 20, 2021 The Issue was with having the Removed section in Trim Right wing and Left wing down. If that is being removed it works fine. for some reason the Diff lua didnt like that it got removed from 2 spots in the diff lua. Have a nice day!
Flappie Posted April 20, 2021 Posted April 20, 2021 (edited) @imacken I assumed your "...MT-50..." files correspond to "VPCWarBRD + MT50.diff.lua", but I may be wrong: 3 hours ago, imacken said: Just to add guys, I have no keyboard folder in the C:\Users\username\Saved Games\DCS.openbeta\Config\Input for any module. This is normal if you have never assigned custom keyboard controls. Edited April 20, 2021 by Flappie 1 ---
Frederf Posted April 20, 2021 Posted April 20, 2021 .diff.lua files are difference files. They define how your controls are different than the defaults. If your difference files are empty or missing then you have default controls and deleting the difference files is also a fine way to reset your controls back to default. 1
Mike77 Posted April 22, 2021 Posted April 22, 2021 Thank you for the info in this thread! I've been trying to work out some problems and this thread is VERY helpful. Thank you again, greatly appreciated! 1 12th Gen i7 12700K, MSI Z690 Edge mobo, 32 GB of DDR4-3600 RAM (G.Skill Ripjaws V CL16). Gigabyte RTX4080 Eagle OC (Triple Fan, 16GB VRAM), ACER XV322QU 32" IPS monitor (running 2560x1440). 2TB NVMe M.2 Internal SSD (3D TLC NAND PCIe Gen 4 x4). Windows 11.
TimberWolf5871 Posted November 21, 2021 Posted November 21, 2021 So, getting past all the technical talk, how does one fix this issue? I have the problem with my Camera Transpose Mode command. Went to General controls and cleared the button binding there, don't have any custom profiles for that aircraft.
XCNuse Posted November 22, 2021 Posted November 22, 2021 (edited) I am having this issue with the C101 pitch and roll axis. Edit - Was able to resolve by completely deleting the bindings for the C101 CC/EB Edited November 22, 2021 by XCNuse fix'd
TimberWolf5871 Posted November 23, 2021 Posted November 23, 2021 I have a fix that may work for you all. Went to a ED dev for this. Go to your Saved Games DCS file, go to the config folder, rename the Input folder "Temp" and restart the game. It cleared my issue with the Camera Transpose Mode button. Hope it helps. If not, submit a ticket. It takes a while but they'll do their best. 1
Flappie Posted November 23, 2021 Posted November 23, 2021 Renaming the "Config/Input/A-10C" folder alone would be little less brutal. 1 1 ---
Captain Chuck Posted April 5, 2022 Posted April 5, 2022 (edited) On 11/23/2021 at 2:03 PM, TimberWolf5871 said: I have a fix that may work for you all. Went to a ED dev for this. Go to your Saved Games DCS file, go to the config folder, rename the Input folder "Temp" and restart the game. It cleared my issue with the Camera Transpose Mode button. Hope it helps. If not, submit a ticket. It takes a while but they'll do their best. We have a winner! Thanks you. Strangely several of low fidelity aircraft of my received red exclamations somehow, and binding not did work. Your "fix" fixed things instantly and so easy. However, I did use Flappie's suggestion. Edited April 5, 2022 by Капитан Чук 1 Ryzen 7 7800; GTX 4070; 32 GB RAM; Monitor 27" 1440p
Flappie Posted October 28, 2023 Posted October 28, 2023 A useful tip from @BMO : Disable the affected device in DCS controls. Restart DCS. Enable the affected deice in DCS controls: the red marks should now be gone. Thanks, mate. ---
BMO Posted October 30, 2023 Posted October 30, 2023 Am 28.10.2023 um 11:10 schrieb Flappie: Disable the affected device in DCS controls. Restart DCS. Enable the affected deice in DCS controls: the red marks should now be gone. This is only a quickfix tho, since the problem kept reoccuring for me. Also I noticed that u dont have to restart the game (I played my first online operation yesterday and noticed that my rudders are not working when I was supposed to taxi to the cat -.-). Just: 1. Disable the device via the dropdown menu in DCS Controls 2. Rescan devices 3. Activate it again. The Axis did then work, the red exclamation at the bind (column of the device) was gone, but the red exclamation mark at the description of the bind stays. Which is probably the reason it keeps occuring for me. I guess i have to delete the controls completely and make them new.
Recommended Posts