[How to] Multi monitor MFCD display export set-up guide - Nov 2024 (updated)

Stompy · April 22, 2023

On 4/19/2023 at 10:16 PM, jonsky7 said:

I'm sorry I don't know any way other than removing the mod. Your best bet is to use a mod manager like OvGME. Then it's as easy as double clicking the mod to install/remove it.

Can I use a mod manager to replace the files that I had to do the text editing in too, so it's putting in the three files in the zip folder plus (in my case) the 4 files I had to edit to point at the three new files? I have little experience with mod managers, sorry.

jonsky7 · April 22, 2023

3 hours ago, Stompy said:

Can I use a mod manager to replace the files that I had to do the text editing in too, so it's putting in the three files in the zip folder plus (in my case) the 4 files I had to edit to point at the three new files? I have little experience with mod managers, sorry.

You certainly can yes. You just have to be aware that the files that you need to edit may get updated from time to time, like something else in the code may change, not very often in my experience. If something does change, I just copy the original file over to the mod folder (see video) and do the edit again.

You store a modified set of files in a separate "mod" folder, and the mod manager takes those files and overwrites the originals, but it makes a backup of the originals for when you want to disable the mod.

The only downside to using a mod manager is that you need to keep a copy of the modified files, and like I mentioned it creates a backup. This isn't really a big deal when you're just dealing with .lua files as they are small, but a mod that would normally be 1GB, will effectively become 2GB. The price you pay for the convenience of a mod manager.

You can get OvGME here ----> https://wiki.hoggitworld.com/view/OVGME
and
This video isn't too bad at explaining OvGME

Edited April 22, 2023 by jonsky7

JIGGAwest · April 22, 2023

15 hours ago, The Billder said:

Wanted to clarify frame rate issues with exporting to MFDs. I have a 144hz 34” ultra wide. A second single monitor that’s 720p60hz. Both plugged into GPU. 3440x2160 overall
I’ve read that a 60hz additional display will effectively lower your primary monitor frame rate to 60hz as well? (Despite what the fps counter suggests?)

If so, are there any differences in regards to this issue for the usb type vs HDMI type external displays?

I’ve tried reducing my primary to 60fps and the frame tearing was terrible. With VSYNC off

thanks

I've not experienced this issue.

My main is 120hz and second monitor is 60hz.

Main monitor is HDMI and second monitor is mini HDMI to Display port adapter.

You should be able to set refresh rate individually in windows display settings under advanced.

Edited April 22, 2023 by JIGGAwest

Scott-S6 · April 24, 2023

On 4/22/2023 at 11:37 PM, JIGGAwest said:

You should be able to set refresh rate individually in windows display settings under advanced.

This is correct. If you're screen mirroring or using g-sync on one of the displays then it's a bit more complicated.

Think404 · May 3, 2023

Hello. When I export my MFD's to my second monitor it looks like this:

F18:

A10:

The MFD in the A10 looks almost normal, but has those weird yellow lines at the sides.

What could this be? In the cockpit everything looks normal.

I'm using a 1920x1080 monitor on the left, a 2560x1440 in the center and an other 1920x1080 on the right. I want the MFD's on the right monitor.

This is my code:

Viewports =
	{
	Center =
		{
		x = 1920;
		y = 0;
		width = 2560;
		height = 1440;
		viewDx = 0;
		viewDy = 0;
		aspect = 2560/1440;
		}
	}

	LEFT_MFCD =
		{
		x = 4490;
		y = 100;
		width = 368;
		height = 368;
		}

	RIGHT_MFCD =
		{
		x = 5000;
		y = 100;
		width = 368;
		height = 368;
		}
		

UIMainView = Viewports.Center
GU_MAIN_VIEWPORT = Viewports.Center

No1sonuk · May 3, 2023

That looks like it might be a problem with your computer output to the monitor.

How are you connecting the second monitor to the computer?

Think404 · May 4, 2023

Oh nevermind, just found this topic:

Think I'm not running the latest version. Should be fixed now.

Edited May 4, 2023 by Think404

Flappie · May 4, 2023

@Think404 I thought this MT bug had been fixed with the latest update.

Is your DCS OB up-to-date? (2.8.4.39313)

Think404 · May 4, 2023

1 minute ago, Flappie said:

@Think404 I thought this MT bug had been fixed with the latest update.

Is your DCS OB up-to-date? (2.8.4.39313)

Yes thanks for the reply. Should be fixed when I update to latest version.

Cyclone_ZAR · June 21, 2023

Thanks Jonsky for the detailed guide.

Flying the F16 - I'm experimenting with trying to get the left MFD to display in the created view port.

I've set the the correct resolution in DCS

I have followed all the steps - and the view port does get created on my second screen, however it simply mirrors my main cockpit view when in flight and does not export the LEFT_MFCD?

Is there something I may be missing? (I've tried both the single thread and MT versions - same result)

Any assistance would be greatly appreciated!

My .lua monitor setup is :-

_ = function(p) return p; end;

name = _('1 Screen and MFD Screen');

Description = 'Configuration with 1 main monitors and a small MFD'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

viewDx = 0;

viewDy = 0;

aspect = 2560/1440;

},

LEFT_MFCD =

{

x = 2552;

y = 8;

width = 480;

height = 480;

viewDx = 0;

viewDy = 0;

}

UIMainView =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

}

GU_MAIN_VIEWPORT =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

}

JIGGAwest · June 21, 2023

11 hours ago, Cyclone_ZAR said:

Thanks Jonsky for the detailed guide.

Flying the F16 - I'm experimenting with trying to get the left MFD to display in the created view port.

I've set the the correct resolution in DCS

I have followed all the steps - and the view port does get created on my second screen, however it simply mirrors my main cockpit view when in flight and does not export the LEFT_MFCD?

Is there something I may be missing? (I've tried both the single thread and MT versions - same result)

Any assistance would be greatly appreciated!

My .lua monitor setup is :-

_ = function(p) return p; end;

name = _('1 Screen and MFD Screen');

Description = 'Configuration with 1 main monitors and a small MFD'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

viewDx = 0;

viewDy = 0;

aspect = 2560/1440;

},

LEFT_MFCD =

{

x = 2552;

y = 8;

width = 480;

height = 480;

viewDx = 0;

viewDy = 0;

}

}

UIMainView =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

}

GU_MAIN_VIEWPORT =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

}

Instead of defining separately UIMainView and GU_MAIN_VIEWPORT

You can instead use.

UIMainView = Viewports.Center
GU_MAIN_VIEWPORT = Viewports.Center

You also have a , after the last } in the center definition. This could be an issue. And you missing another bracket } to close out the viewport.

The location of the last bracket currently is including the LEFT_ MFCD. Try deleting that.

_ = function(p) return p; end;

name = _('1 Screen and MFD Screen');

Description = 'Configuration with 1 main monitors and a small MFD'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 2560;

height = 1440;

viewDx = 0;

viewDy = 0;

aspect = 2560/1440;

}

LEFT_MFCD =

{

x = 2552;

y = 8;

width = 480;

height = 480;

viewDx = 0;

viewDy = 0;

}

UIMainView = Viewports.Center

GU_MAIN_VIEWPORT = Viewports.Center

Edited June 22, 2023 by JIGGAwest

Cyclone_ZAR · June 22, 2023

8 hours ago, JIGGAwest said:

The location of the last bracket currently is including the LEFT_ MFCD. Try deleting that.

That did it!

Thank you! - my programming habits saw the LEFT_MFSD as a viewpoint - so therefore should be an element in the ViewPorts element - which strictly should be

Thanks again!

Cyclone_ZAR · June 22, 2023

1 hour ago, Cyclone_ZAR said:

That did it!

Thank you! - my programming habits saw the LEFT_MFSD as a viewpoint - so therefore should be an element in the ViewPorts element - which strictly should be

Thanks again!

After relooking at it with fresh eyes - it makes sense now

Thanks again!

I have noticed your FPS takes at least a 20fps hit with having exported MFSD's (well in my case with only one exported at the moment)

plockhead69 · June 22, 2023

Hello everyone!

Have anybody exported Strike eagles mfds/mpds? It was just released and I tried but I think my display names are wrong..

Martus · June 23, 2023

I have a 1080p display above a 4k.
The 4k is the main screen. I've successfully configured the viewport and MFDs, but end up with an off-center HMCS, as seen in the screenie.

Is there a way to offset it?

My display setup...

_ = function(p) return p; end;
name = _('Martus custom');
Description = 'Displays on top screen'
xOffset = 460
mfcdWidth = 800
rwrWidth = 320
Viewports =
{
    Center =
    {
        x = 0;
        y = 1080;
        width = screen.width;
        height = screen.height;
        viewDx = 0;
        viewDy = 0;
        aspect = screen.aspect;
    }}

    LEFT_MFCD = -- L DDI/MFD
    {
        x = xOffset;
        y = 1080 - mfcdWidth;
        width = mfcdWidth;
        height = mfcdWidth;
    }
    RIGHT_MFCD = -- R DDI/MFD
    {
        x = xOffset + 1920 - mfcdWidth;
        y = 1080 - mfcdWidth;
        width = mfcdWidth;
        height = mfcdWidth;
    }

    F16_RWR = -- RWR left-top
    {
        x = xOffset + mfcdWidth;
        y = 1080 - rwrWidth - 25;
        width = rwrWidth;
        height = rwrWidth;
    }

    UIMainView =
    {
        x = 0;
        y = 1080;
        width = 3840;
        height = 2160;
    }

    GU_MAIN_VIEWPORT =
    {
        x = 0;
        y = 0;
        width = 3840;
        height = 2160;
    }

jonsky7 · June 23, 2023

18 hours ago, Martus said:

I have a 1080p display above a 4k.
The 4k is the main screen. I've successfully configured the viewport and MFDs, but end up with an off-center HMCS, as seen in the screenie.

Is there a way to offset it?

My display setup...

_ = function(p) return p; end;
name = _('Martus custom');
Description = 'Displays on top screen'
xOffset = 460
mfcdWidth = 800
rwrWidth = 320
Viewports =
{
    Center =
    {
        x = 0;
        y = 1080;
        width = screen.width;
        height = screen.height;
        viewDx = 0;
        viewDy = 0;
        aspect = screen.aspect;
    }}

    LEFT_MFCD = -- L DDI/MFD
    {
        x = xOffset;
        y = 1080 - mfcdWidth;
        width = mfcdWidth;
        height = mfcdWidth;
    }
    RIGHT_MFCD = -- R DDI/MFD
    {
        x = xOffset + 1920 - mfcdWidth;
        y = 1080 - mfcdWidth;
        width = mfcdWidth;
        height = mfcdWidth;
    }

    F16_RWR = -- RWR left-top
    {
        x = xOffset + mfcdWidth;
        y = 1080 - rwrWidth - 25;
        width = rwrWidth;
        height = rwrWidth;
    }

    UIMainView =
    {
        x = 0;
        y = 1080;
        width = 3840;
        height = 2160;
    }

    GU_MAIN_VIEWPORT =
    {
        x = 0;
        y = 0;
        width = 3840;
        height = 2160;
    }

Personally I'd just try using actual numbers for your centre viewport entry, so

Center =
    {
        x = 0;
        y = 1080;
        width = 3840;
        height = 2160;
        viewDx = 0;
        viewDy = 0;
        aspect = 3840/2160;
    }
}

Notice also the double brackets at the end of the center, ie }}
I'm not really a coder but mine looks like
}

}

I'd also set your GU_MAIN_VIEWPORT to the same as your UI_Mainview, adjusting the y position as below

GU_MAIN_VIEWPORT=
    {
        x = 0;
        y = 1080;
        width = 3840;
        height = 2160;
    }

Edited June 23, 2023 by jonsky7

jonsky7 · June 23, 2023

21 hours ago, plockhead69 said:

Hello everyone!

Have anybody exported Strike eagles mfds/mpds? It was just released and I tried but I think my display names are wrong..

Patch notes say it's not yet possible apparently

DCS: F-15E by RAZBAM - Known Issues

Bombs dropped in AUTO mode can land long of target for wings level release. It is recommended to do a dive bombing for improved accuracy.
CBUs can open prematurely, specially if dropped above 1500 ft AGL
HUD Repeater in MPCD sometimes not visible
MFD exports not yet implemented
Volume control for TEWS & TACAN WIP
WSO HOTAS commands WIP

Edited June 23, 2023 by jonsky7

plockhead69 · June 24, 2023

16 hours ago, jonsky7 said:

Patch notes say it's not yet possible apparently

DCS: F-15E by RAZBAM - Known Issues

Bombs dropped in AUTO mode can land long of target for wings level release. It is recommended to do a dive bombing for improved accuracy.

CBUs can open prematurely, specially if dropped above 1500 ft AGL

HUD Repeater in MPCD sometimes not visible

MFD exports not yet implemented

Volume control for TEWS & TACAN WIP

WSO HOTAS commands WIP

Okay thank you

AstroEma · July 2, 2023

quick question on exporting the MFDs for various planes. Is it possible to use the a single Monitor.lua file to export MFDs for various planes? I fly different aircrafts and change them on the fly and was wondering if the lua file will support different sections: i.e F18, F16. A10C, F14... etc.

Or, I need to exit DCS, change the lua file each time I want to change the aircraft?

Cheers!

MadKreator · July 2, 2023

20 minutes ago, AstroEma said:

quick question on exporting the MFDs for various planes. Is it possible to use the a single Monitor.lua file to export MFDs for various planes? I fly different aircrafts and change them on the fly and was wondering if the lua file will support different sections: i.e F18, F16. A10C, F14... etc.

Or, I need to exit DCS, change the lua file each time I want to change the aircraft?

Cheers!

No need to change the lua file. Once you setup exported mfd’s, it will work with all planes that support it. You just need to set the monitor type in settings as lmfd+monitor+rmfd … however some mfds are larger than others.. the a-10 exports are larger than the f-16 so if you’re fitting them inside a set of mfd cougars, you may have to play with the sizes until you find a good compromise. Its good and also bad that it covers every aircraft, good because it’s easiest, bad because you have the least control and have to mess with lua files.. You could also download and use Helios to have ultimate control and export much more than just mfd’s if you want to.

Edited July 2, 2023 by MadKreator

AstroEma · July 2, 2023

Thanks for your help! What about the F14, Mirage and Ka50III though as they are not called MFDs ? How do I export those in the same file?

I have the Winwing MIP by the way and trying to find a way not to restart DCS every time I want to fly a different aircraft than one that does not have LMFD RMFD etc exports

Edited July 2, 2023 by AstroEma

No1sonuk · July 2, 2023

I thought the DCS monitor config calls them all the same name if they're in the same position.

If it doesn't, I'd imagine just telling it to use the same screen position for the different aircraft MFDs would ignore the ones not being supplied.

MadKreator · July 2, 2023

11 hours ago, AstroEma said:

Thanks for your help! What about the F14, Mirage and Ka50III though as they are not called MFDs ? How do I export those in the same file?

I have the Winwing MIP by the way and trying to find a way not to restart DCS every time I want to fly a different aircraft than one that does not have LMFD RMFD etc exports

Three aircraft I don’t fly, of course.. you may have to do custom luas…However, as I said, Helios does have exports for f-14, ka-50 and mirage, and lots of others.. you would literally drag the viewports from the “toolbox” onto the correct screen, position and size them to your MIP’s. They all get combined in a single monitor config file, then you just run the helios ”control center” app and select which aircraft you’re in to display the appropriate viewports. Never have to change a thing in dcs or even touch a lua file. Select Helios as your monitor ( and entering the total screenspace resolution), which I assume is done already with the MIP’s and uncheck fullscreen. ….. I don’t know much about setting up the monitor files manually, but if you give helios a shot, hop over to Captnzeen discord channel and DM me or tag me and I can help you get going if you have issues. There’s not really any great instructions to use it lol

DCS many indeed call them the same thing when exporting as @No1sonuk said. Or it may know, internally what its supposed to export even though the monitor config says MFD in the title.. Last time I used the dcs MFD config, I only had the 16, 18, a-10, and harrier. All worked no problem with the same config file.

Edited July 2, 2023 by MadKreator

jonsky7 · July 3, 2023

On 7/2/2023 at 4:32 AM, AstroEma said:

quick question on exporting the MFDs for various planes. Is it possible to use the a single Monitor.lua file to export MFDs for various planes? I fly different aircrafts and change them on the fly and was wondering if the lua file will support different sections: i.e F18, F16. A10C, F14... etc.

Or, I need to exit DCS, change the lua file each time I want to change the aircraft?

Cheers!

Yes, it is possible, but depending on what you want to do it may break the integrity check on some servers if you are playing multiplayer.

For most aircraft the display exports are labelled LEFT_MFCD and RIGHT_MFCD, if you have two (or more) aircraft that have these export names, and you want to display the MFCDs of each aircraft in a different location, then you can modify the MFCD output name by modifying a lua file for each of the aircraft.

E.g. you rename the F16 Left MFCD export name from LEFT_MFCD to F16_LEFT_MFCD
or
if your aircraft have different names for the displays you can just add them to the config file.

eg

Viewports

Centre
LEFT_MFCD
RIGHT_MFCD
F16_LEFT_MFCD
F16_RIGHT_MFCD
ABRIS
SCHVAL
F14_EDI
UI_MainView

On the first page of this topic, you will find a post with all the currently available default export names. Some aircraft export names look like
eg Ka-50
mods/aircraft/Ka-50/cockpit/scripts/ABRIS/BAKE/init.lua
says
try_find_assigned_viewport("ABRIS","RIGHT_MFCD")

if the output name contains two names like the above, then DCS will scan your monitor config file for a definition of where to put the first name (ABRIS), if it doesn't find ABRIS, it will look for the second name (RIGHT_MFCD) and put it there.
Unfortunately, most aircraft only have (LEFT_MFCD) and (RIGHT_MFCD) defined, which is why there is a need to modify the game files if you want to display them differently (size,location)

Here is my monitor config file and my modified lua files. You can use a mod manager for the modified game files.
You can either use them, or modify them to your liking, or just have a look to see what I'm talking about.

Display Exports.zip

JB Camera Cougar.lua

Note: Use Notepad++

Edited July 4, 2023 by jonsky7

scrupeus · July 28, 2023

On 7/2/2023 at 2:03 PM, AstroEma said:

Thanks for your help! What about the F14, Mirage and Ka50III though as they are not called MFDs ? How do I export those in the same file?

I have the Winwing MIP by the way and trying to find a way not to restart DCS every time I want to fly a different aircraft than one that does not have LMFD RMFD etc exports

On 7/4/2023 at 4:28 AM, jonsky7 said:

Yes, it is possible, but depending on what you want to do it may break the integrity check on some servers if you are playing multiplayer.

For most aircraft the display exports are labelled LEFT_MFCD and RIGHT_MFCD, if you have two (or more) aircraft that have these export names, and you want to display the MFCDs of each aircraft in a different location, then you can modify the MFCD output name by modifying a lua file for each of the aircraft.

E.g. you rename the F16 Left MFCD export name from LEFT_MFCD to F16_LEFT_MFCD
or
if your aircraft have different names for the displays you can just add them to the config file.

eg

Viewports

Centre
LEFT_MFCD
RIGHT_MFCD
F16_LEFT_MFCD
F16_RIGHT_MFCD
ABRIS
SCHVAL
F14_EDI
UI_MainView

On the first page of this topic, you will find a post with all the currently available default export names. Some aircraft export names look like
eg Ka-50
mods/aircraft/Ka-50/cockpit/scripts/ABRIS/BAKE/init.lua
says
try_find_assigned_viewport("ABRIS","RIGHT_MFCD")

if the output name contains two names like the above, then DCS will scan your monitor config file for a definition of where to put the first name (ABRIS), if it doesn't find ABRIS, it will look for the second name (RIGHT_MFCD) and put it there.
Unfortunately, most aircraft only have (LEFT_MFCD) and (RIGHT_MFCD) defined, which is why there is a need to modify the game files if you want to display them differently (size,location)

Here is my monitor config file and my modified lua files. You can use a mod manager for the modified game files.
You can either use them, or modify them to your liking, or just have a look to see what I'm talking about.

Display Exports.zip

JB Camera Cougar.lua 4.75 kB · 3 downloads

Note: Use Notepad++

First, and most importantly, a huge thanks to @jonsky7 for all your work not only creating this guide but supporting it for more than two years!

---

There is an easy way to include multiple aircraft in a single monitor config file without renaming display exports.

NOTES:

Apparently, the method below worked many years ago, stopped working for a few years but is working again now (at least with OpenBeta 2.8.7).
As others have mentioned, many aircraft have common names for display exports (LEFT_MFCD, RIGHT_MFCD, etc.) so you may not need customisation for each aircraft.
As also mentioned by others, any display export that doesn't have a matching name will simply be ignored (meaning you could have an 'F14_EDI' entry for example and it would simply be ignored for other aircraft).
If you want to use a display that isn't exported for a given aircraft, then you will still need to add a 'try_find_assigned_viewport' function call into the aircraft's appropriate Lua file (details of how to do that can be found elsewhere).
I am by no means an expert with this stuff but it's working for me!!!

The following method is useful if you want different display arrangements for different aircraft, without having to customise display export names.

The solution is to use a 'reconfigure_for_unit' function and its passed 'unit_type' parameter...

(Note: this is in your monitors config file, after 'name =', 'description =', 'Viewports =', etc.)
Instead of just having a single, generic entry in your monitors config file that will be used for all aircraft:

LEFT_MFCD =
{
    ...
}
RIGHT_MFCD =
{
    ...
}

wrap them in a 'reconfigure_for_unit' function and define entries for each unit (aircraft, etc.):

function reconfigure_for_unit(unit_type) 
    if unit_type == "AH-64D_BLK_II" then
        LEFT_MFCD =
        {
            ...
        }
        RIGHT_MFCD =
        {
            ...
        }
        TEDAC =
        {
            ...
        }
    elseif unit_type == "FA-18C_hornet" then
        LEFT_MFCD =
        {
            ...
        }
        RIGHT_MFCD =
        {
            ...
        }
        CENTER_MFCD =
        {
            ...
        }
    elseif unit_type == "F-16C_50" then
        ...
    elseif unit_type == "F-14A-135-GR" then
        ...
    else  -- FALLBACK FOR UNITS NOT MATCHED ABOVE
        LEFT_MFCD =
        {
            ...
        }
        RIGHT_MFCD =
        {
            ...
        }
    end
end

(you need to replace '...' with appropriate values of 'x', 'y', 'width' and 'height' for each entry)

NOTE: There are various ways of finding unit type names - I got them from a Helios config file. Here's a copy:

Spoiler

A-10C

A-10C_2

F-14B

F-14A-135-GR

F-16C_50

FA-18C_hornet

A-10A

F-15C

MiG-29

Su-25

Su-27

Su-33

AV8BNA

UH-1H

Ka-50

Ka-50_3

AH-64D_BLK_II

AJS37

L-39

L-39C

L-39ZA

Mi-8MT

MiG-21Bis

P-51D

P-51D-30-NA

TF-51D

SA342

SA342L

SA342M

SA342Mistral

SA342Minigun

JF-17

Thanks again to @jonsky7 and everyone else who has contributed - it's been a huge help to me!

Sign In

[How to] Multi monitor MFCD display export set-up guide - Nov 2024 (updated)

Recommended Posts

Stompy

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

jonsky7

jonsky7

jonsky7

jonsky7

JIGGAwest

Scott-S6

Think404

No1sonuk

Think404

Flappie

Think404

Cyclone_ZAR

JIGGAwest

Cyclone_ZAR

Cyclone_ZAR

plockhead69

Martus

jonsky7

jonsky7

DCS: F-15E by RAZBAM - Known Issues

plockhead69

DCS: F-15E by RAZBAM - Known Issues

AstroEma

MadKreator

AstroEma

No1sonuk

MadKreator

jonsky7

scrupeus

Recently Browsing 0 members