[REPORTED] F10 Map Is Not Confined to GUI Coordinates in 1.5.4 OB

[Tibet]

Wow just noticed the date on this original post... and this is still broken / was pushed out as part of a live build.

 

 

Not really sure what to say about that... :doh:

[SkateZilla]

I've submitted a new bug report w/ updated information from this thread.

 

Thanks for the information and monitor configs.

[klem]

I've submitted a new bug report w/ updated information from this thread.

 

Thanks for the information and monitor configs.

 

:thumbup:

[EricR]

:thumbup:

[Video]

My biggest problem with the temporary fix I posted earlier is that it moves the radio menus to the far right. This mod solves that problem. http://www.digitalcombatsimulator.com/en/files/2019016/ (all credit to Snacko)

Edited August 5, 2016 by Video

[EricR]

Thamks for link Video. I tried it and love it! Not only does it put text on the front screen. It also makes it a bit larger and easy to see.

[indiadamjones]

Ditto

 

I get the 75% load then switch to left monitor thing mention earlier.

 

1152x864 --- 1920x1080 --- 1152x864

 

GUI centering properly in everything except F10 view, which as the others stated:

 

shifted to the origin of the left monitor, but hover in the center monitor to click.

 

Still, nice to have the regular GUI's and ME working in center only.

 

Getting closer guys! Thanks as always.

dcs.log.old.txt

Edited August 11, 2016 by indiadamjones

[ofcross]

Same thing here!

[f4l0]

Any update on this?

[slicker55]

another 3-monitor user and two years on...

 

have been away for a while and wonder if there has there been any developments on this important issue?

 

it would be great if there was a way to confine the F10 map to the centre monitor only and have the ability to reposition things like the ATC menu and other dialogue text so they appear to the left and right of the centre monitor only

[klem]

another 3-monitor user and two years on...

 

have been away for a while and wonder if there has there been any developments on this important issue?

 

it would be great if there was a way to confine the F10 map to the centre monitor only and have the ability to reposition things like the ATC menu and other dialogue text so they appear to the left and right of the centre monitor only

 

 

This has been fixed for a while now. Try this ( I think its the defaullt 3Cameras.lua):-

 

 

_ = function(p) return p; end;

name = _('3 Screen by screen.width etc.');

Description = 'Configuration with 3 identical monitors each with its own camera'

Viewports =

{

Left =

{

x = 0;

y = 0;

width = screen.width / 3;

height = screen.height;

viewDx = -1;

viewDy = 0;

aspect = screen.aspect / 3;

},

 

Center =

{

x = screen.width / 3;

y = 0;

width = screen.width / 3;

height = screen.height;

viewDx = 0;

viewDy = 0;

aspect = screen.aspect / 3;

},

 

Right =

{

x = screen.width * 2 / 3;

y = 0;

width = screen.width / 3;

height = screen.height;

viewDx = 1;

viewDy = 0;

aspect = screen.aspect / 3;

}

}

 

 

UIMainView = Viewports.Center

 

 

 

 

 

if you are using one widescreen and the default 1Camera.lua doesn't do it add this to the bottom of the lua file:-

 

 

GUI =

{

x = screen.width / 3;

y = 0;

width = screen.width / 3;

height = screen.height;

}

 

UIMainView = GUI

 

 

[slicker55]

@klem,

I know we can always rely on some kind hearted person on this forum to spring to the rescue whenever needed but I just wanted to say a special thanks to you for providing a very swift reliable response to something which has been annoying the hell out of me for ages.

I am running the 3 monitors in an Eyefinity configuration so as you say, effectively one large monitor (5760 x 1920) but I omitted to mention that I also have a 1920 x 1080 touch screen for Helios and custom monitor lua's for various aircraft to capture the viewports correctly.

Therefore, when I tried changing the values to /3 (as per your second example) the GUI didn't take up pride of place on the centre monitor but I immediately realised that I needed to change these values to /4

Bingo! - well done mate... you have a very happy customer here!

[klem]

Glad it helped slicker55

 

 

I am running a T-shaped 3 over 1 but the Viewports method hits the FPS too hard so I am running 5760 x 2160 and don't need Helios etc.. However, because that puts the HUD/Gunsight right on the bezels between the top and bottom monitor I set y = -300 for the 'top' to be 300 px above the top monitor, i.e. raised up 300px including the gunsight which is then in the bottom half of the top monitor. Of course I lose 300px at the bottom of the lower screen but it still gives me enough instruments down there :)

 

 

Have a look at this:

 

 

 

 

_ = function(p) return p; end;

name = _('1 Screen 5760x2160 raised 300');

Description = 'One monitor configuration for 5170 x 2160 in-game resolution'

Viewports =

{

Center =

{

x = 0;

y = -300;

width = screen.width;

height = screen.height;

viewDx = 0;

viewDy = 0;

aspect = screen.aspect;

}

}

 

GUI =

{

x = 1920;

y = 0;

width = 1920;

height = 1080;

}

 

UIMainView = GUI

 

 

 

 

Cheers!

[slicker55]

@klem,

 

Bear with me, it's late (it's been a long day and it's just turned midnight here)

 

I am also mindful that we are starting to stray from the original topic

 

A few years ago, my monitor config was like yours when something interesting occurred to me which later sparked a lengthy debate.

 

Here goes...

 

It was argued that a T arrangement increases the workload of the GPU as the total draw area is significantly greater than when using a Linear arrangement.

 

The counter-argument was that any part of the T arrangement which was not actually producing any image could not impact on GPU performance.

 

However, another train of thought was the GPU still has to process those area's even though they are not physically there!

 

In the end, the only real way to come to a satisfactory conclusion was to carry out tests which, in my case, produced a higher FPS when using the Linear arrangement and therefore, I've stuck with that since.

 

Of course, (and at the risk of stating the obvious) references to Linear arrangement do not dictate the physical position of the fourth monitor which might still be positioned to form a T arrangement.

 

Food for thought...

 

The sums....

 

T arrangement:

 

5760 x 2160 = 12441600 pixels

 

Linear arrangement:

 

7680 x 1080 = 8294400 pixels

 

 

Result:

 

The Linear arrangement reduces the draw area by 4147200 pixels (approx 30% less)

[klem]

@klem,

.........................................

 

Food for thought...

 

The sums....

 

T arrangement:

 

5760 x 2160 = 12441600 pixels

 

Linear arrangement:

 

7680 x 1080 = 8294400 pixels

 

 

Result:

 

The Linear arrangement reduces the draw area by 4147200 pixels (approx 30% less)

 

 

Yes we have drifted OT so this is my last post on this point. I conducted tests with various configurations using exactly the same instant mission (F/A-18C 'Ready on Ramp'). You might like to see the FPS results in the attached zip file. 5260 x 2160 is more pixels but I am only generating one viewport. The more viewports you generate the harder the card has to work. Also, Helios can save you FPS if you are not using glass cockpits, just instrument data exports. For glass cockpits you have to have another viewport to fill the glass holes in the Helios panel.

 

 

 

Anyway, good luck and have fun.

Settings.zip

[slicker55]

interesting set of results.. anyway, like you say, back on track... loving the F10 map and comms menus centred - big improvement but it would be even better if the size and colour of the fonts could also be customised... hard to see the small white text at times