Crashing with custom res/dual screen

[doveman]

If I launch BS2 with 1920x1200, which is the res of my main monitor, it loads OK, even if I have my secondary monitor (1920x1080) enabled in Windows as well.

 

However, if I try and launch with a custom res of 3840x1200 or 3840x1080 it says "DCS has stopped working" when I try and launch BS2 and throws me back to the menu. If I try with this res and a custom MonitorSetup (as below) it does the same thing, so at the moment I can only run it on a single display. I did have it running with Helios on the secondary monitor OK before I had to reinstall Win7 though, so I know it should work.

 

_ = function(p) return p; end;
name = _('Helios');
Description = 'Two monitor configuration';
Viewports =
{
Center =
{
x = 0;
y = 0;
width = 1920;
height = 1200;
viewDx = 0;
viewDy = 0;
aspect = 1.6;
}
}

LEFT_MFCD =
{
x = 2676;
y = 73;
width = 465;
height = 343;
}

RIGHT_MFCD =
{
x = 3230;
y = 384;
width = 370;
height = 485;
}

Gui =
{
x = 460;
y = 0;
width = 1024;
height = screen.height;
}

UIMainView = Gui

 

_ = function(p) return p; end;
name = _('Dual Screen-MFCDs on Right');
Description = 'Two monitor configuration';
Viewports =
{
Center =
{
x = 0;
y = 0;
width = 1920;
height = 1200;
viewDx = 0;
viewDy = 0;
aspect = 1.6;
}
}

LEFT_MFCD =
{
x = 1920;
y = 60;
width = 960;
height = 960;
}

RIGHT_MFCD =
{
x = 2880;
y = 60;
width = 960;
height = 960;
}

Gui =
{
x = 460;
y = 0;
width = 1024;
height = screen.height;
}

UIMainView = Gui

 

I'm currently running with an unmodified OptionsData.lua so it looks like this

 

    resolution = {
       __value__ = '1024x768',
       control = 'combo',
       values =  {},
       binder = 'bindResolutionCombo',
       },

 

it shows the 3840x1200 res in the list but I guess it's just stored that in the user options.lua from where I typed it in manually last time I ran it.

[MTFDarkEagle]

Try disabling fullscreen. If you want to keep using fullscreen: use softth.

[doveman]

Try disabling fullscreen. If you want to keep using fullscreen: use softth.

 

Heh, thanks. That just occurred to me to try and it worked. These things never occur to me until after I've spent three days getting nowhere and writing a long forum post ;)

 

I should have known that anyway as I learnt about SoftTH a few weeks ago but I've had to reinstall Win7 since then and have been running unmodified until I was sure everything was OK and I just forgot everything I'd learnt recently :doh:

[doveman]

I'm still having a few problems.

 

With Helios, I can't see the Shvkal. I've attached pictures of with and without Helios so you can see the viewports are being exported.

 

 

 

The Shvkal does have a background layer in Helios called "cache Shklval" (SHKVAL_e.png), the same as the ABRIS does (ABRIS_e.png) but for some reason the Shkval one seems to "stay-on-top" and therefore block the Shkval viewport.

 

Also, when exiting a mission the black background of the ABRIS disappears, leaving my desktop picture poking through. I guess I could either set the desktop on my 2nd monitor to solid black or enjoy a bit of the picture framed in the Abris window ;)

 

I also find that the Abris on/off switch doesn't always sync with DCS, so that if I have it on and then exit the mission and start another one, the switch stays up and when I turn on the Abris in the cockpit (or Auto-Start does it) the Helios Abris does come on but the switch doesn't move because it's already up. Other times I've found that the Helios Abris isn't displaying, despite the cockpit one being on, until I flick the Helios switch.

 

I did have to manually resize the Abris off background (ABRIS_e.png) as after resetting the profile to my two monitors it left a gap around the edges which looked bad but I can't see that doing that could be causing the issues with the Abris.

[doveman]

I've started a new thread about this problem (and some others I'm having with the Helios profile) in a more appropriate section here http://forums.eagle.ru/showthread.php?t=94326