LanceLynxx Posted February 17, 2020 Share Posted February 17, 2020 I'm trying to create a custom mission in mission editor, in which a trigger is activated after the engine RPM hits a certain %. However, while trying to use conditions such as COCKPIT PARAM EQUAL TO or COCKPIT ARGUMENT IN RANGE, I found out I couldn't find the IDs for the indicators, because "devices.lua" apparently doesn't exist for FC3 aircraft, only for stand-alone modules. I can export values such as the RPM using the "export.lua" entering "return LoGetEngineInfo ()" , but even though it gives me all the engine info I need, it doesn't give me the engine RPM gauge ID, so I cannot use it to activate the trigger. Any help appreciated. TL DR where can I find Cockpit Indicator IDs for FC3 aircraft? And if I can't, how can I make a trigger that activates upon FC3 RPM hitting a certain %? Link to comment Share on other sites More sharing options...
djlang1978 Posted March 3, 2020 Share Posted March 3, 2020 Also need this i5 9600K, 32GB DDR4, RTX2080FE, 2x1TB M.2, Win 10 Pro, Thrustmaster Warthog, Oculus Rift S and CV1 Link to comment Share on other sites More sharing options...
Rudel_chw Posted March 3, 2020 Share Posted March 3, 2020 FC3 aircrafts were ported into DCS from Lo-Mac, but they don't have the same simulation technology than study modules. I used the LUA-Console on them but they show no Cockpit Parameters at all, and also no Cockpit Indicators. 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 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1 Mobile: iPad Pro 12.9" of 256 GB Link to comment Share on other sites More sharing options...
Recommended Posts