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

[jonsky7]

39 minutes ago, Red_Pilot said:

Does anyone know if there is a "MFCD" for MiG 21? Can we see radar screen in the "MPCD" area? 

 

Yes, it should export to either "RP22" or "RIGHT_MFCD"

 

So if you make an config entry called RP22, it will go there, otherwise you can have it export to RIGHT_MFCD.

Looks a bit dark though, I don't know how to turn it on, just downloaded the trial version to check it.

[Red_Pilot]

Yes, thank you so much, RIGHT_MFCD is working! Lol I couldn't see the radar at first because it turned out to be much darker on my monitor than the red field on the radar screen in the game, so it seemed to me that the image just wasn't exported until I turned on the RADAR BEAM mode

Edited February 25, 2024 by Red_Pilot

[Red_Pilot]

It's a pity that this doesn't work for MiG 19

[NoLegalMoves]

So not to appear ungrateful or anything BUT…

I can’t help myself, being a perfectionnist…

My triple 4k +3 MFDs lua file works great except for distortion on the side screens (left screen appears leaning left, right screen leaning right).. On the ground or leveled flights it looks like the nose is pointing up if i look at the sides.

Is there a way to correct for that? I tried to play with viewdx viewdy, but doesn’t not seem it’s the right lever..

Also I tried to place all my TVs into a single giant viewport (center) but when I do that i keep losing the right screen (which is what i was struggling with initially). Looks like this might be a DCS bug?

On a different topic, my stick suddently stopped working..  Hugh! 

 

 

[jonsky7]

5 hours ago, NoLegalMoves said:

So not to appear ungrateful or anything BUT…

I can’t help myself, being a perfectionnist…

My triple 4k +3 MFDs lua file works great except for distortion on the side screens (left screen appears leaning left, right screen leaning right).. On the ground or leveled flights it looks like the nose is pointing up if i look at the sides.

Is there a way to correct for that? I tried to play with viewdx viewdy, but doesn’t not seem it’s the right lever..

Also I tried to place all my TVs into a single giant viewport (center) but when I do that i keep losing the right screen (which is what i was struggling with initially). Looks like this might be a DCS bug?

On a different topic, my stick suddently stopped working..  Hugh! 

 

 

I haven't tried a setup like yours so in all honesty, I just don't know. 

I did a quick search to see if there was a missing "rotate dx" or something but nothing looked particularly obvious.

Only other thing I could suggest is altering your "head position". A simple test could be achieved by using the seat height adjustment in the jet.

If it looks like that would improve the situation there is a way to "make yourself taller/shorter and save that as the default view.

Also, The standard default view set by DCS is slightly downward looking, you can check this by zooming all the way in, you will see that it zooms into the instrument panel, and not through the centre of the HUD. For single screen this is understandable as it will include some instruments. So changing the default to be straight ahead might give you the result you're after.

I think you have to disable track ir, if used, press numpad 5 to select centre view, then use the numpad keys to alter view, and then RCTRL+NUMPAD 0 saves the view.

 

As for your stick not working. DCS uses specific hardware IDs to assign buttons, and if you unplug usb cables and plug them back in, the hardware ID can change as thus lose the bindings etc.

You can load them back in through the controls options screen. Select the column for your stick, then press the load profile button. Navigate to aircraft folder in your saved games, config, input, and load the profile for the correct device.

 

 

[NoLegalMoves]

Thanks, i’ll give it a go this weekend (about pilot seat height). The stick, i m afraid is a more, well sticky issue.. The buttons won’t even show as depressed in the windows controller settings whereas I have the main axis working.. I wrote a ticket to vkb but bizarrely they’ve ignored it so far (3 days). I think I’ll take it appart this weekend and clean the contacts as I’ve seen it suggested elsewhere. There’s always something with this many pieces of hardware, i guess.

 

 

[jonsky7]

4 hours ago, NoLegalMoves said:

Thanks, i’ll give it a go this weekend (about pilot seat height). The stick, i m afraid is a more, well sticky issue.. The buttons won’t even show as depressed in the windows controller settings whereas I have the main axis working.. I wrote a ticket to vkb but bizarrely they’ve ignored it so far (3 days). I think I’ll take it appart this weekend and clean the contacts as I’ve seen it suggested elsewhere. There’s always something with this many pieces of hardware, i guess.

 

 

VKB, you didn't say which one so if it's a gunfighter, it could be it has just lost its calibration settings which could be fixed through their software.

It could be the joystick to base contacts, or just the clamp has become loose.

Or the wire inside that goes from the board to the base connection has come loose at the board. The wires used are very thin and I've had to replace 2 of mine. Though I think it was the x axis ones on mine. 

[karavak]

Resolved my issue using Helios.  Not sure what I did wrong but it works now!  Thanks for the guide!

Edited March 1, 2024 by karavak

[lone82]

SA342M TV MFCD Name? ......"LEFT_MFCD" doesnt work

[IanC58]

2 minutes ago, lone82 said:

SA342M TV MFCD Name? ......"LEFT_MFCD" doesnt work

SA342_TV =
{
    x = 3050;
    y = 780;
    width = 800;
    height = 635;
}

obviously my numer settings and on 1 screen but TV works

Edited April 23, 2024 by IanC58

[lone82]

Didn't work for me. I take it I need to add some lines to the init.lua? WIll probably fail the IC.

 

Edited April 23, 2024 by lone82

[jonsky7]

2 hours ago, lone82 said:

Didn't work for me. I take it I need to add some lines to the init.lua? WIll probably fail the IC.

 

 

The TV screen is not exportable by default

Mod file here _> Viviane exportt.zip  export name SA342_TV

Will break pure scripts however, the choice is yours.

Edited April 23, 2024 by jonsky7

[DonRumsey]

This has ben the most detailed and explanatory "HOW TO" on this topic I've found.  Much appreciated!

I just added two 27" to the right and left of my main monitor (32") for more of a "wrap-around" view.  Would I use negative x-values for the left monitor?

I'm slowly getting this all together.

Many thanks!

Don

Doc |WA-509|

 

[jonsky7]

35 minutes ago, DonRumsey said:

This has ben the most detailed and explanatory "HOW TO" on this topic I've found.  Much appreciated!

I just added two 27" to the right and left of my main monitor (32") for more of a "wrap-around" view.  Would I use negative x-values for the left monitor?

I'm slowly getting this all together.

Many thanks!

Don

Doc |WA-509|

 

I have never personally been able to get anything on a screen that is left of my main monitor.

DCS will simply not go there for me, I have tried with multiple graphics cards over the years, albeit all Nvidia cards.

I just set my Main Monitor as the left most.

This guide is really for the exporting of MFCDs, if that is what you are trying to do then cool.

If you want a 3 display cockpit view, you can just try the 3 screens setting that already exists in the DCS settings menu.

 

[Darkdiz]

Anyone figure out the names for the F4 radar and RWR?

Trying to export them to my Cougar monitors

UPDATE: Got the names and viewports sorted, but the DSCG exports as white, completely washed out. Any ideas?

Still tweaking the exact position of the export

 

Edited May 26, 2024 by Darkdiz

[HawaiianRyan]

3 hours ago, Darkdiz said:

Anyone figure out the names for the F4 radar and RWR?

Trying to export them to my Cougar monitors

UPDATE: Got the names and viewports sorted, but the DSCG exports as white, completely washed out. Any ideas?

Still tweaking the exact position of the export

 

 

Why don't you share the names for those who have the same question?

[Darkdiz]

I found the answer here:

You can actually call them what you like, mine are F4_ALR46 and F4_DSCG, as long as it is the same in your monitor setup lua

[jonsky7]

Doesn't look like any of the F-4's displays are exportable by default at the moment.

 

[Darkdiz]

On 5/28/2024 at 12:41 AM, jonsky7 said:

Doesn't look like any of the F-4's displays are exportable by default at the moment.

 

The RHAW exports, so does the DSCG, but there are issues with the DSCG. For whatever reason, when I initially got the DSCG to display, I got what you would expect, the grid and cursor. Then, all of a sudden, I got the entire DSCG display overlaid onto my entire DCS screenspace, and try as I might, could not get that to disappear. I never successfully got the TV display ot work, but TBH I didn't try all that hard, as I was still working on the DSCG.

For the RHAW, I editied the maingame/mods/aircraft/f4e/cockpit/scripts/RHAW/indicator init_bake.lue by adding the following:

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

Then, in my monitor config file, I added the following:

--///////////////////////
--F-4
--///////////////////////

F4_ALR46 = -- MFD 2
{
     x = 1205;
     y = 600;
     width = 600;
     height = 600;
     aspect = 1--600/600
}

F4_DSCG = -- MFD 1
{
     x = 90;
     y = 600;
     width = 595;
     height = 595;
     aspect = 1--600/600
}

Obviously, the monitor config file will wildly vary from person to person. The RHAW dial grid also will not export, its just the data (I think similar to the F-14 ALR).

The F4_DSCG line will display at those coords, however, I get the full radar grid over my entire screenspace. Its also a bit blurry, I suspect the large grid that is overlaid has something to do with that

The file I edited was maingame/mods/aircraft/f4e/cockpit/scripts/DSCG/indicator/init.lua by adding the following (for the DSCG):

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
update_screenspace_displacement(1, true, 0)
try_find_assigned_viewport("F4_DSCG")

The second line in the above I am unsure of, I got it from another post on the forum, linked as few posts above. I also can't directly recall if I added the lines to the DSCG_Pilot and DSCG_WSO/init_bake.lua file (I'm about 75% sure I did, but note in the WSO file, the ViewportHandling command is already there, but without the try_find_assigned_viewport command).

Since I couldn't get it to work, I double-dashed the lines for now, so they are ignored in my setup.

I'm kind of "other tasked" right now, not sure how much time I can dedicate to this, fixing it as either going to be a HB thing, or its something stupid, like a syntax error or a setting. Please feel free to edit these lines and update the thread with successes or failures as they occur.

Hope folks aren't as confused as I am

[DandareBR]

Nevermind. I already solved the issue

 

 

Edited June 13, 2024 by DandareBR
adding more pictures

[CallsignLord]

Thanks

[peeter]

PeetMultiAircraft.lua

Hello there !

For some reasons the PeetMultiAircraft.lua config files does not show up in the DCS options...

It's placed in SavedGames like the PeetSaveGames.lua wich is working fine.

Any ideas ?

 

Thanks !

null

PeetSaveGames.lua

[jonsky7]

23 hours ago, peeter said:

PeetMultiAircraft.lua 1.05 kB · 0 downloads

Hello there !

For some reasons the PeetMultiAircraft.lua config files does not show up in the DCS options...

It's placed in SavedGames like the PeetSaveGames.lua wich is working fine.

Any ideas ?

 

Thanks !

null

PeetSaveGames.lua 473 B · 0 downloads

Only thing I could see wrong is that only the first aircraft should be listed as 'if'

if unit_type == "AH-64D_BLK_II" then

other specified aircraft are 'elseif', ie:

elseif unit_type == "SA342L" then

You had them down as just 'if'

give this a try

Quote

_  = function(p) return p; end;
name = _('PeetMultiAircraft');
Description = 'exports by aircraft type'
Viewports =
{
    Center =
    {
        x = 0;
        y = 0;
        width = 2560;
        height = 1440;
        aspect = 1.7777777777777777;
    }
}

--/////////////////////////////////////
--AH-64D_BLK_II
--/////////////////////////////////////

function reconfigure_for_unit(unit_type) 

if unit_type == "AH-64D_BLK_II" then

LEFT_MFCD =
{
    x = 2570;
    y = 710;
    width = 748;
    height = 708;
}

--/////////////////////////////////////
--SA342
--/////////////////////////////////////

elseif unit_type == "SA342L" then

LEFT_MFCD =
{
    x = 2570;
    y = 710;
    width = 748;
    height = 708;
}

elseif unit_type == "SA342M" then

LEFT_MFCD =
{
    x = 2570;
    y = 710;
    width = 748;
    height = 708;
}

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

else

RIGHT_MFCD =
{
    x = 2570;
    y = 710;
    width = 748;
    height = 708;
}

end
end

UIMainView = Viewports.Center
GU_MAIN_VIEWPORT = Viewports.Center

 

Edited June 24, 2024 by jonsky7

[peeter]

2 hours ago, jonsky7 said:

Only thing I could see wrong is that only the first aircraft should be listed as 'if'

if unit_type == "AH-64D_BLK_II" then

other specified aircraft are 'elseif', ie:

elseif unit_type == "SA342L" then

You had them down as just 'if'

give this a try

 

 

Well spotted, now it's working !

Thanks for the help Jonsky !

[jonsky7]

12 minutes ago, peeter said:

Well spotted, now it's working !

Thanks for the help Jonsky !

You're welcome, glad to have helped.