jonsky7

Glad you got it sorted

I personally ran the config file I named spencer.lua on my machine and it worked as intended, did you try that specific file? From your options file it says ["multiMonitorSetup"] = "new screen mfd under", Which is the filename of the config file you are currently using. Which is not the one I made for you obviously. Resolution from your options looks fine. I would perhaps turn off DLSS upscaling until we have it working, just a thought. I see you are using the launcher, have you verified any changes made in the settings menu of the game? To be clear, I mean the actual game menu screen. Little cog wheel on the top left? (sorry if I'm teaching you how to suck eggs here) null Have you tried just renaming your entire DCS Saved Games folder? DCS will make a new one on launch, you will have to set the resolution and config file again. This will ensure nothing else in the saved games folder is interfering with it. Once established working, you can copy files from the renamed folder across to the newly created one, and see if the problem re-appears. I have to ask, have you checked the display settings in windows? Does your setup work as intended while at the desktop? You can open something like file explorer and drag it onto the lower screen etc? From your earlier screenshot, the lower screen does NOT look stereoscopic to me, just a duplicate. In a stereoscopic image there is a difference in perspective to generate images for your left and right eye. I looked at the joystick against the map, they look identical to me.

Looks like imgur has decided to just block traffic from the UK rather than deal with our OSA bull<profanity>. https://www.bbc.co.uk/news/articles/c4gzxv5gy3qo Get yourself a VPN or TOR browser (not too clued up on its safety aspects) to work around it.

That took an age to find lol, I have no idea how it's giving you your result though. Syntax errors usual mean the config is not selectable in the settings menu. spencer.lua <<<-- I have tested this actual file, it worked It will be named Spencer in the options. I thought I'm missing something, so I just started from scratch. Then comparing the two, I noticed it.

In that config file, your MFD are set in the viewports section, and a few other little errors. Should be

I've just seen your reply, but thought I'd post anyway, glad you got it sorted, though I have no idea what a displayport dummy is What about setting your Left monitor as main for a test? DCS really likes the left and upper most monitor to be the main, I added a display table to the config file that is supposed to fix that, but it obviously hasn't Try running with Full Screen off too, I personally don't see a difference in frame rate between them. Delete these files/folders, DCS will rebuild them on start C:\users\*yourname*\appdata\local\temp\DCS Saved games\DCS\metashaders2 Saved games\DCS\fxo Saved games\DCS\config\appSettings I also made a couple of mistakes in the files, resolution wise, fixed them here Veen-3 screen-1 Camera.lua Veen-3 screen-3 Cameras.lua

You have two options when running 3 monitors You can either: 1. Use all 3 monitors to effectively make one large wide display. All 3 screens will show a forward facing view which equates to a large Field of Vision (FoV) or 2. Have a 90deg Left view, a Centre View, and a 90deg Right view. I am assuming from your pictures, that your centre monitor is your "WINDOWS MAIN DISPLAY" and the left and right monitors are set to "EXTEND DESKTOP TO THIS DISPLAY", these are set in the Windows display settings. You now have to make another choice, do you wish to keep the centre monitor as your main display, or could you live with the LEFT monitor being your main display. The simplest method of getting DCS to do either option 1 or 2 is to set your "MAIN DISPLAY" as the left monitor. Then Option 1 - Select "1Camera" in the DCS settings and set your resolution as 7680x1440 Option 2 - Select "3Cameras" in the DCS settings and set your resolution as 7680x1440 If you want to keep your centre monitor as your MAIN DISPLAY then; Option 1 - Use this monitor config file Veen-3 screen-1 Camera.lua , in the DCS settings and set your resolution as 7680x1440 Option 2 - Use this monitor config file Veen-3 screen-3 Cameras.lua , in the DCS settings and set your resolution as 7680x1440 Save the files in SAVED GAMES > DCS WORLD > CONFIG > Monitorsetup For 3 screens x 3 Cameras, you can alter the left and right view by adjusting the values of "viewDx" where 0 is straight ahead, a value of -1 is left 90Deg, and 1 is right 90Deg. So 45 degrees, or a forward-left view would be -0.5, but it doesn't work very well as a FWD-LEFT view duplicates parts of the cockpit, there is no way currently that I know of to align it.

I modified the files so that it is the co-pilot displays being exported. The Pilot displays function as normal, and you can still export. Set co-pilot screens to same as pilot, or have different info.

Exporting the RWR requires file mods, which does not pass integrity check on servers requiring "Pure Scripts" Helios can modify the file, or you can do it manually. I would send you the modified file but I'm not at home for a week or so.

Some things to try. 1. Did you try the config file I gave you in your other topic, the one with the displays table? 2. You do not need Helios for what you are trying to do, DCS will do that. We will need to modify the file for the RWR export, but let us see if we can get it working first. 3. You DO NOT need "Display Fusion" for what you are trying to do with DCS, turn it off or un-install it. Just Spacedesk for the iPad to work as another monitor. 4. Try moving your screens around in windows display settings, try these Enter resolution in DCS Main Settings = 5888x1536 Config file >>>>> 4wide.lua OR Enter resolution in DCS Main Settings = 3968x2160 Config file >>>>>4Z.lua 5. You pasted this above -- UIMainView = Viewports.Center UIMainView = { Gx = 0; <<<<<<<<<<<<<<<<<<<<<<<<<<<< ERROR, delete the G y = 0; width = 1920; height = 1080; }

I'm guessing that's an issue with the software, or at least the compatibility of the software that you are using to run the iPad as a monitor. The easiest solution would be to buy another actual monitor. That's entirely up to you though. Sorry i can't be of any further help.

I dont own the Kiowa so I cant say, sorry

So, If I select "Single Screen" as my monitor config, and go into ALT-F1-HUD view, MFDs also show. The F-18s shows 3 MFDs along the bottom, and they take up half the screen. Is this what you want to resize/relocate? ok, I've had a look at the F-18 some more Without any exports in in the monitor.cfg file I get By changing values in DCS World\Mods\Aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\AMPCD\Indicator\AMPCD_viewport_cfg.lua 4 sets of numbers, same order as monitor.cfg files {x-pos, y-pos, width, height} It now looks like This does not look the same for all aircraft it seems, or even displays in the same aircraft. I can't see anything obvious to change size and position of the Left and Right MFDs??? Something to look into maybe?

Hello again, Due to the ongoing bug with the CH47 Chinook CDU where the screen goes blank while trying to access certain pages, or the page doesn't change, I have modified how the waypoints are entered. I have removed the ACP entries, so now the LAT/LON coordinates are entered directly into the FLPN/ALTN FPLN pages. I believe this solves an issue that can pop up when two or more ACPs are entered with the same name, i.e. when you create a new list of waypoints in "TheWay". If ACP 1 already existed, and a new ACP called 1 was entered, when the ACP 1 was being entered into the FLPN, the user would have to select which ACP 1 was to be used. There is no way for "TheWay" to see the "new" Waypoint selection screen, so it could get out of sync with DCS and create INPUT ERRORS. This new method also speeds up the creation of a FLPN, as it doesn't have to create the ACPs first. It seems that the underlying CDU systems are working as they should, and it is only the CDU display output that is bugged. So you are still able to create new, and add to existing, ALTN FPLNs. (the display just doesn't follow along when data is entered) The ALTN FPLN summary is still updated, and the route can be shown on the HSD by enabling it. https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.9 Cheers Jon

WhaaaaaaaAAAAAAAAT!! Still not fixed?

Doesn't seem to be much wrong there, but you can try this one F18_4-screens_v2.lua I have created a displays table, based on your display settings above (4 screens now?) which tells DCS which screens to use and where they are. You CAN NOT run in fullscreen mode and keep DCS open while reading a PDF, that is a Windows "feature" and nothing to do with DCS, just run in windowed mode (fullscreen off) I don't think it makes a difference anyway when running multiple monitors.

What is your current monitor config file? And where are your monitors positioned in windows display settings? And what resolutions are they?

Thank you both, much appreciated! Yes, I had trouble with that too. It can work fine multiple times, then it doesn't. I haven't checked it for a while though, maybe something broke.

Really disappointed that the CDU going blank didn't get fixed for today's update either (23 Jul 25)

Yes, you can not manually enter a resolution in the DCS Launcher, start the game and use the settings menu.

Seems fine to me at the moment

I wouldnt say I took over development exactly. I couldn't have made this from scratch as I don't have the knowledge. However, I have been able to add a couple of aircraft, and make some minor mods and fixes. I have also taken some other people's mods for theWay and combined them into one. I thought they made good additions, after testing and minor modifications, I thought I would share it here. There are some fixes in "my branch" that will not be in the official branch, F16 DED entry being one of them.

Sorry to hear that it wiped your keybinds. I use the Quaggles input command injector. You can make modifications in a separate file and it leaves the default keybindings files alone. Added benefit is that there is no need to modify the default files each update.

The 'name' and the 'category' can be anything you like, they are just what shows up in the controls menu, first and second columns. You weren't far away though. In the clickable data you have the device name, devices.APN_209, and also there's reference to the buttons. The low setting was easier device_commands.Button_2 But the high setting said buttons 1, and 3, I just had to test them. There was also some reference to some values, 0, 0.1, 1 IIRC. Button 1 is the push to test on the HI Knob. Like I mentioned, for a rotary encoder, you might have to change them to 'down' rather than 'pressed'.

Well you're not wrong {pressed = device_commands.Button_2, up = device_commands.Button_2, value_pressed = 0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT LO SET DOWN'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_2, up = device_commands.Button_2, value_pressed = -0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT LO SET UP'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_3, up = device_commands.Button_3, value_pressed = 0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT HI SET DOWN'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_3, up = device_commands.Button_3, value_pressed = -0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT HI SET UP'), category = {_("RAD ALT")}}, You can adjust the values in the part value_pressed = 0.01 value_pressed = -0.01 0.05 seemed too fast to me, but 0.01 may be a little slow. Maybe 0.02 would be good. Copy into both keyboard and joystick "default.lua" files. "Pressed" means the action will be repeated as long as the key/button is held down or you could change that to {down = device_commands.Button_2, up = device_commands.Button_2, value_down = 0.01, value_up = 0 (probably better for a rotary encoder) if you want to move the setting a certain amount each key press, like the notch in the mouse wheel Regards Jon.