Multi-monitor set-up guide & help (unofficial)

[kingpinda]

nvidia?

sounds like the nvidia SLI problem.

 

nope.

 

Single ati 4870

[MadTommy]

I can confirm this all works in the final release.

[Bullant]

I wasn't sure if I should put this here or in a new thread.

 

Thanks to this awesome guide, I've managed to have this working beautifully with my MFCDs displayed on my second monitor, embedded in my HELIOS screen.

 

However, as most of you are aware, the menus for A10C are stretched across the multiple screens.

 

Is anyone aware of a setting that will restrict the menus to only displaying on the first monitor?

 

As I'm using a 1920x1200 stacked above a 1920x1080, the buttons on the mission end dialogs are ending up pushed onto the second monitor (as they sit just below half way) and therefore they are hidden by HELIOS and I have to close HELIOS every time I want to exit a mission. It also looks rubbish with the top half of the stretchy A10 displayed during the loading screens.

 

Any help greatly appreciated :)

[Loz]

Look above your post in this thread. Already been addressed.

[Bullant]

Look above your post in this thread. Already been addressed.

 

Thanks, I thought I'd scanned the whole thread, must have missed it :music_whistling:

[MadTommy]

Thanks, I thought I'd scanned the whole thread, must have missed it :music_whistling:

 

This is the best thread to discuss this.. its fairly complicated, but its all covered there.

 

EDIT: see 1st post, new fix for this added to the guide. Thanks to Kurky

Edited February 23, 2011 by MadTommy

[jtmedina]

Created a new monitor profile to show two MFDs on the main screen but when I go to options, the profile doesn't show up.

I saved it with notepad++

There is the config file.

 

_ = function(p) return p; end;

name = _('1CameraExample');

Description = 'Two MFDs on the first screen'

Viewports =

{

Center =

{

x = 0:

y = 0;

width = 1680;

height = 1050;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

 

LEFT_MFCD =

{

x = 10;

y = 1000;

width = 400;

height = 400;

}

 

RIGHT_MFCD =

{

x = 1100;

y = 1000;

width = 400;

height = 400;

}

 

UIMainView = Viewports.Center

 

 

[MadTommy]

Are you saving it as a *.lua in the \Eagle Dynamics\DCS A-10C\Config\MonitorSetup\ folder

 

Not that this would stop it showing up but these, in red, look wrong..

 

LEFT_MFCD =
{
[color="Red"]x = 10;
y = 1000;[/color]
width = 400;
height = 400;
}

RIGHT_MFCD =
{
[color="#ff0000"]x = 1100;
y = 1000;[/color]
width = 400;
height = 400;
}

Edited February 25, 2011 by MadTommy

[jtmedina]

Anyway what I really wanted is to show the MFDs on a floating window something like that...

http://img251.imageshack.us/f/floatingmfd.jpg

 

I think I was wrong it may not be even possible.

[MadTommy]

oh i get you.. not tried that. Nice idea tho.

 

Still looks wrong.. i'd try:

 

LEFT_MFCD =

{

x = 0;

y = 650;

width = 400;

height = 400;

}

 

RIGHT_MFCD =

{

x = 1280;

y = 650;

width = 400;

height = 400;

}

 

Did you get your file to show up in Options?

Edited February 25, 2011 by MadTommy

[jtmedina]

oh i get you.. not tried that. Nice idea tho.

 

Still looks wrong.. i'd try:

 

 

 

Did you get your file to show up in Options?

 

Nop, I tried notepad, wordpad and notepad++ I even manage to save it as UTF-8 without BOM but nothing.

[airdog]

Created a new monitor profile to show two MFDs on the main screen but when I go to options, the profile doesn't show up.

I saved it with notepad++

There is the config file.

 

_ = function(p) return p; end;

name = _('1CameraExample');

Description = 'Two MFDs on the first screen'

Viewports =

{

Center =

{

x = 0:

y = 0;

width = 1680;

height = 1050;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

 

LEFT_MFCD =

{

x = 10;

y = 1000;

width = 400;

height = 400;

}

 

RIGHT_MFCD =

{

x = 1100;

y = 1000;

width = 400;

height = 400;

}

 

UIMainView = Viewports.Center

 

Try this below...your's is all wrong

 

_ = function(p) return p; end;

name = _('1CameraExample');

Description = 'Two MFDs on the first screen'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 1680;

height = 1050;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

LEFT_MFCD =

{

x = 0;

y = 650;

width = 400;

height = 400;

}

RIGHT_MFCD =

{

x = 1280;

y = 650;

width = 400;

height = 400;

}

UIMainView = Viewports.Center

 

 

Ive attached the .lua file to this post. Put it in the x:/program files/eagle dynamics/DCS A10-C/Config/MonitorSetup folder.

1CameraExample.zip

Edited February 25, 2011 by airdog

[MadTommy]

Nop, I tried notepad, wordpad and notepad++ I even manage to save it as UTF-8 without BOM but nothing.

 

You need to save it as a .lua file.

 

And you should not use notepad or wordpad. They can corrupt lua code. I'd rewrite it using Notepad++ from scratch.

[jtmedina]

Try this below...your's is all wrong

.........

 

Ive attached the .lua file to this post. Put it in the x:/program files/eagle dynamics/DCS A10-C/Config/MonitorSetup folder.

 

Thanks, it worked!.

 

 

You need to save it as a .lua file.

 

And you should not use notepad or wordpad. They can corrupt lua code. I'd rewrite it using Notepad++ from scratch.

 

 

I did. It had to be the way the file is saved. No sure although.

 

Thank you both for your help :thumbup:

[Thermal]

Got a two monitor setup, a 24in and a 22in and one Nvidia GFX560

 

The 24in is my primary monitor and centre viewport. To the *left* of that is the 22in (and thats how it has to stay).

 

So, in the Nvidia control panel, I have the 22in on the left (#2) and the primary 24in on the right(#1).

 

This results is a desktop which is functional and works as expected.

 

But when configuring my two monitor setup is DCS-A10, the origin point (0,0) is the top left of the primary monitor in all orientations, and my primary is on the right.

 

Warning, bad ascii art follows:

|---------------+----------------|
|               |`               |
|               |                |
|               |                |
|---------------+----------------|

The ` denotes the (0,0) point.

 

So when trying to put a MFCD on the left monitor, I need to have the Center viewport set to (0,0) in the .lua file (for it to be on the primary monitor), and that means the MFCD needs a negative x value to put it on the left monitor.

 

But nothing shows up on the left monitor.

 

If I give the MFCD a slightly negative number, so it straddles the two monitors (i.e. x = -200 and width = 400) then I get half the MFCD on the primary monitor, and nothing on the left.

 

|---------------+----------------|   |---------------+----------------|
|               |                |   |               |                |
|               |#               |   |              #|#               |
|               |#               |   |              #|#               |
|---------------+----------------|   |---------------+----------------|
          As displayed                           As expected

So I know my positioning and co-ordinate system is seemingly sane.

 

Anyone got any ideas? Already swapped the physical ports that the monitors plug into the GPU.

 

Thanks!

Edited February 26, 2011 by Thermal
ascii art is tricky :)

[MadTommy]

No.. your logic is wrong. You cannot have nor do you need negative numbers.

 

Make the centre viewport x = 1680, y = 0. As a starting point, assuming your 22" is 1680x1050

 

EDIT: And have your MFCD at something like x=0, y=150 & x=840, y=150

At 840x840.

Edited February 26, 2011 by MadTommy

[Thermal]

No.. your logic is wrong.

 

No, its not.

 

I've proven that by the correct positioning of the MFCD in my crappy ascii art demonstration. I've also proven that the sim understands negative numbers, and when the centre viewport is set to (0,0) the centre viewport is displayed on the right hand display, where I expect it to.

 

The issue is that the MFCD cant be displayed on the left hand monitor if the right monitor is the primary display, when (0,0) is in its as explained position. That has nothing to do with logic, that is factually where (0,0) is.

 

If I make my left monitor the primary display, then I can get correct positioning of everything, because then (0,0) is move to top left of left monitor, where it should be. In that case however, all the start screens, mission editor and inflight notifications all end up on the left.

Edited February 27, 2011 by Thermal

[71st_Mastiff]

uh then don't put that monitor on that 0,0 because thats the center camera screen. duh just move your monitors around.

[Kuky]

Thermal, the game does not recognize negative coordiantes, if it did it would work for you.

 

Instead, the game sees total resolution of the monitors and 0,0 coordinate is top/left of the left monitor so you should adjust values with that in mind. There's plenty of posts on how people got their setups working so you should read through a bit.

[MadTommy]

No, its not..

 

Oh well i was trying to help. Good luck with those negative coordinates. ;)

Edited February 27, 2011 by MadTommy
typo

[Paradaz]

Thermal, the game does not recognize negative coordiantes, if it did it would work for you.

 

Instead, the game sees total resolution of the monitors and 0,0 coordinate is top/left of the left monitor so you should adjust values with that in mind. There's plenty of posts on how people got their setups working so you should read through a bit.

 

I'm having exactly the same problem as 'Thermal'. I've read all the comments in this whole thread but it seems the problems arise when people (like me) want the MFD's on the left hand monitor when the right hand monitor is designated as the first (or the primary) and is the same reason why people are wanting negative numbers for MFD's on the left screen.

 

Can anyone confirm that when having 2 monitors, the left hand monitors co-ordinates are definitely 0,0 even if it is the second monitor? I'm starting to believe that the 0,0 co-ordinates originate from the primary monitor therefore if the primary is on the right hand side, then we have a problem with co-ordinates of the left hand monitor if negatives cannot be used. If that sounds double-dutch I'll link an image.

 

-------------------

-------------------

Edit: I've been playing around with the settings, I believe the original guide needs slightly amending - I'm not saying that it's incorrect but it does need clearing up to avoid confusion.....

 

The 0,0 co-ordinates are not the left most screen as referenced, the 0,0 co'ordinates are taken from your primary screen. Therefore if you you had 3 monitors but the furthest most screen to the right was identified by windows as 'number 1' or the 'primary' then your 0,0 coordinate would be at the top left of your third screen. This creates a problem for the multi-monitor setups because you cannot create negative values to get the MFD's on the first two screens. The solution is to ensure (and mention in the first post) that your primary monitor must be the left hand screen. It is possible to set this up within windows and configure it so that your system/task bars appear on the third screen.

 

Hope this helps others with the same problem.

Edited February 27, 2011 by Paradaz
After additional testing

[MadTommy]

Hmm ok, thanks for the feedback.

 

Can anyone else confirm this?

Edited February 27, 2011 by MadTommy

[Paradaz]

Hmm ok, thanks for the feedback.

 

Can anyone else confirm this?

 

Anyone can see this behaviour by setting their right hand monitor as 'main monitor' within Windows display settings, starting the game/mission up and they will see that whatever the .lua has configured for the 0,0 co-ordinates will be displayed on that screen. It's not a big issue at all, it's just that anyone with their main screen on the right hand side needs to be aware of it and change their 'main monitor' setting before starting DCS A10 up. It only takes a minute and the PC doesn't need a reboot.

Edited February 27, 2011 by Paradaz

[Lucky]

This couldn't be any simpler. I was up and running my 2 monitor setup in about 10 minutes. Thanks to all involved.

[Thermal]

Hmm ok, thanks for the feedback.

 

Can anyone else confirm this?

 

Thats exactly what I said in my post, bad ascii art and all.