jonsky7

If you launch into the game and go the settings menu, you can manually type a resolution into the box, can't do this in the launcher for some reason. You will need to enter 3840x (2160+small screen height in pixels), you haven't given the resolution of your smaller displays unfortunately. You might also have to turn off "full screen" mode for your windows monitor to not turn black.

I've made a few changes bringing it in line with the description that was found in one of the original config files. Not sure if FC3 was a usable unit type, so added them separately for each aircraft. Removed the duplicate entries for the Mirage F1 exports. On a side note, the whole point of the configure for unit type was so you didn't have to modify the export names for any default exportable display. Most of your aircraft have mods applied for the RWR etc, so it's a bit redundant. Helios2.lua Give a try I suppose, there wasn't anything glaringly obvious, name in settings menu = Helios2 When I asked ChatGPT to compare it said: Helios2.lua is now better written, more efficient, and easier to maintain than the original Helios.lua. With additional comments and modularization, it could be even more user-friendly and robust. edit: error in the above file at line 128, corrected below Helios3.lua

Can we see the config file please?

I believe the RTX3060 only supports 2x8K displays, or a maximum of four displays, but at lower resolution.

Hmmm, I haven't been able to try this yet, but I wonder if putting a displays table in the monitor config file would prevent this. Example The displays table is a list of all your monitors, the reference point is your windows main display. My setup above is a fairly straight forward 3 monitor setup, two 1440p monitors, and a 1080p monitor, laid out from left to right. Let me know if you need assistance writing a displays table.

I do occasionally get this if my displays go to sleep, and when they wake up it is all squished. I have no idea why my monitors go to sleep when running DCS as I have that switched off in power options. Nothing seems to work for me either, other than restarting the game. Sorry to not be able to offer a solution at this time.

I watched a setup video to try and understand what is going on. The following is based on the assumption that your "folds" are vertical and equally spaced on your main screen, which is the view from the pilot seat: There seems to be a setting in the app that chooses between 3 screen setup and single screen, have you perhaps chosen the 3 screen setup? This setting may refer to the Main view (or cockpit view), and not the actual number of screens you have in your setup. DCS has two default settings Single screen, which is one view looking forward out of the cockpit, 3 screen has a left view, forward view, and a right view. I think the app is asking which one of these you want, and then it writes a DCS monitor config file for you. I can see where this may be a bit confusing. You could think of it as asking do you want a single view, or three views. DCS doesn't really care how many actual monitors you have. It treats all of your monitors as one large display area, and the config file tells it where to place various "views" in that display area. So it will squash the "3 Views" onto one monitor if you, or the app, tells it to. If this doesn't help, let us know and we can try something else.

I don't have WinWing displays. Do they show up in Windows Display Settings like normal monitors do?

Found out these are Civ. Traffic related. Don't show when off, from low to high they all follow the same path, with decreasing gap between tugs as you increase the level of civ traffic.

Now there's two lines of tug boats tugs.trk

Well i would have thought you'd get a wider field of view. It's at least worth a try isn't it?

Yeahhhhhh, that's not very good at all. Totally understand your frustration, was just trying to help. How does the 1 camera setup look, but with the resolution adjusted to include all 3 monitors?

Not sure if you are aware or not, but the view is adjustable, but not in the settings menu. You have to do that in the configuration file. This is the default 3 camera config file, DCS > Config > Monitorsetup > 3Cameras.lua If you are going to make adjustments, I suggest you copy the file to Saved Games > DCS > Config > Monitorsetup > *name the file something different* Also change the name inside the file, below it is called 3 Screen To adjust the left/right angle, adjust the values of viewDx, negative values for left, positive for right, -1 = left 90deg, 1 = right 90deg To adjust up/down, adjust the value of viewDy, negative values for down, positive for up, -1 = down 90deg, 1 = up 90deg 1 degree = 0.011112 30 deg = 0.33333 45 deg = 0.5 You can also run 3 screens with the 1 camera file, this should give you a wide forward view To do that, just adjust the resolution in the DCS settings menu to cover all 3 of your monitors i.e. 11520x3184

If you upload the file I can take a look. Just to be sure, you said F-14_TDI but it should be F14_TDI No hyphen (dash) in F14 and is that in the core directory, or your saved games folder? It won't change on updates if you save the config file in the saved games folder Saved Games > DCS > Config > Monitorsetup > your config file.

I've not changed the names and mine is still working Did you use my guide to do your setup, or did you use Helios? Notepad++ Search Find in files Search for try_find_assigned_viewport(" filter *.lua Point it at your game directory.

ED have made some changes to the clickable data file for the Chinook, mainly all of the button codes for the CDU's have changed. Update can be found: https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.7

I've updated both the Quaggles and Mod files to reflect the changes in the clickabledata.lua button renumbering (WTF?). Sorry for any inconvenience. with Thanks to @digitego

Thanks for the info.

Updated for DCS 2.9.10.3948, not sure if anything has changed, but just in case the CDU and MFD keybinds have been added to the latest CH-47F Input files. CH-47F Keybinds V4.1.zip Mod manager ready

After using Razbam's F-15E Terrain Following Radar, I couldn't help but think that this would be a fantastic addition to the AI Mosquitos and the AI flight model in general. At the moment it seems the AI (certainly for the Mossie) is set to fly no lower than 150-200ft whereas there are reports of Mosquito's carrying out bombing raids as low as 30-50ft. Obviously WW2 aircraft don't have TFR, but whatever the process is to recreate it would be a welcome addition.

Excellent! You are very welcome, I appreciate your appreciation

I don't think SRS is fully integrated with the Chinook at the moment, one of the radios work, for the others you have to use the SRS Overlay for tuning etc.

The AC Generators are connected to the Rotor Transmission and not the engines, the same as the Mi-8, so the rotors need to be at 86% or more for the generators to come online.

Here is my Input folder, from DCS > Mods > aircraft > CH-47F Input.zip The main controls has this section Line 968 onwards and the gunners section has Line 85 The only other thing I can think of is if you are not using English as the language for DCS (I've never had to change it so I'm unfamiliar), I've seen at least one other post where a keybind was hard to find due to translation. From your screenshot it looks like you are using English, but I thought I'd mention it anyway. And just some info: If you modify any game files at any time, and then do an update or repair, all of those files are saved in the main directory in a new folder called Backup.000, and they are saved with the folder structure intact, so you can just drag the contents of BackUp.000 back into your main DCS folder to restore all your Mods. A mod manager is much better though, for when the files can changed (can break stuff) More info. The files and folder for the Crew Indicator are located DCS > Mods > aircraft > GCBase > Cockpit > Scripts > AI > ControlPanel and the location is in the file g_panel_page.lua It is extremely similar to the Huey's Crew Indicator file. To change it's position I mess with Line 62 base.init_pos = {aspect + shift_X,firstLineY + shift_Y} Mine being base.init_pos = {aspect + shift_X - 5.2,firstLineY + shift_Y + 1.6} Hope any of this helps.

I have exactly the same name in the main controls window null