Jump to content

Dummies Guide for the “MonitorSetup.lua“


Recommended Posts

The display I have is this

 

DSCN1279_zps71bd0b1a.jpg

 

or this:-

Screen_131211_190701_zpsc4ffe85f.jpg

 

Using this set up

 

_ = function(p) return p; end;

name = _('3 Screen + MFCD');

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;

}

}

LEFT_MFCD =

{

x = 1355;

y = 548;

width = 512;

height = 512;

}

RIGHT_MFCD =

{

x = 3961;

y = 548;

width = 512;

height = 512;

}

UIMainView = Viewports.Center


Edited by Jetkar

Regards

[sIGPIC][/sIGPIC]

 

 

 

Steam ID: Jetkar

Steam Group: 223rd CAS

Join and fly with us on the 223rd CAS Dedicated server

Link to comment
Share on other sites

  • 3 weeks later...

Thankyou PeterP for the valuable help of the guide!!!!

 

Phanteks Enthoo Evolv Tempered Glass, Asus ROG Maximus IX Hero, Intel i7 7700K @ 4.8, Corsair HX 1000i, Nzxt Kraken 62, 32gb DDR4 3000Mhz Corsair Dominator Platinum, Nvme SSD Samsung 960 Evo 1Tb, Asus Strix OC 1080ti, Philips 43" 4K Monitor + 2 x Dell 24" U2414H, Warthog HOTAS, Track IR 5, Obutto R3volution, Buttkicker Gamer 2, MFG Crosswind pedals, Occulus Rift CV1, Windows 10 Pro.

Link to comment
Share on other sites

 

So can anyone fill me in on what I'm missing? I'm playfully curious since I'm extremely interested in the technology and the potential. Sorry for nagging or being off topic but I figured PeterP was the PERFECT person to ask about it.

Yes I can:

I didn't have the time to evaluate your idea at all .

36 hours aren't enough for me to give you any answer if it is doable at all what you have in mind and how easy/hard this might be.

 

Let me elaborate: I have a family, friends, my daily job (that will start again tomorrow), and many other things that have a much, much higher priority than the DCS.

 

Don't get me wrong , but right now I'm even not able to answer if I'm able to help at all .

I even didn't read your original thread and I don't know what exactly is needed to simulate the functions of the "ROVER".

 

And I also don't think that this thread is the appropriate one to discuses your idea/request.

 

Maybe bump you original thread instead this one.

 

sorry if this isn't the answer you expected from me, but this is all that I can say up to now.

 

And have some patience, - you can't force someone to do some research for you.


Edited by PeterP

Link to comment
Share on other sites

  • 2 months later...

3 Monitors

 

I have looked through a lot of the forums and I just don't have a lot of time.. I have 3 monitors all 1920x1080 and want to have the huds on left and right and fly Chopper in middle.

 

I have tried various configs to varying degrees of success and still haven't managed it.. Would be great to have xtras info on other screens to.. anyway if someone has a 3 monitor setup lua that would be great!

 

Cheers,

Aussie777

Link to comment
Share on other sites

  • 1 month later...

We should have this added to the first post & make people read the whole thing before posting. The youtube vid is hilarious.

 

Really in the first post needs a HOW TO ASK A QUESTION IN THIS THREAD TUTORIAL.

 

This should start it.

 

As a starter , please try this link and follow the info you get:

http://lmgtfy.com/?q=how+to+open+a+zip

 

Once you have read the pdf and still have questions left:

 

Please give us all available info about your system - especially your GPU and if you are able to use eyefinity or surround and in which exact resolution .

 

The best thing would be that you attach simply a dxdiag.txt - as it will short-cut long-winded discussions ,

because this dxdiag.txt will contain every info of your system and people that want help you will have the whole picture and they can see what your system is capable without the need to bother you with cryptic questions at all.

 

 

And here is a general 'how to attach a file' (your dxdiag.txt) - the needed steps a very,very similar on this forum - you just have to look for the button called "Manage Attachments".

 

 

Then

so 'we' can teach you how to do it in DCS ?

Posting the requested info it would be also a good idea to start naming your problems more detailed instead just telling "it is just DCS that I struggle with" .

 

...so no one has to guess around and/or gets the feeling to be one of the protagonists of this video:

 

 

:)

 

EDIT:

 

Please don't get me wrong - but I/we need some kind of 'starting point' to give you better assistance .

Help us to help you!

 

GREAT EXAMPLE:

 

Up to now we know that you

-can't open a zip

-have had three screens for 4 years now and I still do not have them set up right

-have a i7 pushing two titans

-no problems in other games

-you struggle to get DCS working as you want.

 

Expanded:

 

Things that we don't know

-did you finally learned how to decompress zip and did you read the pdf

-what have you tried already , so we can rule out possible user errors

-how does the your 'problem' look/ what do you not understand.

-what do you expect to see on your monitors.

-how is you desktop arranged.

-which res did you set up in DCS

-did you tried to switch off SLI

- Which OS your running.

- Exactly which version number of DCS module are you running? found on bottom right corner when you start DCS

- Which other modules are active. ie Combined Arms, P-51 etc.

- Your options file from C:Users[Your User NAME]Saved GamesDCSConfig

- Your Multimonitor setup lua from C:Program FilesEagle DynamicsDCS WorldConfigMonitorSetup

- a real life picture of setup if relavent.

- an in game snapshot of the problem.

- how to take a screenshot within windows ie (printscreen button)

 

See, there a so much variables involved that can cause a failure - we need a better description of your problem or we will end up like the two blind guys in the video.


Edited by thinkr

Modded CapLoz HeliosV2.1_1280x1024.zip

 

2x 1080p 22"Monitors, Saitek X52, Saitek Combat Rudder Pedals, Trackir5, Win7Pro Pro 64Bit, Intel Q9550 @3.8Ghz, EP45-UD3L, 8GB Ram, Nvidia 560Ti 2GB, 2x 500GB Velociraptor

 

Flaming Cliffs 3

DCS:A10C,KA-50, Huey, Mi-8, WWII Euro 40+ Supporter, Mig21

Falcon 4 BMS

IL-2 Sturmovik: 1946

Take on Helicopters

Arma 2 AO + PMC + BF All Addons Series

Arma 3

EECH & EEAH

Medivac & Search and Rescue 4 Series

 

 

Link to comment
Share on other sites

  • 5 months later...

Quick question....

 

ED_A10C_CMSP =

 

ED_A10C_RWS =

 

ED_A10C_CDU =

 

Do not appear at all....

 

LEFT_MFCD =

RIGHT_MFCD =

 

Appear on my second screen as wanted in the correct places.

 

I did some searches on viewports, read the monitor setup PDF, and even installed easy monitor configuration tool, and pressed the install LUA button (i'm not certain it did tho tbh)

 

EMC deactivates ingame displays as claimed, but all the tabs I see in EMC are missing except the MISC tab.

 

So bit of a double barrelled question I guess, firstly none of the extra displays work for me, and secondly EMC doesn't work as indicated in some vids, my ED path is correctly displayed in the bottom of the EMC first screen tho.

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 months later...

I have this working fine. Thanks PeterP!

 

A few days ago I started to integrate 'if' statements into my MonitorSetup lua file so I could have a different viewport with the standard mfds for other Aircraft like Su-25t, F15, etc.. But it will not work with these export names in your mod. I got this script from Maverick-X and it works fine 'without' your mod installed using the stock game's standard viewport names (RIGHT_MFCD, LEFT_MFCD, etc.)

 

However, if you install your mod init files (I have them setup for jsgme), and I change the viewport names to your new names, it fails every time. I am thinking that maybe it has something to do with this reconfigure_for_unit() function not recognizing your viewport names? I am guessing that this is somehow called when a mission runs to see which viewports to use, and it passes the aircraft_type. But it probably cannot resolve your new names.

 

In this lua script, when I fly the ka50 it does put the game on the center monitor. So it IS calling the function correclty and passing the aircraft name. But then the shkval does not appear at those coordinates. So, I think the code fails at that point. The shkval and abris show up on the left and right sides of the screens, which is a default position I believie.

 

_  = function(p) return p; end;
name = _('Maverick-Xs test IFs');
Description = 'Testing!'

function default_setup()
   Viewports =
   {
        Center =
        {
             x = 0;
             y = 0;
             width = 5760; 
             height = 1080; 
             viewDx = 0;
             viewDy = 0;
             aspect = 5760 / 1080;
        }
   }
  
   Gui =
   {
      x = 0;
      y = 0;
      width = 1920;
      height = 1080;
   }

UIMainView = Gui          
end

default_setup();
UIMainView = Viewports.Center;

function reconfigure_for_unit(unit_type)

   if unit_type == 'Ka-50' then
      
   Viewports = {

        Center =
        { 	-- PUT KA50 ON CENTER SCREEN JUST TO SEE IF THIS CODE IS RUN...
             x = 1920;
             y = 0;
             width = 1920;
             height = 1080;
             viewDx = 0;
             viewDy = 0;
             aspect = 1920 / 1080;
        },
}

ED_KA50_Shkval =
{
	 x = 1920;
	 y = 0;
	 width = 823;
	 height = 656;
}
  else
       default_setup()
   end
end

 

 

I also tried coding it without the functions, and just an in-line if then elseif statement, but it needs the aircraft names and I can't figure out how to get them. :doh:

 

And ideas anyone??

I am about to give up on this. I've spent 5 hours today, and several more the past 3 days on this... :cry:

 

_  = function(p) return p; end;
name = _('Maverick-Xs No Functions');
Description = 'testing'

Viewports =
{
 Center =
 {
	  x = 0;
	  y = 0;
	  width = 5760; 
	  height = 1080; 
	  viewDx = 0;
	  viewDy = 0;
	  aspect = 5760 / 1080;
 }
}

GUI =
{
  x = 0;
  y = 0;
  width = 1920;
  height = 1080;
}

UIMainView = GUI          
--UIMainView = Viewports.Center;

local myInfo = LoGetSelfData()
unit_type = myInfo.Name

if unit_type == 'Ka-50' then
Viewports = {
	 Center =
	 { 	-- PUT KA50 ON CENTER SCREEN JUST TO SEE IF THIS CODE IS RUN...
		  x = 1920;
		  y = 0;
		  width = 1920;
		  height = 1080;
		  viewDx = 0;
		  viewDy = 0;
		  aspect = 1920 / 1080;
	 },
}

ED_KA50_Shkval =
{
	 x = 1920;
	 y = 0;
	 width = 823;
	 height = 656;
}
else
Viewports = {
	 Center =
	 { 	-- PUT ALL OTHERS ON RIGHT SCREEN...
		  x = 3840;
		  y = 0;
		  width = 1920;
		  height = 1080;
		  viewDx = 0;
		  viewDy = 0;
		  aspect = 1920 / 1080;
	 },
}
end

 

I have 3 monitors in nVidia Surround (5760x1080) for the game and a 1920x1080 touchscreen centered below this.

 

In the above code sample, it does work

 

Thanks,

Snack


Edited by Snacko

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

Ok, I finally got this working. I don't know if someone has done this before. (I couldn't find it) I have ALL viewports for ALL Aircraft located where I want them on my screen, all in ONE MonitorSetup lua file. So I will no longer need to change my Options/Graphics/Monitors setting to export different viewports. This has all the viewports that I know about. The MiG21 has some limitations, but works.

 

The main issue is that the function that lets you check which aircraft you are running crashes if you have a viewport name that it does not like. But I worked around it... Just thought that I would share.. :)

 

My rig is 3 monitors at 5760x1080 with a touchscreen in the center below it (T) at 1920x1080. And I used PeterP's "All Exports ON for A10c & Ka50" mod to export the viewport names all at the same time. (THANKS PeterP!) Here's my code:

 

_ = function(p) return p; end;
name = _('Helios - Export ALL Viewports');
Description = 'Screen Size: 5760x2160, with the Game on 5760x1080, and the Viewports on the bottom screen.'
-- *********************************************************************************************************
-- FOR THIS TO WORK, 
--   SET YOUR !!!!!!!!SCREEN RESOLUTION!!!!!! IN THE GAME OPTIONS 
--       TO THE >>>>>>>FULL SIZE OF "ALL" OF YOUR SCREENS<<<<<<<< so export windows can be rendered.
--          and UNCHECK: FULL SCREEN
--                   AND PUT THIS FILE IN: '..\DCS World\Config\MonitorSetup'  And Select it from the Options Menu.
-- *********************************************************************************************************
-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-- THIS USES PeterP's Init Files in my JSGME 'Export - All Viewports' Script Mod.
-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Viewports =
{
    Center =   -- This is the Camera of the rendered in-game world.
			-- What you see and everything behind the next bracket is controlling to this view-port.
    {
         x = 0;  		 -- Left/Upper corner will start at this X Point inside your set-in-game resolution.
         y = 0;  		 -- Left/Upper corner will start at this Y Point inside your set-in-game resolution.
         width = 5760;  -- Width  of the "Center"-view port inside the in-game resolution.
	  -- !!!SCREEN RESOLUTION MUST BE: 2160 !!!!  TO EXPOSE AREAS FOR THE EXPORTED WINDOWS.
         height = 1080; -- Height of the "Center"-view port inside the in-game resolution.
         viewDx = 0;    -- Horiz. default view-point direction
         viewDy = 0;    -- Vert.  default view-point direction
         aspect = 5760/1080;  -- screen.width/screen.height by default.
    }
}
GUI =
{
    x = 1920;  -- !!!!!!!!! LEFT CLICK ON LEFT SIDE OF DESKTOP WHILE MULTIPLAYER IS LOADING TO FIX MULTIPLAYER MENU BUG !!!!!!!!!!
    y = 0;
    width = 1920;
    height = 1080;
}
-- UIMainView = Viewports.Center  -- ORIGINAL UIMainView
UIMainView = GUI

--XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
--[[ -- THIS CODE WILL  N O T  WORK HERE!   COPY IT TO THE EXPORT.LUA TO RUN IT!
-- CHECK YOUR AIRCRAFT NAME:
local self = LoGetSelfData()
local TBfilepath = "c:/DCS_AircraftName.log"
local TBfile = nil
TBfile = assert(io.open(TBfilepath, "w"))
TBfile:write(string.format("Aircraft=%s\n", self.Name))
TBfile:close()
]]--
--XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


--////////////////////////////////////////////////////////////
--	   A 1 0 C  -  Loz A10c profile.
--////////////////////////////////////////////////////////////
ED_A10C_LEFT_MFCD =  --done
{
	 x = 1987;
	 y = 1200;
	 width = 445;
	 height = 445;
}

ED_A10C_RIGHT_MFCD =  --done
{
	 x = 3326;
	 y = 1200;
	 width = 445;
	 height = 445;
}
	
ED_A10C_CLOCK =  --done
{
	x = 2398;
	y = 1907;
	width = 125;
	height = 124;
}	
	
ED_A10C_RWR =  --done
{
	x = 2508;
	y = 1230;
	width = 198;
	height = 198;
}	

ED_A10C_CMSC =   --done
{
	x = 2775;
	y = 1220;
	width = 230;
	height = 50;
}

ED_A10C_UHF_REPEATER =  --done
{
	x = 2573;
	y = 1779;
	width = 115;
	height = 25;
}
		
ED_A10C_CMSP =  --done
{
	x = 2996;
	y = 1275;
	width = 263;
	height = 58;
}

ED_A10C_UHF_PRESET_CHANNEL =  --done
{
	x = 2665;
	y = 1561;
	width = 34;
	height = 23;
}
	
ED_A10C_UHF_FREQUENCY_STATUS =  --done
{
	x = 2554;
	y = 1645;
	width = 128;
	height = 30;
}

--[[ I don't think this profile has the CDU...
ED_A10C_CDU =
{
	x = 300;
	y = 600;
	width = 200;
	height = 200;
}
]]

--/////////////////////////////////////////////////////////
--	   K A - 5 0  for Capt. Zeen's profile.
--/////////////////////////////////////////////////////////
--SHKIVAL
ED_KA50_Shkval =
{
	 x = 1920;
	 y = 1080;
	 width = 823;
	 height = 656;
}

--ABRIS
ED_KA50_ABRIS =
{
	 x = 3250;
	 y = 1080;
	 width = 590;
	 height = 852;
}

-- PVI800
ED_KA50_PVI =
{
	 x = 1940;
	 y = 1754;
	 width = 230;
	 height = 110;
}

--EKRAN
ED_KA50_Ekran =
{
	 x = 3100;
	 y = 2048;
	 width = 110;
	 height = 80;
}

--UV26
ED_KA50_UV26 =
{
	 x = 2820;
	 y = 1618;
	 width = 190;
	 height = 70;
}
--[[
--CAUTION LIGHTS
ED_KA50_CautionLights =
{
	x = 1920;
	y = 1150;
	width = 700;
	height = 700;
}
]]--



-- MiG-21Bis DOEN'T WORK IN THE FUNCTION CALL BELOW:
RIGHT_MFCD = 
{
	 x = 3326;
	 y = 1200;
	 width = 445;
	 height = 445;
}
	
--////////////////////////////////////////////////////////////////////////////////////
--	   B E G I N   F U N C T I O N   C A L L   F O R   O T H E R   A I R C R A F T 
--////////////////////////////////////////////////////////////////////////////////////
function reconfigure_for_unit(unit_type)

if unit_type == 'A-10C' then
	-- DO NOTHING HERE, THESE VIEWPORTS ARE HANDELED ABOVE.
	--   This is needed here so that it does not revert to the 
	--   default statement at the bottom for an unknown aircraft type.

elseif unit_type == 'Ka-50' then
	-- DO NOTHING HERE, THESE VIEWPORTS ARE HANDELED ABOVE.
	--   This is needed here so that it does not revert to the 
	--   default statement at the bottom for an unknown aircraft type.

   elseif unit_type == 'Su-25T' then	-- tested
	--/////////////////////////////////////////////////////////
	--	   S U - 2 5   for Capt. Zeen's profile.
	--/////////////////////////////////////////////////////////
	RIGHT_MFCD =
	{
		 x = 3121;
		 y = 1084;
		 width = 653;
		 height = 433;
	}

elseif unit_type == 'Su-25' then	-- tested
	-- NO MFDs

elseif unit_type == 'F-15C' then	-- tested
	RIGHT_MFCD =	-- ACTUALLY IS LEFT MFCD.  
	{
		 x = 2210;
		 y = 1080;
		 width = 383;
		 height = 383;
	}

elseif unit_type == 'A-10A' then	-- tested
	RIGHT_MFCD = 
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}


elseif unit_type == 'MiG-29A' then	-- tested
	RIGHT_MFCD = 
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}

elseif unit_type == 'MiG-29G' then	-- tested
	RIGHT_MFCD = 
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}
	
elseif unit_type == 'MiG-29S' then	-- tested
	RIGHT_MFCD = 
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}

elseif unit_type == 'Su-27' then	-- tested
	RIGHT_MFCD = 
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}
	
elseif unit_type == 'Su-33' then	-- tested
	RIGHT_MFCD = 
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}

elseif unit_type == 'UH-1H' then	-- tested

elseif unit_type == 'Mi-8MT' then	-- tested
--[[		RIGHT_MFCD = 		-- HAS SOME CONTROLLER INDICATOR ON RIGHT SIDE.
	{
		 x = 3326;
		 y = 1200;
		 width = 445;
		 height = 445;
	}	
]]--
elseif unit_type == 'F-86F Sabre' then	-- tested

elseif unit_type == 'MiG-21Bis' then	-- tested
--[[  -- THIS VIEWPORT DOES NOT WORK IN THIS FUNCTION RIGHT NOW.  SO, IT IS CALLED ABOVE.
	RP22 = 	-- NONE OF THESE WORK RIGHT NOW.
	MFD_RIGHT = 
]]
elseif unit_type == 'BF-109K-4' then

elseif unit_type == 'FW-190D9' then

elseif unit_type == 'P-51D' then	-- tested

else
	--////////////////////////////////////////////
	--	   O T H E R   A I R C R A F T  
	--	D E F A U L T   S C R E E N   T O   
	--		  6 4 0   X   4 8 0
	--	SO I KNOW THAT IT IS AN UNKNOWN AIRCRAFT
	--////////////////////////////////////////////
	Viewports = {
		 Center =
		 {
			  x = (screen.width - 640) / 2;
			  y = (1080 - 480) / 2;
			  width = 640; --screen.width;
			  height = 480; --screen.height;
			  viewDx = 0;
			  viewDy = 0;
			  aspect = 640 / 480;
		 },
	}

       LEFT_MFCD = nil  	-- remove for others 
       RIGHT_MFCD = nil  	-- remove for others 
   end
end


Edited by Snacko

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

  • 9 months later...
Excellent job, this is what i was looking for. I tried it several times with no luck.

 

That works with 1.2 using PeterP's Export mod. But some things have changed for 1.5/2.0. And I am working that out now.. :cry:

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

Ah,,, finally found something, Snacko, I have been using Helios for many years with Loz files, and Peter P files to handle the exports. I am in the midst of installing 1.5 & 2.0 fresh because I have had some keybinding issues, likey related to copying over INPUT file for controls etc. So what I'm trying to find out before I proceed is if Peter P's files are still valid to use in 1.5 and 2.0 to help with the exports? I'm basically trying to figure out what the latest procedure to be so I can install it. I see you mentioned you are working on something. Please advise, thanks

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

PeterP's viewport mod doesn't work for me in 1.5 or 2.0. I didn't want to spend the time trying to figure out why they fail. I have a friend who has the exports working and just tested the A10c. It worked in a simple monitorsetup.lua but not in my 'all in one' script. So, I am going to try and get the Ka50 and others working and then try and fix my 'all in one' script.

 

I am not sure what mod or where he got his scripts. But I have attached the files to this post. It's just for the A10c. :smilewink:

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

ok,,, I did get everything to work for Helios in 1.5 as it was for 1.2, but that is when I took the latest backup.00# file from 1.2 and copied them into the 1.5 root directory. All was well, but since i'm doing a clean install because Im trying to figure out what is interrupting the key commands, Im not copying and files over (not supposed to anyway).

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

The main problem that I can find is that the reconfigure_for_unit() function does not work anymore in 2.0. It's in Alpha, so I cannot complain.

 

But I spent several hours today trying to figure it out. When I use that function to setup different viewports for different aircraft, none of it works. And there is NO error or any message of any kind in the DCS.log file! And I cannot write any of my own debug output to see where it is failing using the lua io object or use the dbg_print() function. Both are unavailable in these lua files. So, it's hard to debug, but it seems to be that the reconfigure_for_unit() function simply does not work. If I just comment out that function, everything works.

 

So, at this point I will just have to wait until I hear something else or they fix that function. All of my exports will need to be in separate MonitorSetup lua files I guess, or I just wont use Helios now..

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

Just for the heck of it. look at the last post of this thread, I am in the middle of editing the provited monitor config file so I can test it out, but Scooternuts & RightStuff have seemingly made this work. I am looking into both options, but trying Rightstuffs 1st as he has it setup to use with JSGME

 

http://forums.eagle.ru/showthread.php?t=70716

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

Are you saying that they have 'all' of the viewports for the a10c, ka50, and other aircraft in one MonitorSetup Lua file?

 

I took a quick look at that thread yesterday but didn't see that..

 

Sent via Galaxy Note 4 with Tapatalk.

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

I will say this, I downloaded Rightstuffs file, and looked in his monitor config.lua, and yes, he has the A-10C and KA-50 in it along with some others. i am in the process of editing that file to accommodate my X & Y coordinates, so I have not tested yet, but to me, it all looks in order.

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

Thank you so much!

 

I downloaded his files last night, but was too tired to look at them deeply. And I was not sure what version of DCS his stuff worked with...

 

But he did use that function to get the names of the aircraft. And that function does work. But the old init viewport files that I had tried must have not been reporting the correct aircraft names (ie. 'A-10C'). After trying his init files for one viewport it worked. So, I tried them all, and now my all-in-one monitorsetup lua file seems to work.

 

Off to wrap Christmas presents and run errands now.. But it seems to be fixed with these new init files. So, hopefully I will get a chance to fix everything today or tomorrow..

 

Merry Christmas!

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

Nice to hear! I'm hoping to get this up and running soon myself

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

Great to see this is still active.

I decided to get serious again. Just got Thrustmaster "Cougar" pack, 2 MFDs.

 

#Lateral:

* DCS Dual Monitor setup, need help with lua script: http://simhq.com/forum/ubbthreads.php/topics/3664729#ixzz3uitFJtkA

*

** http://wiki.hoggit.us/view/Simulator_Scripting_Engine_Documentation

** http://wiki.hoggit.us/view/DCS_Configuration#Installing_TARS_TeamSpeak_Plug-In

 

* DCS BIOS Using LCD display: [ame=https://www.youtube.com/watch?v=h5kmggq4ykE]

[/ame]

 

** HomePage: http://dcs-bios.a10c.de/

** YT: https://youtube.com/channel/UCwECFPfC3QJiNYS5fskF2vg/videos

 

* Network Many Arduinos w/Sensors: [ame=http://www.youtube.com/watch?v=asxBA2k29bE]

[/ame]

Panzer Blitz => Panzer General => BF1942 => BF2 => OFP DR => WWIIOL => ArmA:OA => IL-2: BoS => DCS Ka-50

Link to comment
Share on other sites

  • 9 months later...

Perhaps somebody can help this DCS newbie out. I'm running 3 27" monitors in Nvidia surround for a 5760x1080 single display. Consequently in the DCS graphic setup GUI I've got single monitor chosen with that resolution. While it looks great having that large FOV, the side monitors are pretty distorted when looking out of them. What's the best way to address this? Seems like when I select 1920x1080 and 3 monitors my side monitors are not used and my center monitor just shows a narrow image. Sorry for the dumb question, but I'm used to Iracing where it's just a single button click for the option of "rendering each monitor separately".

Link to comment
Share on other sites

Not really fixable. It has to do with the FOV. Check out this:

 

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm
Gigabyte RTX 4090 Gaming OC 24gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 49" Samsung Curved Widescreen │ 28" Touchscreen

- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Link to comment
Share on other sites

  • 2 weeks later...

I know I'm getting older and my mind isn't what it used to be I am having a hell of a time figuring out something that someone else might find absolutely simple. I'm wanting to operate DCS black shark KA-50 in DCS world 1.5.4 with two monitors the main one displaying the normal cockpit and the second on displaying only Abris.

I'm using win 7 ultimate the main monitor is 1920 X 1080 secondary is 1600X900

 

I don't care if the abris isn't perfectly displayed as far as aspect ratio but I would like the whole Abris to be displayed I guess with black bars on each side to maintain some normal aspect ratio for the abris.

 

Every time I've followed this guide I keep coming up an extra wide main and no abris.

The combined size I'm setting in game is 3520x1080 I get main screen and part of the main on the left side on the second and no abris, only the radar in upper right corner of second monitor. Driving them with a single gtx 960.

 

Any hints or guidance would be greatly appreciated.


Edited by aairon

Flying sims since 1980

 

[sIGPIC][/sIGPIC]

Mobo: Asus Z170 Pro Gaming

CPU: i7 6700K @ 4.7 GHz

Video: EVGA GTX 1080

Ram: Patriot DDR4 2800 8GBx2

PWR:Corsair RM750i

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...