[HOW TO] Set up your exports to be aircraft specific

[jonsky7]

Advanced editing by aircraft type,

Thanks to @scrupeus For this information and example.

It is possible to set up your exports to be aircraft specific.

What does that mean?
Well you may want your MFCDs exports to be a different configuration for different aircraft.
Example, you fill a screen with two MFCDs for the A10C, but you want to fit three MFCDs on that screen for the FA-18 or Apache.
Or maybe you want a Right MFCD to be larger in some aircraft, whatever.

This removes any requirement to change the names of MFCD exports in their respective files, or have multiple profiles for different aircraft, and will pass integrity check (as long as you don't modify any other files like RWR displays etc.)

We do this by adding a function to our monitor config files. The function "listens" to DCS for the unit type (aircraft being flown), and sets up the exports depending on the unit type.
We add an "else" function towards the end to allow for a default location for the exports. We can also group aircraft together with an "or" command.
If you do not specify a particular aircraft for reconfiguration, it's exports will be shown in the "else" location

 

Example config file, no mods, just every aircraft with default exportable displays with it's own entry.

Exports by aircraft type.lua

 

 

 

Example:

 

function reconfigure_for_unit(unit_type)
     if unit_type == "A-10C" or unit_type == "A-10C_2" then

          LEFT, RIGHT, etc

     elseif unit_type == "AH-64D_BLK_II" then

          LEFT, RIGHT, TEDAC etc

     elseif unit_type == "F-16C_50" then

          LEFT, RIGHT, EHSI etc
     else

          LEFT, RIGHT, etc

end

Example config file

 

_ = function(p) return p; end;
name = _('my export config');
Description = 'exports by aircraft type';
Viewports =
{
Center =
{
x = 0;
y = 0;
width = 2560;
height = 1440;
viewDx = 0;
viewDy = 0;
aspect = 2560/1440;
}
}

--/////////////////////////////////////
--A10C
--/////////////////////////////////////

function reconfigure_for_unit(unit_type) 

if unit_type == "A-10C" or unit_type == "A-10C_2" then

LEFT_MFCD =
{
x = 5130;
y = 360;
width = 825;
height = 825;
}

RIGHT_MFCD =
{
x = 6210;
y = 360;
width = 825;
height = 825;
}

--/////////////////////////////////////
--AH64D
--/////////////////////////////////////

elseif unit_type == "AH-64D_BLK_II" then

LEFT_MFCD =
{
x = 5130;
y = 360;
width = 825;
height = 825;
}

RIGHT_MFCD =
{
x = 6210;
y = 360;
width = 825;
height = 825;
}

TEDAC =
{
x = 2560;
y = 280;
width = 1620;
height = 1400;
}

--/////////////////////////////////////
--F-16C
--/////////////////////////////////////

elseif unit_type == "F-16C_50" then

LEFT_MFCD =
{
x = 5130;
y = 360;
width = 900;
height = 900;
}

RIGHT_MFCD =
{
x = 6300;
y = 360;
width = 900;
height = 900;
}

EHSI =
{
x = 2560;
y = 280;
width = 825;
height = 825;
}

--///////////////////////////////////////
--EVERYTHING ELSE
--///////////////////////////////////////

else

LEFT_MFCD =
{
x = 5130;
y = 360;
width = 825;
height = 825;
}

RIGHT_MFCD =
{
x = 2560;
y = 360;
width = 1720;
height = 1080;
}
end
end

GU_MAIN_VIEWPORT =
{
x = 0;
y = 0;
width = 2560;
height = 1440;
}

--UIMainView = Viewports.Center
UIMainView = 
{
x = 0;
y = 0;
width = 2560;
height = 1440;
}

In the above example, the A10C & A10C2, Apache, and F-16C have defined MFCD export locations, and any other aircraft's MFCD export will be shown in the "else" location 

This is a list of the unit types

 

A-10A

A-10C

A-10C_2

AH-64D_BLK_II

AJS37

AV8BNA

CH-47Fbl1

F-5E-3

F-5E-3_FC

F-14A-135-GR

F-14B

F-15C

F-15ESE 

F-16C_50

FA-18C_hornet

Hercules (Hercules Mod)

JF-17

Ka-50

Ka-50_3

L-39

L-39C

L-39ZA

OH58D

M-2000C

Mi-8MT

Mi-24P

MiG-21Bis

MiG-29

Mirage-F1BE
Mirage-F1CE
Mirage-F1EE
Mirage-F1M

P-51D

P-51D-30-NA

SA342L

SA342M

SA342Minigun

Su-25

Su-25T

Su-27

Su-33

TF-51D

UH-1H

 And these are the
Default MFCD Export names
 

 

A-10C, A-10C_2
LEFT_MFCD, RIGHT_MFCD

AH64-D 
LEFT_MFCD, RIGHT_MFCD, TEDAC or CENTER_MFCD
An entry for TEDAC in your monitor config file takes priority over a CENTER_MFCD entry, so if you have both, the TEDAC will be shown in the TEDAC position.

AV8BNA
LEFT_MFCD, RIGHT_MFCD

CH-47Fbl1
RIGHT_MFCD

F-5E
RIGHT_MFCD

F-14
F14_VDI,                   F14_HSD,                F14_TID,                  F14_DDD,               F14_ECMD,                                    F14_UHF_ARC159, F14_VHF_ARC182
Pilot upper display, Pilot lower display, RIO lower display, RIO upper display, RIO right display (by right knee), Radio Freq displays x2

F-15E
Front Seat
LEFT_MFCD, CENTER_MFCD, RIGHT_MFCD, UFC.
Back Seat
OUTER_LEFT_MFCD, LEFT_MFCD, RIGHT_MFCD, OUTER_RIGHT_MFCD, UFC.

F-16 
LEFT_MFCD, RIGHT_MFCD, EHSI

FA-18 
LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD

JF-17
JF17_LEFT_MFCD, JF17_RIGHT_MFCD, JF17_CENTER_MFCD, JF17_CLOCK_WIN1, JF17_CLOCK_WIN2, JF17_RADIO, JF17_UFCP_1, JF17_UFCP_2, JF17_UFCP_3, JF17_UFCP_4
or
LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, CLOCK_WIN1, CLOCK_WIN2, RADIO, UFCP_1, UFCP_2, UFCP_3, UFCP_4
(if you have JF17_LEFT_MFCD defined in your config file, the LEFT MFCD of the JEFF will be displayed in that position, otherwise it will be shown in the LEFT_MFCD position.
The upper line here takes priority over the lower line, this enables you to have the display export a different size or location to the LEFT_MFCD position, helpful because the JEFF screens are not square.)

Ka-50 and Ka-50_3
Shkval, ABRIS
or
LEFT_MFCD, RIGHT_MFCD
(again, if you define ABRIS in your config file, the ABRIS will be shown in that position, otherwise it will be displayed in the RIGHT_MFCD position.)

M-2000C
VTB (Radar) displays in RIGHT_MFCD position

MIG-21bis
RP22 or RIGHT_MFCD

Mirage -F1
LEFT_MFCD, RIGHT_MFCD

OH58D
LEFT_MFCD, RIGHT_MFCD

FC3
LEFT_MFCD, RIGHT_MFCD 

 

 

 

 

Cheers

Jon

Edited September 25, 2024 by jonsky7

[MAXsenna]

Excellent!

Sent from my SM-A536B using Tapatalk

[MadKreator]

23 hours ago, MAXsenna said:

Excellent!

Sent from my SM-A536B using Tapatalk
 

Helios now structures the monitor file similar to this. Separating each aircraft so you can use default viewport names. Wasn’t sure if you caught that addition in one of the recent updates. ( you do have to rename them in Helios manually and disable the accompanying patch). But for simple setups with native DCS exports/ names it will no longer break IC.. The forced/patched  exports still will though.

And as always, Thanks Jonsky!

 

Edited September 24, 2024 by MadKreator

[MAXsenna]

26 minutes ago, MadKreator said:

Helios now structures the monitor file similar to this. Separating each aircraft so you can use default viewport names. Wasn’t sure if you caught that addition in one of the recent updates. ( you do have to rename them in Helios manually and disable the accompanying patch). But for simple setups with native DCS exports/ names it will no longer break IC.. The forced/patched  exports still will though.

And as always, Thanks Jonsky!

 

 

I'm in heaven! You guys are Saints! 

When @jonsky7 first told me about this, I was gonna ask you and @BluFinBima  if this possibly could be implemented, and now it is!

So! What must be done now is to lobby ED and all 3rd parties to make the viewports available, and I mean all the viewports, as there are missing ones, and we don't need patching anymore?

This will even work for old Ikarus profiles then I gather. 

Thanks guys! 

[MadKreator]

30 minutes ago, MAXsenna said:

I'm in heaven! You guys are Saints! 

When @jonsky7 first told me about this, I was gonna ask you and @BluFinBima  if this possibly could be implemented, and now it is!

So! What must be done now is to lobby ED and all 3rd parties to make the viewports available, and I mean all the viewports, as there are missing ones, and we don't need patching anymore?

This will even work for old Ikarus profiles then I gather. 

Thanks guys! 

I completely agree. I don’t understand why the export API isn’t opened for all viewports. I know next to nothing about scripting and after following Jonsky’s findings on the CH-47, it took me no time at all to modify them into working “patches” for helios and make them exportable. The scripting is already built into DCS it literally just needs placed in the appropriate file for each aircraft and a name given to each.
That being said, seeing as how the CH47 viewports ( most of them) are in a totally separate file from the aircraft, it makes me wonder if they aren’t working on something better. Keeping hopes up. Maybe one of us should compile a folder full of all the non-exportable viewports with the changes necessary to make them exportable natively and send it to them

[MAXsenna]

@jonsky7 Giving this some more thought, and looking at your list of units above, I decided to check something. The FC2024 F-5E has a viewport defined for the radar. Well, I assume so, because the files are identical, with their content to the FF F-5E,
I have very single module, so feel free to ask go through them to add to to your list. I'm not sure which instruments can be exported as a viewport, like for the MB-339/Mirage F1. They have a lot of references to "viewports" for their instruments, and what other instruments can be exported through Helios. @MadKreator It does make me wonder if your F-5E profile can work for it. That'd be cool for other users.

As for the Kiowa, it has already left and right MFDs defined, so they worked out of the box. I'm sure all these 3rd parties would be more than willing to export all they can, if they were just told how to do so. Unfortunately, I'm not there myself yet.

Cheers!

[MAXsenna]

17 minutes ago, MadKreator said:

That being said, seeing as how the CH47 viewports ( most of them) are in a totally separate file from the aircraft, it makes me wonder if they aren’t working on something better.

Yeah! Makes me wonder regarding the FC F-5E.

18 minutes ago, MadKreator said:

Keeping hopes up. Maybe one of us should compile a folder full of all the non-exportable viewports with the changes necessary to make them exportable natively and send it to them

You read my mind!

[MAXsenna]

2 hours ago, MadKreator said:

Helios now structures the monitor file similar to this. Separating each aircraft so you can use default viewport names.

Right! That did work. But how do I go about making Helios write the correct name for FC modules, and not the generic "FC3"? Mind you. I can now easily do this manually. I just have to have my own "extended" Helios monitor file I do this, that does not get overwritten, and I just transfer the corrections I make.

 

As you can see. I do get conflicts. If Helios can't do this as of now, it's fine. I just do it manually. But it would be super awesome if it could handle this in the future!

 

[jonsky7]

55 minutes ago, MAXsenna said:

@jonsky7 Giving this some more thought, and looking at your list of units above, I decided to check something. The FC2024 F-5E has a viewport defined for the radar. Well, I assume so, because the files are identical, with their content to the FF F-5E,
I have very single module, so feel free to ask go through them to add to to your list. I'm not sure which instruments can be exported as a viewport, like for the MB-339/Mirage F1. They have a lot of references to "viewports" for their instruments, and what other instruments can be exported through Helios. @MadKreator It does make me wonder if your F-5E profile can work for it. That'd be cool for other users.

As for the Kiowa, it has already left and right MFDs defined, so they worked out of the box. I'm sure all these 3rd parties would be more than willing to export all they can, if they were just told how to do so. Unfortunately, I'm not there myself yet.

Cheers!

If you have notepad++, https://notepad-plus-plus.org/downloads/

Go to the search tab, select "find in files", do a search for 

try_find_assigned_viewport

filters - *.lua  (just speeds up the search)

Point it at your DCS aircrafts folder.

 

It will return every instance that term is mentioned in the aircraft files, those are the exportable displays.

 

 

If you have aircraft I don't have in my list, go to that aircrafts main folder, find the entry.lua file.

Near the bottom you will see something like.

make_flyable(
    "CH-47Fbl1",

I think that is the best way to get the aircrafts actual ID name.

Edited September 24, 2024 by jonsky7

[MAXsenna]

@jonsky7 Roger!

[MadKreator]

2 hours ago, MAXsenna said:

Right! That did work. But how do I go about making Helios write the correct name for FC modules, and not the generic "FC3"? Mind you. I can now easily do this manually. I just have to have my own "extended" Helios monitor file I do this, that does not get overwritten, and I just transfer the corrections I make.

 

As you can see. I do get conflicts. If Helios can't do this as of now, it's fine. I just do it manually. But it would be super awesome if it could handle this in the future!

 

That I’m not sure of, Ive never used any of the fc fc/3 modules with helios.. I don’t think Bluefin has done anything with the fc, fc3 interface or anything yet. The monitor change is new, there was quite a few bumps getting to differentiate CZ’s generic interface in modules where its copy pasted ( like f-18 using the a-10 interface and Blackshark and gazelle using the same) so theres bound to be some more work done to it. He’s finishing up some stuff for the next helios release and the CH-47. Then I think he’ll be gone on vacation a couple weeks. But I will try to look into it and see if something he wants to tackle after. I’m not so much interested in the fc jets but a lot of people ask about profiles for them so it’s always something I’d like to try to get working. 

3 hours ago, MAXsenna said:

@jonsky7 Giving this some more thought, and looking at your list of units above, I decided to check something. The FC2024 F-5E has a viewport defined for the radar. Well, I assume so, because the files are identical, with their content to the FF F-5E,
I have very single module, so feel free to ask go through them to add to to your list. I'm not sure which instruments can be exported as a viewport, like for the MB-339/Mirage F1. They have a lot of references to "viewports" for their instruments, and what other instruments can be exported through Helios. @MadKreator It does make me wonder if your F-5E profile can work for it. That'd be cool for other users.

As for the Kiowa, it has already left and right MFDs defined, so they worked out of the box. I'm sure all these 3rd parties would be more than willing to export all they can, if they were just told how to do so. Unfortunately, I'm not there myself yet.

Cheers!

I have not dug into it much after the fc2024 releases, which I don’t have it anyway, but also have not looked at things like the f-5e yet. I asked Bluefin if he was going to redo all the patches and viewports to go with the  standard naming, and while a little hesitant, he wasn’t opposed to it completely. More worried about breaking every single profile ever made with the “Patched” viewports lol 

[MAXsenna]

That I’m not sure of, Ive never used any of the fc fc/3 modules with helios.. I don’t think Bluefin has done anything with the fc, fc3 interface or anything yet. The monitor change is new, there was quite a few bumps getting to differentiate CZ’s generic interface in modules where its copy pasted ( like f-18 using the a-10 interface and Blackshark and gazelle using the same) so theres bound to be some more work done to it. He’s finishing up some stuff for the next helios release and the CH-47. Then I think he’ll be gone on vacation a couple weeks. But I will try to look into it and see if something he wants to tackle after. I’m not so much interested in the fc jets but a lot of people ask about profiles for them so it’s always something I’d like to try to get working. 

Right! I misunderstood then. In any case, I generated a new Helios file, copied and renamed it. Copied the "FC3" changes over and edited them according to Jonsky7 's naming conventions. I can now use one single "HeliosExtended" file for all the FC modules. I'm very happy! If you look at Jonsky7 's file at the top, you can see his text structure is somewhat different. For new users following the thread, they can just use his file without issues. For users that wants the Helios profiles like CaptainZ's, one can do it the way I did. It really doesn't matter. It's really easy to get everything correct now. I do use a little tool that tells me where my cursor is, so I can get perfect alignment for all the profiles.
Thanks for all the help guys!

Sent from my SM-A536B using Tapatalk

[MadKreator]

29 minutes ago, MAXsenna said:

Right! I misunderstood then. In any case, I generated a new Helios file, copied and renamed it. Copied the "FC3" changes over and edited them according to Jonsky7 's naming conventions. I can now use one single "HeliosExtended" file for all the FC modules. I'm very happy! If you look at Jonsky7 's file at the top, you can see his text structure is somewhat different. For new users following the thread, they can just use his file without issues. For users that wants the Helios profiles like CaptainZ's, one can do it the way I did. It really doesn't matter. It's really easy to get everything correct now. I do use a little tool that tells me where my cursor is, so I can get perfect alignment for all the profiles.
Thanks for all the help guys!

Sent from my SM-A536B using Tapatalk
 

Yes two different worlds for sure. @jonsky7 does a hell of a job figuring these things out and always striving to improve the experience and ease the pain for people!( and thank you for posting that list of all of the default viewport names).  Bluefin does a great job too working within the confines of the Helios software and trying to always improve it.  
Good work on combining the two different ways they are written @MAXsenna. I will for sure be stealing some of these ideas to try to help refine the Helios exportsAnd see if the FC exports can now be added, I think a lot of people would like that. If you get them all working and figured out, I may pester you for a copy of your monitor file, and maybe the entry.luas of the FC aircraft, if you don’t mind, someday Might make Bluefins life much easier seeing the key information first hand. 

- on a side note I don’t believe Helios has had much support for the FC aircraft since version 1.4. I’ve tried to get some of CZ’s profiles updated and working briefly but didn’t dive in too deep. I think even just some fc series viewports that don’t break IC would be a good start.

Edited September 25, 2024 by MadKreator

[MadKreator]

3 hours ago, MAXsenna said:

Right! That did work. But how do I go about making Helios write the correct name for FC modules, and not the generic "FC3"? Mind you. I can now easily do this manually. I just have to have my own "extended" Helios monitor file I do this, that does not get overwritten, and I just transfer the corrections I make.

 

As you can see. I do get conflicts. If Helios can't do this as of now, it's fine. I just do it manually. But it would be super awesome if it could handle this in the future!

 

I will show this to Bluefin to see if he can get it modified for the new FC series naming

[jonsky7]

@MAXsenna

 

If you can let me know the ones I've missed please, I can add them to the list 

[MAXsenna]

@MAXsenna
 
If you can let me know the ones I've missed please, I can add them to the list 

Absolutely! Will do it later today!

Sent from my SM-A536B using Tapatalk

[MAXsenna]

1 hour ago, jonsky7 said:

@MAXsenna

 

If you can let me know the ones I've missed please, I can add them to the list 

Here you go:

Bf-109K-4
C-101EB
C-101CC
Christen Eagle II
F-4E-45MC
F-5E-3
F-5E-3_FC
F-86F Sabre
F-86F_FC
FW-190A8
FW-190D9
I-16
J-11A Note: This one doesn't have it's own folder. Or I just couldn't find it. I did find this refernece in the NS430 entry.lua 
MB-339A
MB-339APAN
MiG-15bis
MiG-15bis_FC
MiG-19P
Mirage-F1BE
Mirage-F1CE
Mirage-F1EE
Mirage-F1M Note: Wild guess as it's not released yet.
MOSQUITOFBMKVI
OH58D
P-47D-30
P-47D-30bl1
P-47D-40
SpitfireLFMkIX
SpitfireLFMkIXCW
Yak-52

[MAXsenna]

14 hours ago, jonsky7 said:

If you have notepad++, https://notepad-plus-plus.org/downloads/

Go to the search tab, select "find in files", do a search for 

try_find_assigned_viewport

filters - *.lua  (just speeds up the search)

Point it at your DCS aircrafts folder.

 

It will return every instance that term is mentioned in the aircraft files, those are the exportable displays.

 

Thanks. Did this. Little astonished until it dawned on me that I have the Helios patches installed.
Rinse and repeat...

I did something else though. I search for ViewportHandling.lua in some of the modules you hadn't listed, and I know hasn't been patches by Helios, like the MB-339, now if I just could learn how to "patch" these files myself. I'm positive IndiaFoxTecho would be more than happy to include it in their files.

 D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\AHR-GPS\AHR-GPS-AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\AHR-GPS\AHR-GPS-FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\FUEL-QTY\FUEL-QTY_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\GunCamera\init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RDU\RDU_AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RDU\RDU_FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RFR\RFR_AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RFR\RFR_FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RGS-2\RGS-2_AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RGS-2\RGS-2_FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_AFT_CHAN_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_AFT_FREQ_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_FWD_CHAN_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_FWD_FREQ_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")

The Mig-19P does have this already for it's radar, while we do know about that situation. Maybe ED could do it. Dunno.

 D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MiG-19P\Cockpit\Radar\Indicator\RP5_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
 

 

I'll research some more in unpatched DCS.

@MadKreator I'm one 100 percent sure heatBlur will be more than happy to include those patched files in their F-4E!

[MAXsenna]

Right!

The Mirage F1 has these:

D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mirage-F1\Cockpit\Common\ALR_300\Indicator\Baked\ALR_300_bake_init.lua (2 hits)
    Line 17:     try_find_assigned_viewport("RIGHT_MFCD")
    Line 20:     try_find_assigned_viewport("LEFT_MFCD")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mirage-F1\Cockpit\Mirage-F1\Mirage-F1BE\Radar_Cyrano_IV_legacy\Indicator\BakedGeneral\CyranoLegacy_bake_general_rear_init.lua (2 hits)
    Line 17:     try_find_assigned_viewport("RIGHT_MFCD")
    Line 20:     try_find_assigned_viewport("LEFT_MFCD")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mirage-F1\Cockpit\Mirage-F1\Mirage-F1BE\SightRepeater\Indicator\BakedGeneral\SightRepeater_bake_general_init.lua (2 hits)
    Line 49:     try_find_assigned_viewport("RIGHT_MFCD")
    Line 52:     try_find_assigned_viewport("LEFT_MFCD")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mirage-F1\Cockpit\Mirage-F1\Mirage-F1_Common\Radar_Cyrano_IV_legacy\Indicator\BakedGeneral\CyranoLegacy_bake_general_init.lua (2 hits)
    Line 17:     try_find_assigned_viewport("RIGHT_MFCD")
    Line 20:     try_find_assigned_viewport("LEFT_MFCD")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mirage-F1\Cockpit\Mirage-F1\Mirage-F1_Common\Radar_Cyrano_IV_legacy\Indicator\Main\CyranoLegacy_init.lua (2 hits)
    Line 39:     try_find_assigned_viewport("RIGHT_MFCD")
    Line 42:     try_find_assigned_viewport("LEFT_MFCD")

And the Kiowa these:

 D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\MFDs\Indicator\Bake\init.lua (1 hit)
    Line  9: -- try_find_assigned_viewport("LEFT_MFCD")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\MFDs\Indicator\initLMFD.lua (1 hit)
    Line 3: try_find_assigned_viewport("LEFT_MFCD")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\OH-58D\Cockpit\MFDs\Indicator\initRMFD.lua (1 hit)
    Line 3: try_find_assigned_viewport("RIGHT_MFCD")

Apologies for the formatting!

[jonsky7]

@MAXsenna

Thanks, though I just meant aircraft with default exportable displays.
Not much point including them in the monitor config if they have nothing to export.

 

You can export any digital display by modifying the displays init.lua file by adding these two lines, usually has an "indicator" folder.

eg
A10C RWR

file - G:\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\indicator\AN_ALR69V_init.lua

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("RWR")


 

Quote

dofile(LockOn_Options.common_script_path.."devices_defs.lua")

indicator_type = indicator_types.COMMON
----------------------
rwr_symbols_bound = 0.027   -- coeff to limit indication on RWR when symbol can't be place on RWR entirely
-------PAGE IDs-------
id_Page =
{
    PAGE_OFF        = 0,
    PAGE_MAIN        = 1,
    PAGE_BIT        = 2
}

id_pagesubset =
{
    COMMON            = 0,
    MAIN            = 1,
    BIT                = 2,
}

page_subsets = {}
page_subsets[id_pagesubset.COMMON]    = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_COMMON_page.lua"
page_subsets[id_pagesubset.MAIN]    = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_MAIN_page.lua"
page_subsets[id_pagesubset.BIT]        = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_BIT_page.lua"

----------------------
pages = {}

pages[id_Page.PAGE_OFF]        = {}
pages[id_Page.PAGE_MAIN]    = {id_pagesubset.COMMON, id_pagesubset.MAIN}
pages[id_Page.PAGE_BIT]        = {id_pagesubset.COMMON, id_pagesubset.BIT}

init_pageID        = id_Page.PAGE_OFF
use_parser        = false

--- master modes
A10C_ALR69V_OFF           = 0 
A10C_ALR69V_MAIN       = 1 
A10C_ALR69V_BIT        = 2

------------------------------------
pages_by_mode                 = {}
clear_mode_table(pages_by_mode, 2, 0, 0)

function get_page_by_mode(master,L2,L3,L4)
    return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4)
end

pages_by_mode[A10C_ALR69V_OFF][0][0][0]            = id_Page.PAGE_OFF
pages_by_mode[A10C_ALR69V_MAIN][0][0][0]        = id_Page.PAGE_MAIN
pages_by_mode[A10C_ALR69V_BIT][0][0][0]            = id_Page.PAGE_BIT

opacity_sensitive_materials = 
{
"font_RWR",
"INDICATION_RWR"
}

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("RWR")

 

[MadKreator]

1 hour ago, MAXsenna said:

Thanks. Did this. Little astonished until it dawned on me that I have the Helios patches installed.
Rinse and repeat...

I did something else though. I search for ViewportHandling.lua in some of the modules you hadn't listed, and I know hasn't been patches by Helios, like the MB-339, now if I just could learn how to "patch" these files myself. I'm positive IndiaFoxTecho would be more than happy to include it in their files.

 D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\AHR-GPS\AHR-GPS-AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\AHR-GPS\AHR-GPS-FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\FUEL-QTY\FUEL-QTY_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\GunCamera\init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RDU\RDU_AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RDU\RDU_FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RFR\RFR_AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RFR\RFR_FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RGS-2\RGS-2_AFT_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\RGS-2\RGS-2_FWD_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_AFT_CHAN_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_AFT_FREQ_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_FWD_CHAN_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
  D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MB-339\Cockpit\Scripts\SRT-651\SRT-651_FWD_FREQ_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")

The Mig-19P does have this already for it's radar, while we do know about that situation. Maybe ED could do it. Dunno.

 D:\Simulators\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MiG-19P\Cockpit\Radar\Indicator\RP5_init.lua (1 hit)
    Line  2: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
 

 

I'll research some more in unpatched DCS.

@MadKreator I'm one 100 percent sure heatBlur will be more than happy to include those patched files in their F-4E!

Like Jonsky said. All that needs done is add the two lines in his last post to any “non-native” viewport file and give it a name, then use that name in your monitor file. Thats literally all the devs need to do to make all viewports exportable. I’m not sure why they only pick and choose a couple of them.
A Helios “Patch” is literally the same thing. In some cases though a “patch” will modify another part of the file. Like in the CH-47 rwr, when you export it, it’s just a giant blob texture unless you also change the line “Draw as Wire” from false to true. Then the symbology is legible on the export. The f-18 rwr is the same way, except you tweak the “stroke thickness and fuzziness” values. 
Adding the lines yourself, of course break IC. Baffles me that the devs writing the scripts don’t just add the lines while they’re typing. It would probably take an extra 3 or 4 seconds

[MAXsenna]

25 minutes ago, MadKreator said:

Adding the lines yourself, of course break IC. Baffles me that the devs writing the scripts don’t just add the lines while they’re typing. It would probably take an extra 3 or 4 seconds

Maybe they just don't realize what it does, and have never tried to export to external screens.

50 minutes ago, jonsky7 said:

Thanks, though I just meant aircraft with default exportable displays.
Not much point including them in the monitor config if they have nothing to export.

True, I just saw the Mustangs were there, so I just did it.

51 minutes ago, jonsky7 said:

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("RWR")

Thanks! I'll have a go at this for the MB-339!

 

[MadKreator]

1 hour ago, MAXsenna said:

Maybe they just don't realize what it does, and have never tried to export to external screens.

I would hope they do.  They have it done already for some of the viewports in each aircraft. The viewport files I examined for each aircraft don’t seem to be copy/pasted across modules, so I’d assume they are each written from scratch and those lines are added only to a few select items. Each module maker of course needs to do their own. It has to be common knowledge I mean Deka did pretty much all of them in the Jf-17. I’m the last person anyone wants to talk to about scripting and I managed to trial and error my way through it in a few minutes. Bluefin and Jonsky’s lives would be much easier if devs would take a few minutes to do this. Hell, I would send ED a check to cover the hour of dev time it would take for them to copy/paste the two lines into each file

Edited September 25, 2024 by MadKreator