Naruto

Read all of the post, I give several different examples how to do different Monitor configurations and tried to explained the best I could. You will need to make a custom LAU file if you only want two monitors. Make sure you change the DCS main screen UI resolution drop down menu to active both monitors in DCS. https://forums.eagle.ru/showthread.php?t=221925 The following script will make all two monitors auto scale to the max size of each of your particular monitors resolution: _ = function(p) return p; end; name = _('Camera + AMPCD automatic placement'); Description = 'Camera on primary display and AMPCD MFCD on secondary' if displays and #displays > 1 then primary = { x = displays[1].x - screen.x, y = displays[1].y - screen.y, width = displays[1].width, height = displays[1].height, aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } secondary = { x = displays[2].x - screen.x, y = displays[2].y - screen.y, width = displays[2].width, height = displays[2].height, } else primary = { x = screen.width / 2; y = 0; width = screen.width / 2; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } secondary = { x = 0; y = 0; width = screen.width / 2; height = screen.height; } end UIMainView = primary CENTER_MFCD = secondary Viewports = {UIMainView}

same

Have the MSI trio 2080 TI and its much improvement for 4K but not VR IMO, There are some but not much if you want to run at max settings, maybe next gen 3080 TI it will but by then, 8k VR would be the norm and we're in the same predicament. VR needs to figure out how to implement SLI for each VR lens IMO.

Set up the finger lift key bind to your hotas and also ensure the f-18c custom is set to "always on" to get the finger lift to work.

My final monitor set up. Put the two 10" monitors away and decide to go with one 4k monitor and one 12" 1366 x 768 monitor for both Left and Right MFDs and one 15" 1280 x 1024 monitor for the center MFD so I can read it better. This just looks cleaner. To control the AMPCD buttons, I just used left control key as a modifier and used the right Thrustmaster MFD buttons together. Below is the script I made. _ = function(p) return p; end; name = _('3 Monitor LMFCD + Camera + RMFCD + AMPCD'); Description = 'Camera on primary display and AMPCD MFCD on secondary' if displays and #displays > 1 then primary = { x = displays[1].x - screen.x, y = displays[1].y - screen.y, width = displays[1].width, height = displays[1].height, aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } secondary = { x = displays[2].x - screen.x, y = displays[2].y - screen.y, width = displays[2].width, height = displays[2].height, } LEFT_MFCD = { x = displays[3].x - screen.x, y = displays[3].y - screen.y, width =600, height = 600, } RIGHT_MFCD = { x = displays[3].x - screen.x + 780, y = displays[3].y - screen.y, width = 600, height = 600, } else primary = { x = screen.width / 2; y = 0; width = screen.width / 2; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } secondary = { x = 0; y = 0; width = screen.width / 2; height = screen.height; } end UIMainView = primary CENTER_MFCD = secondary Viewports = {UIMainView} Note that in windows 10, my 15" monitor is listed as #3 and the 12" monitor is listed as #2. In the script, its reversed to get the MFD data on the right monitors. I have no clue why its like this so some experimentation is required on your part.

Glad I could help, I edited my post about the show control panel info since its get messed up. Good luck with that if you use it for trimming.

Thats what the auto scaling script does is make the data the full size of the monitor. Try changing the following: UIMainView = primary RIGHT_MFCD = secondary LEFT_MFCD = tertiary CENTER_MFCD = quaternary Viewports = {UIMainView} to UIMainView = primary CENTER_MFCD = secondary LEFT_MFCD = tertiary RIGHT_MFCD = quaternary Viewports = {UIMainView} That should swap the two screen or you can swap plugs in you video card but that will make the windows monitor number not match anymore. Its easier to edit the script. If that does not work, swap the CENTER_MFCD, LEFT_MFCD and RIGHT_MFCD around the secondary, tertiary and quaternary descriptors. Once the data is on the right monitors you want, then go up to the LEFT_MFCD and RIGHT_MFCD script marked as secondary, tertiary or quaternary and change the width and height to the specific size you want like width = 512, height =512 or what ever you want like I did in my 4 monitor setup in post #3. Once you manually change the size it will put the smaller MFD data in the upper left corner starting at x=0, y=0. If you want to move the data right and down, the just add + values to the x = displays[?].x - screen.x and y = displays[?].y - screen.y, like I did in my post #3. You need to play with the values since everyone will have different resolution monitors. Hope it's not too confusing but it will work. Just be aware that if you make the left and right MFCD data smaller on screen, it will get fuzzy as the lines get thicker, you will need to edit it as stated in Post #1 I also changed the font size of the MFD data to make it more readable C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua stroke_thickness = 0.6 stroke_fuzziness = 0.2 This will also change the Hud font size to so adjust to your own preference. I wonder if ED has a script name for the kneeboard, it would be nice to export it to a seperate monitor so its not overlayed on the main cockpit display. Also be aware that if by adding all these monitors, the resolution on the UI is much bigger, then the "Show Control Panel" will not longer be in the lower left corner of the main screen. You will have to edit the ControlsIndicator_page.LUA too and that is a value you will have to mess with to put it back in the lower left corner of the main screen again. It's located in the following folder: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\ControlsIndicator Original vale was the following: base.init_pos = {0,-(1 - 2.0*size_x)} New value is the following for my setup: base.init_pos = {0.80, -0.2} Start with mine since yours is a 4 monitor setup too but you may have to tweek values. Good luck!

Yeah I just noticed it and figured I bring it up. Hope they fixed it, kinda annoying now that I see it, can't stop looking at it.

You have to move the lower setup around and try different ones. Windows monitor identifier don't always match the script below with DCS for some reason. The right MFD is actually my third monitor in windows and the Left MFD is my second but they were on the wrong monitors when I fired up DCS and had to reverse them in the script. Not sure why it does that. Play around with these, trial and error until you get the right data on the right monitor. Once you do, then fix the code to match the size you want or select the code for auto scaling. I also found that if you turn off you monitors in windows or in DCS and turn them back on, it screws with the order sometimes and you have to find the right match again. Found out when I was playing in VR and powered of my monitors and Windows messed with the identifier order. UIMainView = primary RIGHT_MFCD = secondary LEFT_MFCD = tertiary CENTER_MFCD = quaternary Viewports = {UIMainView} FYI when I say auto scaling I mean the script will just make the mfd size fit full size of your monitor resolution. I recommend you remove the manual location and size script and make them all auto scaling and get the data on the right monitor first then manually resize the left and right mfd data. The following script will make all four monitors auto scale to the max size of each of your particular monitors resolution: _ = function(p) return p; end; name = _('LMFCD + Camera + RMFCD + AMPCD automatic placement'); Description = 'Camera on primary display and Left Right AMPCD MFCD on secondary, tertiary and quaternary' if displays and #displays > 1 then primary = { x = displays[1].x - screen.x, y = displays[1].y - screen.y, width = displays[1].width, height = displays[1].height, aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } secondary = { x = displays[2].x - screen.x, y = displays[2].y - screen.y, width = displays[2].width, height = displays[2].height, } tertiary = { x = displays[3].x - screen.x, y = displays[3].y - screen.y, width = displays[3].width, height = displays[3].height, } quaternary = { x = displays[4].x - screen.x, y = displays[4].y - screen.y, width = displays[4].width, height = displays[4].height, } else primary = { x = screen.width / 2; y = 0; width = screen.width / 2; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } secondary = { x = 0; y = 0; width = screen.width / 2; height = screen.height; } end UIMainView = primary RIGHT_MFCD = secondary LEFT_MFCD = tertiary CENTER_MFCD = quaternary Viewports = {UIMainView}

Im not getting anymore that 45 FPS and can't turn off ASW either. Running RTX 2080 ti too.

Do what I do with a 15" monitor. It very readable :)

There is a little black artifact that looks like a triangle next to the left ddi buttons. Its always there and it def not a shadow. I circled it in red. Thought it may be due to a mod but I did a clean restore and its still there with the latest openbeta build.

ASUS PRIME 3270-A, I7 8700K OC (5Ghz) water cooled, 32 Gigs of G.SKILL TridentZ RGB Series 3200 DDR 4 Ram, WD Black 512 GB M.2 NVMe SSD, MSI 2080 TI X Trio OC. Flying around fine but when in the show, dogfighting with several planes or ground pounding or in multiplayer, it stutters every so often and is annoying. All settings almost maxed out but MSAA is off and running in 4K or Oculas VR. Even lowering some of the setting, I still get stutters when alot of activity is going on.

Ok will do it today.

I have a I7 8700K, thinking of getting the I9 9900K, any real advantage for DCS or am I wasting money? Already have a 2080 Ti, so not looking for a FPS increase, just looking to reduce stutters.

I just used the tray tool hud and it def is stuck at 45 fps and even when I check if ASW is enabled with the tray tool hud, it says its off but I still can't go past 45 FPS. Getting frustrating where I'm just going to go back to 4K monitor and track IR.

I tried it and turned it off on the main menu and also created a DCS profile and turned it off there, still stuck at 45 FPS max :(.

Anyone able to get ASW turned off with the latest DCS updates, I'm stuck at max 45 FPS and nothing I tired will get me higher in my Oculas Rift. Running a RTX 2080 TI.

Get voice attack $10 and a mic and you're golden.

All planes act like that when in a landing configuration, depending on which side of the power curve you are. If you fly fast, you on the front side, pitch for altitude, power for speed. If you fly slow, at or below the powercurve, you are on the back side, it is pitch for speed and power for altitude. Even a little C-172 acts this way, trim pitch for the speed you want and use power for altitude changes desired. I am a current PPL and this is what is taught at all flight schools as basic flight 101. Alot of folks still die when they got to far behind the power curve during landing in general aviation. It doesn't matter if you're in a GA aircraft or a jet fighter, don't get behind the power curve for your plane. Nice read https://www.aopa.org/news-and-media/all-news/2002/january/flight-training-magazine/behind-the-power-curve

On my OC 2080 Ti, I get average 75 FPS with everything maxed except MSAA is off since its not needed in 4K and mirrors off which I never use anyways and that with reshader on too. Reshader eats about 5 - 10 FPS and mirrors eat about 10 FPS. 75 FPS vs 40 is a no brainer, so much smoother on a 4K monitor. If i use MSAA to 4X then I drop about 7 FPS and average around 68 FPS I also have 32 Gig of 3200 DDR4 ram and 8700K CPU OC to 5 Ghz. If you got the money, almost double performance is better IMO.

What do you want to see, I have a MSI 2080 TI X Trio running in 4K with almost all setting maxed. Msaa is turned off since its not needed in 4K and I'm using reshader as well. I also have Oculas Rift.

Did some testing and here is the script for adding a fourth monitor that work fine with the AMPCD. I have it set for auto scaling and I moved the Left and Right MFD data down to the center of the screen. I actually like the Center MFCD that big since I can actually read the map now. _ = function(p) return p; end; name = _('LMFCD + Camera + RMFCD + AMPCD automatic placement'); Description = 'Camera on primary display and Left Right AMPCD MFCD on secondary, tertiary and quaternary' if displays and #displays > 1 then primary = { x = displays[1].x - screen.x, y = displays[1].y - screen.y, width = displays[1].width, height = displays[1].height, aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } secondary = { x = displays[2].x - screen.x + 256, y = displays[2].y - screen.y + 128, width = 512, height = 512, } tertiary = { x = displays[3].x - screen.x + 256, y = displays[3].y - screen.y + 128, width = 512, height = 512, } quaternary = { x = displays[4].x - screen.x, y = displays[4].y - screen.y, width = displays[4].width, height = displays[4].height, } else primary = { x = screen.width / 2; y = 0; width = screen.width / 2; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } secondary = { x = 0; y = 0; width = screen.width / 2; height = screen.height; } end UIMainView = primary RIGHT_MFCD = secondary LEFT_MFCD = tertiary CENTER_MFCD = quaternary Viewports = {UIMainView}

Working in V2.5.3.22176 I created a new Lua file called "LMFCD + Camera + RMFCD automatic placement" in the C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Config\MonitorSetup folder. This will set the main monitor and MFD monitors to auto correct and fill in the MFD data to the resolution of your second and third monitor. Here is the script I used to set it up: _ = function(p) return p; end; name = _('LMFCD + Camera + RMFCD automatic placement'); Description = 'Camera on primary display and Left MFCD on secondary' if displays and #displays > 1 then primary = { x = displays[1].x - screen.x, y = displays[1].y - screen.y, width = displays[1].width, height = displays[1].height, aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } secondary = { x = displays[2].x - screen.x, y = displays[2].y - screen.y, width = displays[2].width, height = displays[2].height, } tertiary = { x = displays[3].x - screen.x, y = displays[3].y - screen.y, width = displays[3].width, height = displays[3].height, } else primary = { x = screen.width / 2; y = 0; width = screen.width / 2; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } secondary = { x = 0; y = 0; width = screen.width / 2; height = screen.height; } end UIMainView = primary RIGHT_MFCD = secondary LEFT_MFCD = tertiary Viewports = {UIMainView} I originally had LEFT_MFCD = secondary and RIGHT_MFCD = tertiary but they MFDs came out reversed. I was using 10 inch monitors so I had to modify the script slightly to make the MFD symbology smaller and centered on my screens so the displays will fit inside a thrustmaster MFD that I ordered and will arrive Thursday. Here is the slight tweak to the above script based on my monitor sizes, yours will need to be adjusted depending on what size monitors you have. I may buy smaller monitors later since the ones I'm using were originally for X Plane 11 C172 G1000 Displays cockpit I planned on building. _ = function(p) return p; end; name = _('LMFCD + Camera + RMFCD automatic placement'); Description = 'Camera on primary display and Left MFCD on secondary' if displays and #displays > 1 then primary = { x = displays[1].x - screen.x, y = displays[1].y - screen.y, width = displays[1].width, height = displays[1].height, aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } secondary = { x = displays[2].x - screen.x + 256, {this moved the data from the upper left corner to the center of the monitor, this comment does not need to be included in the script} y = displays[2].y - screen.y, {I could probably add value here to move the data down some, this comment does not need to be included in the script} width = 512, height = 512, } tertiary = { x = displays[3].x - screen.x + 256, y = displays[3].y - screen.y, width = 512, height = 512, } else primary = { x = screen.width / 2; y = 0; width = screen.width / 2; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } secondary = { x = 0; y = 0; width = screen.width / 2; height = screen.height; } end UIMainView = primary RIGHT_MFCD = secondary LEFT_MFCD = tertiary Viewports = {UIMainView} I also changed the font size of the MFD data to make it more readable C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua stroke_thickness = 0.6 stroke_fuzziness = 0.2 This will also change the Hud font size to so adjust to your own preference. Also make sure you select the higher resolution in the DCS monitor Resolution drop down menu in the UI so all the monitors will turn on in DCS. I'm sure you can keep modifying the code to add more monitors and other displays like the RWR, UFC, AMPCD and IFEI Also RIGHT_MFCD and LEFT_MFCD must be capitalized at bottom of the script or the data will not show up on the monitors for some reason. Credit goes to Capt Zeen for some of the info here and ED for some of the auto scaling script I modified to add a third monitor. All credit goes to them as I just messed around playing with their info until I figured out how to add a third monitor for a second TM MFD. Only works for F-18C, AV8BNA and A-10C that I have tested at the moment. The AV8BNA needs the external Left_MFCD and Right_MFCD key bindings to be set to a key or HOTAS button to work correctly.

Huey already gifted.