requested Why should exporting RWR and other viewports break integrity check?

[Alleluia]

I guess it’s no….

 

[Furlow]

Ran into this problem myself this week. Was playing Contention in chinook and decided it would be nice to have 2x 11 inch tablets as pilots mfd and CDU, since I can barely read the airspeed etc and to make navigation a lot quicker. Three days of Amazon and setup later, and a crash tutorial in spacedesk and helios, everything works great, but I now cant play on Contention because I break IC. (Shout out to helios guys though, amazing program).

 

So what are our options for exporting things? Is anything other than 1-3 monitors in a horizontal line going to break IC? Is there any kind of touchscreen available in vanilla DCS where I could try and get a 43 inch monitor with touchscreen to display the entire pilot-side cockpit interior with usable MFDs and CDU? The monitor options in setup is filled with CAMERA + LMFD etc options, do these work or is it another IC breaker? (I tried some of them and it resets and stretches all my displays that Ive finally just got working for helios, so i dont want to wreck that yet if its not going to help anything).

 

Excuse the long post but at this stage I dont even know what I dont know. Is exporting an mfd possible at all without breaking IC?

[MadKreator]

10 hours ago, Furlow said:

Ran into this problem myself this week. Was playing Contention in chinook and decided it would be nice to have 2x 11 inch tablets as pilots mfd and CDU, since I can barely read the airspeed etc and to make navigation a lot quicker. Three days of Amazon and setup later, and a crash tutorial in spacedesk and helios, everything works great, but I now cant play on Contention because I break IC. (Shout out to helios guys though, amazing program).

 

So what are our options for exporting things? Is anything other than 1-3 monitors in a horizontal line going to break IC? Is there any kind of touchscreen available in vanilla DCS where I could try and get a 43 inch monitor with touchscreen to display the entire pilot-side cockpit interior with usable MFDs and CDU? The monitor options in setup is filled with CAMERA + LMFD etc options, do these work or is it another IC breaker? (I tried some of them and it resets and stretches all my displays that Ive finally just got working for helios, so i dont want to wreck that yet if its not going to help anything).

 

Excuse the long post but at this stage I dont even know what I dont know. Is exporting an mfd possible at all without breaking IC?

The IC breakers aren't the monitor configurations themselves. In the case of the CH-47 and many others it's because the viewports are natively exportable. The "patches" we write for Helios have to modify the core viewport files to let them export... Ironically its the same two lines of script that is built into DCS that let things like mfd's, tedac, etc export.. Odd case in the CH-47 is that the lines of code are already in each(most) file but they don't have names and  are commented out. Why they were written in the files and then blocked from use? Your guess is as good as mine lol
Some viewports can be exported without breaking ic but it is a very limited list.. LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, TEDAC, ABRIS, Shkval, are the ones I can think of off the top of my head.. oh and all of the viewports in the JF-17 are natively exportable from DEKA. .. In the CH-47, the only one that works with native naming is RIGHT_MFCD

 

Edited May 29 by MadKreator

[Furlow]

On 5/29/2025 at 7:21 PM, MadKreator said:

In the CH-47, the only one that works with native naming is RIGHT_MFCD

 

Hi, thanks for the fast reply and apologies for my slow one. Appreciate the help, even if its the answer I dreaded lol. So basically I have a naked right mfd for Contention, and the helios setup is for non-protected servers (which are not many these days) and singleplayer. I'm partly grateful because at least I can read the display now, but its a bit miserable that they are so close to proper connectivity but seemingly purposely fencing it off. Could it be they want things like exportable/exterior instruments to be a divider between DCS and the military trainer version? Makes zero sense to me but there has to be a reasoning somewhere for it to be included then disabled.

 

Also congrats and major thanks to you on your helios stuff, big fan of your chopper cockpit panels. Amazing stuff. Appreciate your time.

[MadKreator]

11 hours ago, Furlow said:

Hi, thanks for the fast reply and apologies for my slow one. Appreciate the help, even if its the answer I dreaded lol. So basically I have a naked right mfd for Contention, and the helios setup is for non-protected servers (which are not many these days) and singleplayer. I'm partly grateful because at least I can read the display now, but its a bit miserable that they are so close to proper connectivity but seemingly purposely fencing it off. Could it be they want things like exportable/exterior instruments to be a divider between DCS and the military trainer version? Makes zero sense to me but there has to be a reasoning somewhere for it to be included then disabled.

 

Also congrats and major thanks to you on your helios stuff, big fan of your chopper cockpit panels. Amazing stuff. Appreciate your time.

 The sentiment is very much appreciated. I'm happy people are using them!

No I don't think there is a divide between the two regarding viewports, I think its just not an important part for them to focus on. Or they are slowly working on a way to do them slightly differently. Oddly, the ch-47 viewports are all located in a folder called GC Base, not in folders withing the aircraft files like every other module. Why its done like this is a mystery to me.. I'm hoping there is a bigger picture at play. a couple of the viewports like the chronometer and sfd's, I had to add the scripts too, but the rest of them already had the scripts in there.. Hopefully they will just name them and un-comment them one of these days so they are natively available.

 

[jonsky7]

On 5/30/2025 at 12:21 AM, MadKreator said:

The IC breakers aren't the monitor configurations themselves. In the case of the CH-47 and many others it's because the viewports are natively exportable. The "patches" we write for Helios have to modify the core viewport files to let them export... Ironically its the same two lines of script that is built into DCS that let things like mfd's, tedac, etc export.. Odd case in the CH-47 is that the lines of code are already in each(most) file but they don't have names and  are commented out. Why they were written in the files and then blocked from use? Your guess is as good as mine lol
Some viewports can be exported without breaking ic but it is a very limited list.. LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, TEDAC, ABRIS, Shkval, are the ones I can think of off the top of my head.. oh and all of the viewports in the JF-17 are natively exportable from DEKA. .. In the CH-47, the only one that works with native naming is RIGHT_MFCD

 

I haven't done a huge amount of testing with this but...

ED's modules' exports are usually named LEFT_MFCD and RIGHT_MFCD as you know.

The CH-47's files that have the exports in them, in GCBase and are there but commented out (not activated), as you mentioned, have 4 screens labelled LEFT_MFCD, and only one RIGHT_MFCD.

When I tried simply removing the comments, to activate them, the exported screens were overlaying each other on the export monitor. 

So I was thinking that maybe, they were waiting for the "seat swap" code to work (like the Apache), where the MFCD exports would change depending on which seat you were sat in.
 

[MadKreator]

On 6/7/2025 at 5:49 PM, jonsky7 said:

I haven't done a huge amount of testing with this but...

ED's modules' exports are usually named LEFT_MFCD and RIGHT_MFCD as you know.

The CH-47's files that have the exports in them, in GCBase and are there but commented out (not activated), as you mentioned, have 4 screens labelled LEFT_MFCD, and only one RIGHT_MFCD.

When I tried simply removing the comments, to activate them, the exported screens were overlaying each other on the export monitor. 

So I was thinking that maybe, they were waiting for the "seat swap" code to work (like the Apache), where the MFCD exports would change depending on which seat you were sat in.
 

Yes thats very possible. I’m sure there’s a reason they are the way they are, at the moment.