Next Issue,

So I have this outstanding Monitor Configuration file that exports most of the various aircraft MFDs to my two Lilliput 8inch LCD monitors. I had set up for everything from the two for the A-10C to the one for the Mig-21.

I tired copying and pasting it to the Monitor Configuration folder and it either doesnt recognize the LUA file in the drop down list or it does but then it still won't work. Has anyone else tinkered with the monitor config files yet? Right now my expensive two-MFD set up is essentially useless.

Help?!

I have actually. I will post my Monitor Setup file here.

_ = function(p) return p; end;
name = _('Camera + LMFCD(on right side)');
Description = 'Left MFCD on the right and camera on the center'
size = 328+371;
Viewports =
{
Center =
{
x = 0;
y = 0;
width = (screen.width / 2) + 120;
height = screen.height;
viewDx = 0;
viewDy = 0;
aspect = screen.aspect;
}
}

LEFT_MFCD =
{
x = (screen.width / 2) + 210;
y = 90;
width = 626;
height = 626;
}
RIGHT_MFCD =
{
x = screen.width - 626 - 90;
y = 90;
width = 626;
height = 626;
}


UIMainView = Viewports.Center


This gives me a full cockpit on left monitor (1920 x 1080) and 2 MFD on Right Monitor (1680 x 1050)

Set resolution in game to 3600 x 1080 and aspect to 16:10

Hope this helps. If not I may be able to answer any questions you have. I also use HELIOS to make my right monitor much 'prettier' with some instruments on it, but that is probably a topic for another thread

filename = Camera+LMFCD(on right side).lua and I select that as my monitor in game.

Mustang,

Good stuff man. Thanks for taking time out.

Did you have to create a new LUA file or where you able to import a previous LUA from your main DCS directory?

If you mean for the monitor .config file. I took one that was in the following directory

C:\DCS Open Beta 1.5\Config\MonitorSetup

and modified it to what I needed.

Or are you referring to the export.lua for Helios. IF so, I took the latest export.lua from the Helios site and that worked fine.

Have you found that you can only do one aircraft configuration per LUA file?

In the previous version, I had one Monitor Config LUA file that covered every aircraft I was concerned with.

That does not appear to work in 1.5.

Well, crap.

Despite several hours of trouble shooting and some forum searching it appears the current Monitor Configuration for DCS 1.5 is fairly dorked up.

I will continue to play with the new graphics engine and the awesome new frame rates but it does suck having my current home-cockpit rendered INOPERATIVE by the current beta. However, I fully understand this is just part of the process and everything still works great on the most recent 1.2 build of DCS.

I have a single 27 inch monitor with two Lilliput 8inch USB LCDs affixed to my Thrustmaster MFDs. If anyone has luck with a similar configuration please, please let me know. Even if I have to make one LUA for each aircraft.

Thanks,

Stepehen

Right now, that is how it appears to work. I never did any of this in previous versions, so I just assumed that is how it always worked.

I have a lua file that uses the reconfigure_for_unit() function and covers 4 separate aircraft (standard, A-10C, Ka-50, Su-25T) that works fine in 1.5, which is to say that the MFDs are placed on the monitors properly when the correct aircraft is selected. This means that I get MFD sizes for FC3 and A-10C, elongated (4:3) SHKVAL for the Ka-50 and Su-25T, and the portrait ABRIS in the Ka-50.

The problem I'm running into is that with the exception of the MFDs (which work properly, and for purposes of the lua include SHKVAL and ABRIS), none of the gauges clear the old data before redrawing. This means that the A-10C RWR looks like alphabet soup after a few minutes, and don't even try to read the CDU display! I use the Instrument Export mod for A-10C and Ka-50, and I've confirmed that the modded files are still valid for 1.5.

Here is my current config which allows me to have diff configs per aircraft. Right now the KA-50 and A10C are the same config, I just did this for testing, but it does work.

_ = function(p) return p; end;
name = _('Camera + LMFCD(on right side)');
Description = 'Left MFCD on the right and camera on the center'
size = 566;

function default_setup()

Viewports =
{
Center =
{
x = 0;
y = 0;
width = (screen.width / 2) + 120;
height = screen.height;
viewDx = 0;
viewDy = 0;
aspect = screen.aspect;
}
}
end

default_setup();

UIMainView = Viewports.Center

function reconfigure_for_unit(unit_type)
if unit_type == 'A-10C' then

Viewports =
{
Center =
{
x = 0;
y = 0;
width = (screen.width / 2) + 120;
height = screen.height;
viewDx = 0;
viewDy = 0;
aspect = screen.aspect;
}

}

LEFT_MFCD =
{
x = (screen.width / 2) + 200;
y = 80;
width = size;
height = size;
}
RIGHT_MFCD =
{
x = screen.width - size - 80;
y = 80;
width = size;
height = size;
}

elseif
unit_type =='ka-50' then

Viewports =
{
Center =
{
x = 0;
y = 0;
width = (screen.width / 2) + 120;
height = screen.height;
viewDx = 0;
viewDy = 0;
aspect = screen.aspect;
}
}

LEFT_MFCD =
{
x = (screen.width / 2) + 200;
y = 80;
width = size;
height = size;
}
RIGHT_MFCD =
{
x = screen.width - size - 80;
y = 80;
width = size;
height = size;
}

else
default_setup()
end
end

Phew!

Alright, working with all your good advice and a little trial and error, last night I got LUA files done for the SU-25T, KA-50, and A-10C. So essentially, I have been able to successfully export MFDs, Shkval, and ARBRIS.

However, I have not been able to export any of the radars from the Mig-29, SU-27, or the F-15C and MIG-21. Its just a corrupted blank space. Any one else experiencing the same?

Progress.

Stephen

The FC3 MFD exports are still buggy (I haven't tried the MiG-21 yet). That's on ED's end and as long as the MFD is in the right position, you've done everything you can do.

Thanks HomeFries. Sounds like I've taken it as far as I can for now. My mind can rest now and in the mean time I'll go fly the SU-25T or A-10C. Twist my arm.

Steve

I have only exported the same as you. Though I am researching the other stuff as well, I think we have to edit some of the .lua files within the aircraft dirs and I hate to do that because when the aircraft gets update, we are back to square one.