Im_TheSaint Posted October 28, 2022 Posted October 28, 2022 (edited) Visual export code such as: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR") or making changes to the profiles in CMDS page will result in a broken Integrity check my DED_init.lua more info here in f16 specific thread: Edited October 28, 2022 by Im_TheSaint
yeldraw1 Posted December 14, 2022 Posted December 14, 2022 yes this is BS, viewports export, should not have issues with IC. just putting a screen on another monitor for people who make sim pit....fix this ED 1
Se1ko Posted December 17, 2022 Posted December 17, 2022 On 12/15/2022 at 9:58 AM, yeldraw1 said: yes this is BS, viewports export, should not have issues with IC. just putting a screen on another monitor for people who make sim pit....fix this ED Agreed. Nearly every post I have read about this is either about people having an issue that they cant change their countermeasure parameters (to which I say, so what, deal with it) or, and most frequently, that they have a cockpit scripts IC issue where they are simply extracting a display to another screen. I am sure ED would satisfy nearly everyone if they added a "pure cockpit script {yes/no}" option to their IC check that allowed display extraction while not allowing other script changes. 1
trenchfeet Posted April 29, 2024 Posted April 29, 2024 Is this still an issue I get the failure on rwr and ded export for the f16
Recommended Posts