How-To: Set up a 4-screen, T-shaped display in DCS

GregP · February 17, 2013

I've gotten a bunch of questions about my 4-screen T-shaped SoftTH-enabled setup lately, so I figured that rather than continue to explain how I did it over PMs, I should finally just take the time to create a forum post about it. First of all, my setup looks like this:

I've got three 27" monitors running in Eyefinity on top, and a single 22" touchscreen on bottom, tied together with SoftTH. Rather than using something like Helios (an excellent utility, by the way) to export gauges and displays from DCS, I use the touchscreen to directly interact with the cockpit. I've created two videos showing how it works:

The basic process for setting this up consists of four steps:

1) Figuring out the render area sizes and positions,

2) Setting up your SofTH config file,

3) Setting up your DCS options.lua file

4) Setting up your DCS monitorsetup.lua file

Stepping through the process:

1) Figuring out the render area sizes and positions

The way SofTH works is that it allows you to specify a total display area that you want the game to render, and from this total render area, you can pick and choose which 'chunks' of it to send to each monitor. My 27" monitors run at 1920x1080, and with 90 pixels of vertical bezel compensation between them, that means my combined Eyefinity resolution is 5940x1080 (see attached picture). My 22" also runs 1920x1080, but because of the different monitor sizes, I need to make some adjustments in order to have the pictures line up correctly. Obviously, if I were to place the 22" directly below the center 27", and run both at 1920x1080, the view in DCS would not line up between them, i.e. the lower monitor's view would look compressed horizontally, relative to the upper monitor. I compensate for this in two ways: 1) By mounting the lower monitor several inches forward of the upper monitor, thus making the lower monitor appear wider (from the position of my seat) than it actually is, and 2) by 'stretching' a resolution lower than 1920x1080 onto the full 1920x1080 display area of the lower monitor -- this part will be explained later.

2) Setting up your SofTH config file

After downloading SoftTH and placing the d3d9.dll in your "DCS World\bin" folder, you need to create a config.SoftTHconfig file. I've pasted mine below:

 
[main]
renderResolution=5940x2180
nonlocalFormat=RGB16D
keepComposition=1
smoothing=1
debugD3D=0
zClear=1
vsync=0
tripleBuffer=0
screenshotFormat=bmp
dllPathD3D9=auto
dllPathDXGI=auto
dllPathD3D11=auto

[overrides]
forceResolution=0
antialiasing=0
anisotropic=0
processAffinity=1
FOVForceHorizontal=0
FOVForceVertical=0

[head_primary]
sourceRect=0,0,5940,1080
screenMode=5940x1080

[head_1]
devID=1
sourceRect=2082,1180,1776,1000
transportResolution=1920x1080
transportMethod=local
noSync=0

Under [main], I'm telling SofTH to force DCS to render a total area of 5940x2180. Why 2180? Because I have determined that, from the position of my viewpoint in the cockpit, the relative size of my 27" and 22" monitors is 1:0.925 (see attached picture). Thus, I can see that the 'chunk' of SofTH display area that I want to push to my lower monitor is, instead of 1920x1080, a rectangle whose size is 0.925 of 1920x1080 = 1776x1000. Additionally, I want 100 pixels of bezel compensation between the upper and lower monitors, and so all together, my combined vertical resolution is going to be 1080 (upper) + 100 (bezel) + 1000 (lower) = 2180. Thus, in my config.SoftTHconfig file, I set the res to 5940x2180.

The [head_primary] section sets the resolution of the 'primary' monitor, i.e. the upper monitors. Since I'm using Eyefinity to tie them together, I set this to 5940x1080.

The [head_1] section sets the lower monitor's resolution. The [sourceRect] line tells SoftTH where exactly to pull a 'chunk' from and how big it should be; doing a little math by consulting the picture of my monitors, I can see that I want to pull the chunk whose upper left corner's X coordinate is 1920 + (1920-1776)/2 + 90 bezel = 2082. This chunk's upper left corner Y coordinate is similarly determined to be 1080 + 100 bezel = 1180. Those are the first two numbers on the [sourceRect] line; the second two tell it how big an area to pull. As explained above, I want this area to be 1776x1000.

The next line in the [head_1] section lets you set what resolution at which to display your chosen chunk. If I used 1776x1000, this would force my lower monitor to run at the (maybe impossible) resolution of 1776x1000. So instead, I ask SoftTH to 'upscale' that res to the one I actually want to run the monitor at, which is 1920x1080.

That's it for the config.SoftTHconfig file. Place this file in your "DCS World\bin\" folder, and on to Step 3.

3) Setting up your DCS options.lua file

This one is simple. The only changes you'll make are to the [graphics] section, and I've pasted mine in below:

["graphics"] = 
   {
       ["multiMonitorSetup"] = "1camera+centeredgui",
       ["color"] = "32",
       ["preloadRadius"] = 150000,
       ["heatBlr"] = 1,
       ["scenes"] = "high",
       ["water"] = 0,
       ["fullScreen"] = true,
       ["disableAero"] = false,
       ["visibRange"] = "High",
       ["treesVisibility"] = 6000,
       ["aspect"] = 2.7247,
       ["haze"] = 1,
       ["HDR"] = 0,
       ["TranspSSAA"] = true,
       ["textures"] = 2,
       ["cockpitShadows"] = true,
       ["shadows"] = 1,
       ["effects"] = 3,
       ["MSAA"] = 2,
       ["height"] = 2180,
       ["sync"] = true,
       ["shadowTree"] = false,
       ["civTraffic"] = "low",
       ["width"] = 5940,
       ["clutterMaxDistance"] = 0,
       ["lights"] = 2,

The important lines here are ["multimonitorsetup"], ["aspect"] (divide horizontal by vertical resolution, in this case 5940/2180 = 2.7247), ["width"] and ["height"].

4) Setting up your DCS monitorsetup.lua file

Another easy step. I've attached mine below, named "1Camera+CenteredGUI.lua":

_  = function(p) return p; end;
name = _('1Camera+CenteredGUI');
Description = 'One monitor configuration'
Viewports =
{
    Center =
    {
         x = 0;
         y = 0;
         width = screen.width;
         height = screen.height;
         viewDx = 0;
         viewDy = 0;
         aspect = screen.aspect;
    }
}

Gui =
{
	x = 2010;
	y = 0;
	width = 1920;
	height = 1080;
}

UIMainView = Gui

This centers the GUI on your middle upper screen. The X coordinate is found from 1920 + 90 bezel = 2010. Drop this file into your "DCS World\Config\MonitorSetup" folder.

And that's it! You should now have a T-shaped, 4-screen setup working in DCS. Depending on your lower monitor's position and size relative to your upper monitors, you may need to change some of the math here, but the general outline of the process should remain the same.

tromac2010 · February 18, 2013

Thank you Greg for taking the time to put this up for us all!

Cowboy10uk · March 24, 2013

Hi Greg, I'm currently trying to run this same setup. May I ask your graphic settings and if you get any micro stutters. I normally run Helios on high settings with no problems, but after switching to this screen setup, I've reduced all settings to medium yet I am suffering from a large amount of micro stutters.

Just trying to find a way to get rid of them.

Cowboy10uk

Cali · March 24, 2013

Awesome thread, it won't let me rep you.

Loz · March 24, 2013

Nice one Greg.

I thought that I would revisit SofTH now that I have bought the update to BS2 and the P51D, maybe a setup that would accommodate all 3 might be in order.

Your guide saves me a lot of head scratching.

Rep Inbound. :)

Cowboy10uk · March 24, 2013

Nice one Greg.
I thought that I would revisit SofTH now that I have bought the update to BS2 and the P51D, maybe a setup that would accommodate all 3 might be in order.
Your guide saves me a lot of head scratching.
Rep Inbound. :)

Now Loz, if you can get Helios profiles for all 3, that would be something. Your A10 one is second to none. Sorry to everyone else, but no other profile comes close. :).

Don't get me wrong though, I love this setup as well. It looks great when running.

Cowboy10uk

Loz · March 24, 2013

Now Loz, if you can get Helios profiles for all 3, that would be something.
Cowboy10uk

Thanks Cowboy, yes I tried my hand at the KA-50 profile but it's very complex with all the panels that are in the cockpit and the graphics in game are not the same quality as A10C. But of course there is nothing for the Mustang (in Helios that is) Hence I am giving the SofTH another look.

GregP · March 24, 2013

May I ask your graphic settings and if you get any micro stutters. I normally run Helios on high settings with no problems, but after switching to this screen setup, I've reduced all settings to medium yet I am suffering from a large amount of micro stutters.

With my current setup I haven't noticed any microstutters, although I had seen them in the past with earlier versions of DCS. But there's no question that running this massive display area can bring just about any single video card to its knees (can't WAIT for the DCS series to finally support SLI/CF some day). I'm kind of surprised that you're seeing stutters though, because your 680 has 4GB of VRAM whereas my 7970's only got 3GB.

I've attached a screenshot of my settings below; how do your settings compare to mine? I couldn't tell from your post -- are you still running Helios, or have instead used my process completely?

GregP · March 24, 2013

Now Loz, if you can get Helios profiles for all 3, that would be something. Your A10 one is second to none. Sorry to everyone else, but no other profile comes close. :).

Agreed on that point. Back when I was messing around with Helios, I absolutely loved Loz's profile, very cool stuff. I'd like to think that I'm somehow building on that with my setup. :)

Cowboy10uk · March 24, 2013

With my current setup I haven't noticed any microstutters, although I had seen them in the past with earlier versions of DCS. But there's no question that running this massive display area can bring just about any single video card to its knees (can't WAIT for the DCS series to finally support SLI/CF some day). I'm kind of surprised that you're seeing stutters though, because your 680 has 4GB of VRAM whereas my 7970's only got 3GB.

I've attached a screenshot of my settings below; how do your settings compare to mine? I couldn't tell from your post -- are you still running Helios, or have instead used my process completely?

Hi gregP at the moment, I'm currently running all graphics on medium, no shadows whatsoever and bushs, trees and preload on full left. So very low compaired to yours. I do still use Helios and when I do I have all settings on high with no issues.

It's only when flying the P51 do I use this method. I've just updated to the latest drivers I can find 314.07 to see if this makes a difference. My drivers were a little out of date. :doh:

I'm sure it's a setting somewhere I'm not doing, do you have any settings in nvidia inspector, think mine are default at mo.

Cowboy10uk

cichlidfan · March 24, 2013

Nice work, good post. :thumbup:

Cowboy10uk · March 24, 2013

After updating graphics drivers and messing around with nvidia inspector, looks like those stutters are gone. Back up to running on high with min slow down. Thanks for your time GregP

Cowboy10uk

GregP · March 24, 2013

If you're trying to exactly replicate my setup, and have your cockpit directly clickable via the lower touchscreen, then you don't have any need for Helios anymore. And I'm pretty sure that adding Helios on top of my setup would significantly lower your FPS. So, if you haven't tried it already, try not using Helios and see what that does to your performance.

Cowboy10uk · March 24, 2013

Hi GregP, sorry what I mean, is when I fly Blackshark or A10, I switch to my Helios screen lua, which gives me my 3 screens and the Helios and outputs showing on touchscreen.

When I fly P51 and hopefully soon the Huey, I switch my screen to 4 screen LUA. I don't have both running at same time. I appreciate this I could run all aircraft from this one setup, but I do prefere the ease of having Helios to access my mfds and buttons. Find it a little easier when the work load increases while on missions.

Now I've managed to almost get rid of the stutters, I must say this setup is stunning with the mustang.

Cowboy10uk

Cowboy10uk · May 20, 2013

Ok,this was working great with P51, however now I'm trying to use it with the Huey, since it has more glass you can see a lot more of the ground.

My bottom monitor, while it lines up nicely with the cockpit on the main 3 monitors, the ground appears to zoom in and move out of line, when it passes onto the 4 th monitor, this is rather disconcerting and is causing me to have headaches when flying with this setup.

Is there anyway I can get the output on lower monitor to match the zoom on the top.

My 3 main monitors are 23" at 1920 x 1080, while my bottom touchscreen is 24" 1920 x 1080. The bottom monitor is also pull forward of the other monitors by about a foot.

I hope this makes sense.

Cowboy10uk

Dachs · July 14, 2013

Thanks a lot GregP!

I've never dabbled with SoftTh before, but thanks to you I got it up and running in no time. Well, I had to fiddle with the ratios of the 4th screen for a while, but all is good now.

Can I ask, how have you setup your touchscreen with regards to rightclicks?

@ Cowboy10uk, maybe changing the ratio (and thereby the resolution) for your 4th screen might help? I had to use 0.73 instead of GregP's 0.925 in order to get the size right.

I guess if the cockpit on your main has the same size as on the 4th, it must be something else.. The bezel compensation between main and 4th perhaps?

PeterP · July 14, 2013

Can I ask, how have you setup your touchscreen with regards to rightclicks?
ps?

I use a very similar set-up and my touch-screen works like this:

Every touch that is shorter as 0.3 second or is moving will be recognized as a Left-clik.

But when I hold a single point (within 64square pixels) longer as 0.3 sec - it will executed as as a Right-click.

When you follow the above rules you will be able to 'drag' dials and be able to do a right click whenever you want.

Thick8 · July 14, 2013

Does this mean that your video card is actually rendering the full 5940x2260 rectangle?

John

GregP · July 15, 2013

Dachs, I've got a similar setup to PeterP: if press lasts 0.X second or less, it's a left-click; if >0.X second, it's a right-click.

Thick8, yes, I believe that is correct, my video card is rendering the entire rectangle, which sounds like a lot but I'm still able to maintain FPS in the 20-50 range even with most graphics options still turned on.

megs8888 · September 3, 2013

what touchscreen is it where are they available pls.

myoun04q · September 7, 2013

indieanna.

Seattle-based Tenzing will install its network on Virgin and Cathay Pacific Airways this year,indieanna.com/shipment.html, as well as a trial service with Singapore Airlines

GregP · September 7, 2013

what touchscreen is it where are they available pls.

The touchscreen is an Acer T272HL, and is available online at Amazon, Newegg, etc.

ThePutzer · September 9, 2013

SLI/Eyefinity required?

Is it necessary,,SLI/Eyefinity,, to set up the, options.lua files,["multiMonitorSetup"] = "1camera+centeredgui. and monitor setup.lua file as instructed?? "1Camera+CenteredGUI.lua". I am runnin 2 gtx 680's with 3 27inch and 1, 23in touchscreen.. Problem they are not identical models,they work just fine with nvidia surround enabled,, and adding the 4thmonitor disables nvidia surround,. So I buy 1 more monitor to match, so surround works, or just enable all 4 monitors thru windows in proper orientation and the use SoftTH. And modify files as directed above????,,I saw you were using EyeFinity, GregP...

Cowboy10uk, are you you using nvidia surround, to set top3 monitors also??

Thanks guys, ThePutzer

AhSoul · September 10, 2013

Sign In

How-To: Set up a 4-screen, T-shaped display in DCS

Recommended Posts

GregP

tromac2010

Cowboy10uk

Cali

Loz

Cowboy10uk

Loz

GregP

GregP

Cowboy10uk

cichlidfan

Cowboy10uk

GregP

Cowboy10uk

Cowboy10uk

Dachs

PeterP

Thick8

GregP

megs8888

myoun04q

GregP

ThePutzer

AhSoul

ThePutzer

Recently Browsing 0 members