reported Changes to scripts fail integrity check again.

[jonsky7]

On 4/25/2024 at 10:25 PM, MadKreator said:

@NineLine

Using the standard method of exporting confines the viewports, say left_mfcd and right_mfcd to be in the same location and same size across ALL aircraft, unless you create a new monitor setup  and switch monitor types for each aircraft.
 

I don't know if you know already, but I just wanted to point out that is possible to define an aircraft in the monitor config files now.

It allows the exports to be placed per aircraft type. Meaning it doesn't matter that displays in different aircraft have the same name.  

It doesn't solve all the problems, but it does allow some flexibility for exporting the default available displays without breaking "Pure Scripts" rules.

See here for how to.
Scroll down to "Advanced editing by aircraft type."

 

Edited May 31, 2024 by jonsky7

[MadKreator]

3 minutes ago, jonsky7 said:

I don't know if you know already, but I just wanted to point out that is possible to define an aircraft in the monitor config files now.

It allows the exports to be placed per aircraft type. Meaning it doesn't matter that displays in different aircraft have the same name.  

See here for how to.
Scroll down to "Advanced editing by aircraft type."

 

Thanks for the tip. I did not know that! That would help I’m sure for the standard “exposed” viewports, but will still run into the issues with the non-exposed viewports that need “patched”,  of course. Maybe already understood by the powers that be, but maybe not efficient enough yet to re-write Helios while still having to “patch” some of the core file to expose other viewports…  @BluFinBima have you ever played around setting up the basic viewports like this? Btw @jonsky7 your guides helped me greatly when I started exporting things. Thanks for always being generous with your time and staying supportive of the “exporting” community. Your knowledge is well received!

[MadKreator]

@NineLine I know its probably not a huge priority at the moment for the team ( I'm sure pushing hard toward DCS 3.0), but just curious if the dev that showed interest has mentioned anything or had any thought of solutions/implementations?( like he showed in his video of the internal export/popup API) 

Edited August 4, 2024 by MadKreator

[Eraseri]

I sincerely hope that this issue gets addressed. It is very limiting at the moment. For instance, there is no possibility to display AH-64D EUFD without failing integrity checks. It should be possible without "cheating" with scripts. Same goes for many other modules like AJS-37 Viggen. Viggen doesn't have radar or mawerick display availability.