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

[sgtoinkz]

Hello all! I have a few question regarding the T-45 mod and exporting the MFD's onto my MIP. 

Has anyone here successfully exported the L and R MFD's of the T45 mod?

I have taken the "wwtmonitor.lua" that simapp created, copied and renamed it for testing exports without simapp running to learn how to export on my own. I created a MonitorSetup folder in my saved games/dcs/config folder with the renamed lua file. I can see it and select it from the drop down menu in the "monitors" options.  

 The A-10, F-18, AV-8 etc. will automatically export no problems. So I figured to give the T-45 mod a try with no luck, it won't automatically export. I figured I am at a point where I need to make a manual entry into the T-45's .lua files? I have found both the left and right "indicator" files in the mods directory for the T45. I need a little help with how to make the entry into those specific files so an export can take place. I can't fully grasp from the guide mentioned in this thread on how to input the numbers needed for export.

Thank everyone in advance for your time and advice with my question. I will respond as soon as I can...working and flying DCS from Japan.  

 

[jonsky7]

8 hours ago, sgtoinkz said:

Hello all! I have a few question regarding the T-45 mod and exporting the MFD's onto my MIP. 

Has anyone here successfully exported the L and R MFD's of the T45 mod?

I have taken the "wwtmonitor.lua" that simapp created, copied and renamed it for testing exports without simapp running to learn how to export on my own. I created a MonitorSetup folder in my saved games/dcs/config folder with the renamed lua file. I can see it and select it from the drop down menu in the "monitors" options.  

 The A-10, F-18, AV-8 etc. will automatically export no problems. So I figured to give the T-45 mod a try with no luck, it won't automatically export. I figured I am at a point where I need to make a manual entry into the T-45's .lua files? I have found both the left and right "indicator" files in the mods directory for the T45. I need a little help with how to make the entry into those specific files so an export can take place. I can't fully grasp from the guide mentioned in this thread on how to input the numbers needed for export.

Thank everyone in advance for your time and advice with my question. I will respond as soon as I can...working and flying DCS from Japan.  

 

I've just had a look at the T-45 mod for you and the export names are:-

MFDL
MFDR

So you need to put entries in your monitor config file with reference to above. (see below)

Alternatively, you could change those names to LEFT_MFCD and RIGHT_MFCD and then they will export into the same positions as the A10, F18 etc.

In the files
VNAO_T45\Cockpit\Scripts\Displays\MFDL\Indicator\init.lua  ---->  try_find_assigned_viewport("MFDL") to try_find_assigned_viewport("LEFT_MFCD")
and
VNAO_T45\Cockpit\Scripts\Displays\MFDR\Indicator\init.lua ---->  try_find_assigned_viewport("MFDR") to try_find_assigned_viewport("RIGHT_MFCD")
eg

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

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

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

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

 

It works but they don't look great, going to need a bit of modifying the code for the font I reckon

Edited September 8, 2023 by jonsky7

[sgtoinkz]

2 hours ago, jonsky7 said:

I've just had a look at the T-45 mod for you and the export names are:-

MFDL
MFDR

So you need to put entries in your monitor config file with reference to above. (see below)

Alternatively, you could change those names to LEFT_MFCD and RIGHT_MFCD and then they will export into the same positions as the A10, F18 etc.

In the files
VNAO_T45\Cockpit\Scripts\Displays\MFDL\Indicator\init.lua  ---->  try_find_assigned_viewport("MFDL") to try_find_assigned_viewport("LEFT_MFCD")
and
VNAO_T45\Cockpit\Scripts\Displays\MFDR\Indicator\init.lua ---->  try_find_assigned_viewport("MFDR") to try_find_assigned_viewport("RIGHT_MFCD")
eg

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

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

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

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

 

It works but they don't look great, going to need a bit of modifying the code for the font I reckon

 

Thank you for the help and your dedication to the community! It works! I applied both of your methods to fully understand them and chose to stick with the alternate method. The font definitely needs to be worked on. Do you think there would be anything buried within the WWsimapp files that could lead to a correction of the fonts? perhaps somewhere in the F-18 since that's what the MIP was designed around?

[Constable]

How do I render my main window in a different resolution in the lua?

I want to render the game at 2560x1440 on my main monitor instead of the native 3840x2160 that it runs at in Windows. How do I do that in the MonitorSetup lua file? I have tried changing just "aspect" but it doesn't seem to have the desired effect. If I change the resolution in DCS, it messes up the setup.

 

Thanks for the help. Wonderful thread.

[BaronVonVaderham]

On 9/8/2023 at 11:39 AM, sgtoinkz said:

Thank you for the help and your dedication to the community! It works! I applied both of your methods to fully understand them and chose to stick with the alternate method. The font definitely needs to be worked on. Do you think there would be anything buried within the WWsimapp files that could lead to a correction of the fonts? perhaps somewhere in the F-18 since that's what the MIP was designed around?

That probably requires some digging into lua files, if it’s even possible. I agree with you though that the fonts in the t-45 (also fit the a-29) are really quite poor. The f-16 is pretty clear!

Note that it has nothing to do with winwing or simapppro. The displays used are dumb displays, meaning they just convert a video signal into pixels. 
 

As a little knowledge snippet:  aircraft can use dumb or smart displays. The former only convert video into pixels, similar to our desktop displays. The latter do lots of processing for graphics generation

18 hours ago, Constable said:

How do I render my main window in a different resolution in the lua?

I want to render the game at 2560x1440 on my main monitor instead of the native 3840x2160 that it runs at in Windows. How do I do that in the MonitorSetup lua file? I have tried changing just "aspect" but it doesn't seem to have the desired effect. If I change the resolution in DCS, it messes up the setup.

 

Thanks for the help. Wonderful thread.

You can’t. You need to change the resolution of your main monitor in windows as well. Of course you could do it only in the lua, but your main display will show black bars.

Note that if you do change your main display resolution, don’t forget to recalculate the positions of all other displays. 

Edited September 23, 2023 by BaronVonVaderham

[jonsky7]

18 hours ago, Constable said:

How do I render my main window in a different resolution in the lua?

I want to render the game at 2560x1440 on my main monitor instead of the native 3840x2160 that it runs at in Windows. How do I do that in the MonitorSetup lua file? I have tried changing just "aspect" but it doesn't seem to have the desired effect. If I change the resolution in DCS, it messes up the setup.

 

Thanks for the help. Wonderful thread.

Baraon has just beat me to it while I was doing some testing.

As Baron has said, it doesn't seem possible to run the game using a lower resolution while also utilising a multi-monitor configuration.

Changing the center viewpoint settings only seems to make the picture smaller on the screen, and checking fullscreen has no effect.

So as Baron has pointed out, the only way to do this is to first change the resolution in Windows display settings, you will then have to reconfigure your monitor config file to place MFCDs etc according the new resolution.

[lone82]

Any fix for the CA Sights looking like this with MFD's exported? @jonsky7

[jonsky7]

2 hours ago, lone82 said:

Any fix for the CA Sights looking like this with MFD's exported? @jonsky7

Pretty sure I fixed mine by adding the 

GU_MAIN_VIEWPORT

entry to the end of the config file.

Give it the same parameters as your main screen.

 

You can see an example on page 1 where I describe the sections of the monitor config file.

[lone82]

9 hours ago, jonsky7 said:

Pretty sure I fixed mine by adding the 

GU_MAIN_VIEWPORT

entry to the end of the config file.

Give it the same parameters as your main screen.

 

You can see an example on page 1 where I describe the sections of the monitor config file.

THis is how I have it. Top monitor #2 is 3840x2160 and bottom "Main #1" monitor is 3840x1080

 

_  = function(p) return p end
name = _('test2')
description = 'JF17, KA50_3, SU25T'
Viewports =
{
    Center =
    {
         x = 0;
         y = 2160;
         width  = 3840;
         height = 1080;
         viewDx = 0;
         viewDy = 0;
         aspect = 3840/1080;
    }
}

function reconfigure_for_unit(unit_type) 

if unit_type == "JF-17" then

  CENTER_MFCD =
{
    x = 0;
    y = 0;
    width = 1920;
    height = 2160;
}

  RIGHT_MFCD =
{
    x = 1920;
    y = 0;
    width = 1920;
    height = 2160;
}

elseif unit_type == "Ka-50_3" then

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

elseif unit_type == "Su-25T" then

RIGHT_MFCD =
{
    x = 0;
    y = 0;
    width = 3840;
    height = 2160;
}
end
end

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

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

[Darkdiz]

Hey has anyone figured out the F-15E kneeboard, and how to get it to display where you want it? Apparently RAZBAM kneeboards are different, and they don't display or can be manipulated like the standard (say A-10C) kneeboard positions

[jonsky7]

On 10/12/2023 at 3:23 AM, lone82 said:

THis is how I have it. Top monitor #2 is 3840x2160 and bottom "Main #1" monitor is 3840x1080

 

_  = function(p) return p end
name = _('test2')
description = 'JF17, KA50_3, SU25T'
Viewports =
{
    Center =
    {
         x = 0;
         y = 2160;
         width  = 3840;
         height = 1080;
         viewDx = 0;
         viewDy = 0;
         aspect = 3840/1080;
    }
}

function reconfigure_for_unit(unit_type) 

if unit_type == "JF-17" then

  CENTER_MFCD =
{
    x = 0;
    y = 0;
    width = 1920;
    height = 2160;
}

  RIGHT_MFCD =
{
    x = 1920;
    y = 0;
    width = 1920;
    height = 2160;
}

elseif unit_type == "Ka-50_3" then

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

elseif unit_type == "Su-25T" then

RIGHT_MFCD =
{
    x = 0;
    y = 0;
    width = 3840;
    height = 2160;
}
end
end

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

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

I can't get to my computer at the moment, I'm on holiday.

Is the sight not filling monitor 1?

Do you use monitor 1 as your main display, like cockpit view etc?

In windows settings, is monitor 1 or 2 set to main display?

You could try deleting the viewdx viewdy and aspect parameters from uimainview and gumainviewport entries. I have them setup like mfd.

 

[ZuluThreeZero]

Hi @jonsky7, looks like you're the guru on multi-monitor setups - I've sorted the basics but am looking to try to pull off something possibly more involved, think you came close to covering it with the F-15E discussion. Would it be possible to set it up such that if you are in the AH-64 pilot seat, your right screen displays the right MFCD, but if you're in the CPG seat, it displays the TEDAC / TADS? At the moment my TEDAC display is shown over the right MFCD rather than replacing it, in both seats. I've tried both creating a separate TEDAC viewport in the monitor setup file, and setting the TEDAC cfg file to search for RIGHT_MFCD.

I'd also be fine with still having them overlap, but only in the front seat, and hidden in the back seat.

I guess the question boils down to, is it possible to have the TEDAC only exported when occupying the CPG seat?

Thanks in advance!

[No1sonuk]

@ZuluThreeZero Is that something Helios could do? If not dynamically turn a viewport on and off, maybe resize it? 

[jonsky7]

Hi @ZuluThreeZero

I'm sorry to say that ED has not given us the ability to define a multicrew position in the monitor setup file, at least not that I know of.

The TEDAC remaining on screen but FROZEN when switching from CPG to PLT seat seems to be a "bug"  

I've just raised it as such
 

 

[ZuluThreeZero]

Thanks guys, no worries, for now I'll just write up to have the TEDAC layer over one of the MFCDs and see if it's worth it.... to be honest just staring at it in the main viewport isn't too bad, will have a play around. Cheers!

 

[speakinginsilver]

Hi all, thanks for this great thread. Is there any way to export MFCDs while using VR? I know it may sound weird, but this would be quite interesting for me during startup, setting up waypoints, etc.

[jonsky7]

13 hours ago, speakinginsilver said:

Hi all, thanks for this great thread. Is there any way to export MFCDs while using VR? I know it may sound weird, but this would be quite interesting for me during startup, setting up waypoints, etc.

I don't use VR so I haven't tested this personally, but I believe it is possible.

1. add this line to your monitor config file, apparently it can go at the very end under UIMainView, and GU_MAIN_VIEWPORT (if you have it)
VR_allow_MFD_out_of_HMD = true

2. make sure "Use DCS System Resolution" is checked in the VR settings in DCS, won't work without this setting checked.

3. adjust the Monitor config file to place the MFDs in the desired position.

 

Please report back if it works, and I'll add it to the main part of the guide. It would be helpful to others if you also make a note of any drawbacks.

Cheers

Edited November 27, 2023 by jonsky7

[William Trembletts]

Hey, I'm having some trouble with this. I've got the same set up as you but for some reason my MFDs aren't appearing, I don't know what I'm doing wrong. I'm not that good at understanding software so I've probably buggered something up, but any help would go greatly appreciated. 

[jonsky7]

6 hours ago, William Trembletts said:

Hey, I'm having some trouble with this. I've got the same set up as you but for some reason my MFDs aren't appearing, I don't know what I'm doing wrong. I'm not that good at understanding software so I've probably buggered something up, but any help would go greatly appreciated. 

Hi William

I'm sure we can get this figured out for you.

Can you tell us your setup?

How many monitors do you have, what resolution are they, and how are they arranged in window display settings? A screenshot is always helpful

And

Where do you want stuff to display?

If you've already had a go, you could upload your monitor config file and we can maybe check for errors.

Cheers

Jon

[Red_Pilot]

Hello! After installing the second monitor, I do not see the control indicator in FC aircraft (MiG29, Su 27 and 33) and unfortunately I cannot find where (init_file?) the files for the indicator are located. Maybe someone knows the location of these files for these aircraft?

[jonsky7]

On 12/21/2023 at 1:42 PM, Red_Pilot said:

Hello! After installing the second monitor, I do not see the control indicator in FC aircraft (MiG29, Su 27 and 33) and unfortunately I cannot find where (init_file?) the files for the indicator are located. Maybe someone knows the location of these files for these aircraft?

FC3 has a different coding structure. Most of the files are locked away in encrypted files. 

There's an "aircrafts/common" folder somewhere. It may be in there but I'm not at my computer to check. 

Edited December 23, 2023 by jonsky7

[Red_Pilot]

Thanks for the answer! I'll try to look at these folders again. In any case, fortunately, I have found that I can still see the indicator in the MFD-free area on the second monitor, so even if I don't find the control indicator file, I won't be left without the indicator at all

Edited December 24, 2023 by Red_Pilot

[MAXsenna]

According to a lot of other posts, sadly the controls Indicator for FC3 modules can't be edited.

Sent from my SM-A536B using Tapatalk

[Bigity]

Would there be any benefit in using the integrated graphics vs my Nvidia GPU to run the monitor I will export my MFDs to? 

[MadKreator]

On 12/26/2023 at 7:58 AM, Bigity said:

Would there be any benefit in using the integrated graphics vs my Nvidia GPU to run the monitor I will export my MFDs to? 

No not really, the exported displays are minimal in resolution and theres not much to them. It’s not trying to render millions of triangles and textures. Even the tpod is low enough resolution you probably wouldn’t notice any hit on performance. Maybe if you were doing a full 4K tpod.. but not in standard usage.