Exporting MFDs to a second monitor

[16th Widowmakr]

Can anyone tell me if it is possible to export the MFDs to a second monitor? And if it is how? I have tried searching but haven't had any luck so far. Thanks

[ry-ballz]

Super easy. I have both MFDs as well as the EHSI over a total of 4 monitors.

 

Here's a guide.

https://wiki.hoggitworld.com/view/Exporting_MFCD_Displays

[MadKreator]

In this forum section the first pinned post is the guide to do so. Follow it to the letter. Its not difficult but worth reading through the whole guide once or twice before following it 

Edited November 7, 2022 by MadKreator

[16th Widowmakr]

I got the MFDs working but can't get anything else for the F16 to show up such as the DED, CDU or EHSI

Edited November 6, 2022 by 16th Widowmakr

[Scott-S6]

On 11/6/2022 at 12:19 AM, 16th Widowmakr said:

I got the MFDs working but can't get anything else for the F16 to show up such as the DED, CDU or EHSI

 

The EHSI in the F16 is already configured for export, just create a viewport called EHSI.

For any other displays you want to export, like the DED, you need to edit the LUA file of the relevant display and create a viewport.

The DED's LUA is at:

DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator\DED_init.lua

Add these two lines somewhere in the file (I usually put it at the end) with XXXX replaced by whatever you want to call the viewport:

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

Then create a viewport called whatever you replaced XXXX with.

Edited November 13, 2022 by Scott-S6

[bones1014]

On 11/12/2022 at 8:01 AM, Scott-S6 said:

The EHSI in the F16 is already configured for export, just create a viewport called EHSI.

For any other displays you want to export, like the DED, you need to edit the LUA file of the relevant display and create a viewport.

The DED's LUA is at:

DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator\DED_init.lua

Add these two lines somewhere in the file (I usually put it at the end) with XXXX replaced by whatever you want to call the viewport:

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

Then create a viewport called whatever you replaced XXXX with.

 

This is how I have long been exporting viewports but now these edits violate the multiplayer integrity check.

[Scott-S6]

2 hours ago, bones1014 said:

This is how I have long been exporting viewports but now these edits violate the multiplayer integrity check.

That's up to the server settings. You're out of luck if you can't edit the display component lua files. All of the export methods need it. There are various threads with people complaining and suggesting that the integrity check should be limited to files that might have an impact on gameplay.

[bones1014]

27 minutes ago, Scott-S6 said:

That's up to the server settings. You're out of luck if you can't edit the display component lua files. All of the export methods need it. There are various threads with people complaining and suggesting that the integrity check should be limited to files that might have an impact on gameplay.

It just became a problem in the past two weeks. Something about the IC has changed because I've been doing the same integrity checks for years.

[Scott-S6]

4 minutes ago, bones1014 said:

It just became a problem in the past two weeks. Something about the IC has changed because I've been doing the same integrity checks for years.

Yep, they changed it recently.