Search the Community

I managed to scrounge up information from various scattered forum posts a while ago to make this monitor config a while ago, which currently has no issues working: However, I recently got 2 more MFD screens, but when I tried to add them to my monitor config file the main menu now stretches across all the MFDs, is there something I missed? Was hoping there would be some centralized up to date area where I can find out what I need to edit. EDIT: I plugged the code into copilot and it managed to pull the answer out of the ether for me, here it is in case it helps anyone.

Can we please get the MFD exports added to the white list on IC check. using a home cockpit with exports used to be easy and would allow me to us the cockpit that I've built in any server that I wanted to. However the IC Check now causes more kicks and frustration than does anything to help the "Fairness" on servers because someone has something different in the cockpit files. With the popularity of Helios and the availability of MFD's that we've seen in the last couple of years for home cockpits, this should be addressed and made so that its not as frustrating to get onto multiplayer servers.

It would be helpful to have a built in tool rather than LUA manipulation and the FPS issues associated with trying to get exports onto a 2nd screen with medium grade gpu's (Currently have a 1070ti). Currently I have been using Helios to run a virtual cockpit while I fly and have done the usual steps to get the MFD's and what not exported to my 2nd screen. However I feel that there is a definite FPS hit to my setup from having to have a resolution of 2560x2520 (Main screen is a 32" 1440p screen and cockpit is run on 24" 1080P touch screen). It would be helpful to have a baked in way to handle exporting Cockpit MFD's and other scopes (radar, RWR in Particular) that would not have a huge hit on FPS especially given the scarcity of higher end equipment as of recent. I know that MFCD existed but that program hasn't been updated or supported in some time and so there is no other options than the current LUA manipulation method.

I downloaded IHOPI's Display Export App. Its a server executable, and an APP that goes on your ipad/tablet/phone/etc. It worked fine for a few days. I could use my A10c2's CDU on my tablet. (also TADs and the Lightning Pod... pretty cool) Today, The Server Program.. loads, completes its checklist, then just shuts off. Disappears. No error pop-up. Nothing. In Game.. the A10's Displays are blank. All the switches are on. Nothings displayed. Ive reached out to his channel here. Is there anything i can do, to reset my game? Reset MFD exporting? Any Ideas, where to look and do? Thanks (picture: Missing Display Data. 2nd screen (blank) where the data is exported from)

I've got a lua script set up to display the main viewport on one monitor, and two MFDs (and apache TEDAC) on a second monitor. I use the same script in the apache, Ka-50, F-16 and F/A-18 the MFDs all appear in the monitor in the correct place. When I switch to the AV8B harrier, the MFD displays do not show up in the F1 cockpit view, but do display when I switch to the F2 external view, and disappear when I switch back to the F1 view. The script uses the generic LEFT_MFCD and RIGHT_MFCD identifiers as they seem to work in the modules listed above. _ = function(p) return p; end; name = _('AH-64D Apache CPG Dual Monitor: m1 - Viewport, m2 - MFDs, TEDAC (equal)'); Description = 'dual monitor: viewport on main 2560 x 1080 (21:9 aspect ratio), MFDs and TEDAC on second monitor: 1680 x 1050 (16/10 aspect ratio) bottom aligned' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1080; viewDx = 0; viewDy = 0; aspect = 21/9; } } LEFT_MFCD = { x = 2560; y = 30; width = 554; height = 554; } RIGHT_MFCD = { x = 3668; y = 30; width = 554; height = 554; } TEDAC = { x = 3114; y = 30; width = 554; height = 554; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Is it a case of using specific IDs for the AV8b displays instead of the generic IDs, or is just a weird bug with the harrier?

Exported MFD to a secondary monitor are nearly unuseable with the F-18 because they are way too dark (Monitor Brightness is already set to max) Exported MFDs from the F-16 are bright and readable. It's a long standing problem, but is there a fix incoming?

I know there is a lot of talk about homemade MFD setups. I found one video in particular where the guy connects a lilliput USB monitor to his setup. What is appealing about this is that my Graphics card has just two outputs (well three if you include VGA). So I cannot have 3 separate outputs for DDIs and then one for the main screen. A USB monitor fits my setup best. My question is, in the video below the guy says the screens have a USB input as well so the MFD Cougar can plug into the screen and both output/connect to the PC through the Lilliput USB cable. However, I have seen nothing in the description of the Lilliputs that confirms that they have a USB input. Does anyone know? I suppose I could connect both separately to the PC but his setup looks so streamlined. Anyone know anything about these screens?

MFD export effect before 2.8.3.37854.1 Open Beta update: After the update: My MonitorSetup: _ = function(p) return p; end; name = _('3440MFD+'); Description = '3440*1440' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 790; y = 410; width = 620; height = 620; } RIGHT_MFCD = { x = 2030; y = 410; width = 620; height = 620; } --[[ CENTER_MFCD = { x = 1565; y = 100; width = 310; height = 310; } ]] JF17_LEFT_MFCD = { x = 350; y = 0; width = 620; height = 930; } JF17_CENTER_MFCD = { x = 2820; y = 0; width = 620; height = 930; } F14_TID = { x = 2030; y = 410; width = 620; height = 620; } GU_MAIN_VIEWPORT = Viewports.Center Previously I can see thru the MFDs on my screen and get a very clean view on the outside while don't have to lower my head and zoom in to see the MFDs, this can be a great help to enjoy flying and operating avionics at the same time, since you can choose a position you like to place the MFDs and read the information on them more confortably. Its for the same reason that some people buy a external screen and export MFD on it. building a monitor setup on the screen is just like building a cabin with many external screen at home, the only difference is one is virual and cheaper, the other is solid and obviously more costy. This should not be canceled just because of "simulation", it's player's freedom to display their MFDs wherever they like without obstucting the main view.

MFD export effect before 2.8.3.37854.1 Open Beta update: After the update: My MonitorSetup: _ = function(p) return p; end; name = _('3440MFD+'); Description = '3440*1440' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 790; y = 410; width = 620; height = 620; } RIGHT_MFCD = { x = 2030; y = 410; width = 620; height = 620; } --[[ CENTER_MFCD = { x = 1565; y = 100; width = 310; height = 310; } ]] JF17_LEFT_MFCD = { x = 350; y = 0; width = 620; height = 930; } JF17_CENTER_MFCD = { x = 2820; y = 0; width = 620; height = 930; } F14_TID = { x = 2030; y = 410; width = 620; height = 620; } GU_MAIN_VIEWPORT = Viewports.Center Previously I can see thru the MFDs on my screen and get a very clean view on the outside while don't have to lower my head and zoom in to see the MFDs, this can be a great help to enjoy flying and operating avionics at the same time, since you can choose a position you like to place the MFDs and read the information on them more confortably. Its for the same reason that some people buy a external screen and export MFD on it. building a monitor setup on the screen is just like building a cabin with many external screen at home, the only difference is one is virual and cheaper, the other is solid and obviously more costy. This should not be canceled just because of "simulation", it's player's freedom to display their MFDs wherever they like without obstucting the main view.

Good afternoon! Just did the first lesson, thanks for this incredible aircraft. I was wondering if I missed something, but I didn't get any image on my external MFDs. Most modules just "get them" based on the DCS configuration I have. But some, like the F-14 need some extra work. Could you please point me in the right direction? Thanks, best regards, Rafa.