Maulkin Posted June 7, 2018 Share Posted June 7, 2018 I tried using my multimonitor configuration but it causes the left and right DDI's to no longer display anything at all. I have not yet attempted to re-route the DDI video output so technically nothing should have changed from a single monitor setup. The center AMPCD still works however. Has anyone gotten this to work? --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars Link to comment Share on other sites More sharing options...
=Panther= Posted June 7, 2018 Share Posted June 7, 2018 Not implemented in the current Open Beta release. Don't think they have said a timeframe when it will be available either. Twitch Channel [sIGPIC][/sIGPIC] Virtual Thunderbirds, LLC | Sponsored by Thrustmaster Z390 Aorus Xtreme, i9 9900k, G.SKILL TridentZ Series 32GB, 1080ti 11GB, Obutto R3Volution, Thrustmaster HOTAS Warthog, TPR, Cougar MFDs, FSSB R3L, JetSeat, Oculus Rift S, Buddy-Fox A-10C UFC, F/A-18C UFC, Tek Creations F-16 ICP Link to comment Share on other sites More sharing options...
Maulkin Posted June 7, 2018 Author Share Posted June 7, 2018 I'm ok with it not implemented but setting DCS into a multimonitor mode (even if I have not set up the F-18 module to take advantage of it) causes the in-cockpit DDI displays to not function. This is annoying because it means I cannot use the multimonitor setup on my AV-8B, M-2000, A-10C, KA-50, and Mig-21 without having to switch back and forth. I was hoping it was simply something I was doing incorrectly.Not implemented in the current Open Beta release. Don't think they have said a timeframe when it will be available either. Sent from my P00A using Tapatalk --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars Link to comment Share on other sites More sharing options...
xoxen Posted June 7, 2018 Share Posted June 7, 2018 If you have exported the MFCDs like in the A-10C it seems like the DDIs stay black. I kicked the MFCD export out of my config and now it works fine. My 3 Display setup is still working like in the other modules. Xoxen AMD Ryzen 7 5800X3D, MSI MPG X570 Gaming Plus, 64GB Crucial Ballistix DDR4-3600 CL16, Asus TUF Gaming RTX 4080 OC, Windows 10 64bit Home Premium, TrackIR 5 with TrackClip: Pro!, Virpil MongoosT-50CM3 Base + TM Warthog Stick + 7cm extension + WINWING Orion 2 with F-15EX grips, Cougar MFDs with 8" displays, Saitek Rudder Pedals, Samsung Odyssey G9 49" 5120x1440 @120 Hz Link to comment Share on other sites More sharing options...
SkateZilla Posted June 7, 2018 Share Posted June 7, 2018 (edited) Right now if Any Viewports are Exported (RIGHT_MFCD, LEFT_MFCD etc), The DDIs Will be blank. You can either remove them or set a function to have separate options for FA-18C: Example: function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end I will post a full Monitor Setup Config in a few. Edited June 7, 2018 by SkateZilla Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs Link to comment Share on other sites More sharing options...
Maulkin Posted June 12, 2018 Author Share Posted June 12, 2018 Thanks SkateZilla I will try that out! --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars Link to comment Share on other sites More sharing options...
mhe Posted June 12, 2018 Share Posted June 12, 2018 Right now if Any Viewports are Exported (RIGHT_MFCD, LEFT_MFCD etc), The DDIs Will be blank. You can either remove them or set a function to have separate options for FA-18C: Example: function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end I will post a full Monitor Setup Config in a few. That code example is worth gold. Does the monitor config get parsed let's say when I change aircraft in an MP session or only upon initial loading of the sim? That is my convoluted way of asking whether I can do a unified monitor config that contains all my Helios capable aircraft in a way that they don't interfere with each other and that I can change aircraft in an MP session with my viewports syncing up with whatever I fly at the time? | i9 12900K | 64GB DDR5-6000 | STRIX RTX 4090 OC | LG 38GN950 38" | | Hanns-G HT225HPB | TIR 5 & Varjo Aero | Virpil Throttle & Stick | TM TPRs | You don't stop playing because you grow old, you grow old because you stop playing. Link to comment Share on other sites More sharing options...
Maulkin Posted June 12, 2018 Author Share Posted June 12, 2018 So I am having a bit of trouble getting this to work. This is where I am starting from, where the A-10C works and the MFCD's are exported correctly to the second monitor (but the F-18C is having trouble with the DDI output in-cockpit): multimonitor_setup.lua: _ = function(p) return p; end; name = _('General Multimonitor'); Description = 'A general multimontor config for all modules' Viewports = { Center = { x = 0; y = 0; width = 2560; height = screen.height; viewDx = 0; viewDy = 0; aspect = 2560 / screen.height; } } KNEEBOARD = { x = 0; y = 0; width = 526; height = 789; } ------------ -- for A-10C ------------ LEFT_MFCD = { x = 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } RIGHT_MFCD = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } ------------ -- for Ka-50 ------------ SHKVAL_SCREEN = { x = 2560; y = 0 + 360; width = 980; height = 817; -- must be this height to hide splash screen } ABRIS_SCREEN = { x = 2560 + 980; y = 0 + 360; width = 940; height = 1080; } -------------- -- for M-2000C -------------- MIRAGE_RADAR = { x = 2560; y = -100 + 360; width = 1920 / 2; height = 1080; } MIRAGE_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } COM = { x = 1920 / 2 + 2560; y = 0 + 360; width = 120; height = 70; } ECM_CHF = { x = 1920 / 2 + 2560; y = 610 + 360; width = 75; height = 40; } ECM_FLR = { x = 1920 / 2 + 2560; y = 650 + 360; width = 75; height = 40; } PCA_UR = { x = 2560; y = 980 + 360; width = 500; height = 50; } PCA_BR = { x = 2560; y = 1030 + 360; width = 500; height = 50; } PPA = { x = 1920 / 2 + 2560; y = 810 + 360; width = 70; height = 90; } PCN_UR = { x = 2560 + 1920 - 700; y = 1080 - 120 + 360; width = 500; height = 60; } PCN_BR = { x = 2560 + 1920 - 700; y = 1080 - 60 + 360; width = 250; height = 60; } FUEL = { x = 2560 + 1920 - 80; y = 0 + 360; width = 80; height = 45; } -------------- -- for Mig-21 -------------- MIG21_RADAR = { x = screen.width / 2; y = 0 + 360; width = 1080; height = 1080; } -------------- -- for F-5E -------------- AN_APQ159_RADAR = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1080; height = 1080; } AN_ALR87_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } UIMainView = Viewports.Center and this is the modified code with what I think you were describing: _ = function(p) return p; end; name = _('General Multimonitor'); Description = 'A general multimontor config for all modules' Viewports = { Center = { x = 0; y = 0; width = 2560; height = screen.height; viewDx = 0; viewDy = 0; aspect = 2560 / screen.height; } } KNEEBOARD = { x = 0; y = 0; width = 526; height = 789; } ------------ -- for A-10C ------------ function reconfigure_for_unit(unit_type) if unit_type == "A-10C" then LEFT_MFCD = { x = 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } RIGHT_MFCD = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } else LEFT_MFCD = nil -- remove for others RIGHT_MFCD = nil -- remove for others end end ------------ -- for Ka-50 ------------ SHKVAL_SCREEN = { x = 2560; y = 0 + 360; width = 980; height = 817; -- must be this height to hide splash screen } ABRIS_SCREEN = { x = 2560 + 980; y = 0 + 360; width = 940; height = 1080; } -------------- -- for M-2000C -------------- MIRAGE_RADAR = { x = 2560; y = -100 + 360; width = 1920 / 2; height = 1080; } MIRAGE_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } COM = { x = 1920 / 2 + 2560; y = 0 + 360; width = 120; height = 70; } ECM_CHF = { x = 1920 / 2 + 2560; y = 610 + 360; width = 75; height = 40; } ECM_FLR = { x = 1920 / 2 + 2560; y = 650 + 360; width = 75; height = 40; } PCA_UR = { x = 2560; y = 980 + 360; width = 500; height = 50; } PCA_BR = { x = 2560; y = 1030 + 360; width = 500; height = 50; } PPA = { x = 1920 / 2 + 2560; y = 810 + 360; width = 70; height = 90; } PCN_UR = { x = 2560 + 1920 - 700; y = 1080 - 120 + 360; width = 500; height = 60; } PCN_BR = { x = 2560 + 1920 - 700; y = 1080 - 60 + 360; width = 250; height = 60; } FUEL = { x = 2560 + 1920 - 80; y = 0 + 360; width = 80; height = 45; } -------------- -- for Mig-21 -------------- MIG21_RADAR = { x = screen.width / 2; y = 0 + 360; width = 1080; height = 1080; } -------------- -- for F-5E -------------- AN_APQ159_RADAR = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1080; height = 1080; } AN_ALR87_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } UIMainView = Viewports.Center But with this the F-18C is no longer having a problem but the A-10C is also not exporting. Am I putting this code in the correct location? I am a bit of a .lua n00b and only managed to get this far with it by trial and error. ;) I am afraid I will need detailed instructions on how to do this... Also, what is the unit_type for the Harrier as I think it also uses LEFT_MFCD and RIGHT_MFCD. Thanks! --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars Link to comment Share on other sites More sharing options...
sreventon Posted June 12, 2018 Share Posted June 12, 2018 See my reply here https://forums.eagle.ru/showthread.php?p=3528626 Link to comment Share on other sites More sharing options...
Maulkin Posted June 13, 2018 Author Share Posted June 13, 2018 See my reply here https://forums.eagle.ru/showthread.php?p=3528626 HEY!! Thanks sreventon! Just by moving those lines of code around I am now getting the left and right DDI's exported to the second monitor, and more importantly, the DDI's in-cockpit are able to display as well. However there appears to be a bit of weirdness going on with the exported video: --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars Link to comment Share on other sites More sharing options...
sreventon Posted June 13, 2018 Share Posted June 13, 2018 HEY!! Thanks sreventon! Just by moving those lines of code around I am now getting the left and right DDI's exported to the second monitor, and more importantly, the DDI's in-cockpit are able to display as well. However there appears to be a bit of weirdness going on with the exported video: There is one temporary fix for this problem IF you are not overlaying the viewports. Change "shaderLineDrawAsWire" to "true" in "MDI_init.lua", which would make the viewports exported looks better when having a black background but not so much if overlaying. This would also mess a bit on the original display (fonts become thinner), but you wont be looking at them once you got the exported display right? Use this at your own preference. Link to comment Share on other sites More sharing options...
splash Posted June 13, 2018 Share Posted June 13, 2018 Does anyone can post a working monitor.lua in which works function reconfigure_for_unit(unit_type)? I tried several variations based upon the original but it won't work. Link to comment Share on other sites More sharing options...
Recommended Posts