jonsky7

Pretty sure I fixed mine by adding the GU_MAIN_VIEWPORT entry to the end of the config file. Give it the same parameters as your main screen. You can see an example on page 1 where I describe the sections of the monitor config file.

Baraon has just beat me to it while I was doing some testing. As Baron has said, it doesn't seem possible to run the game using a lower resolution while also utilising a multi-monitor configuration. Changing the center viewpoint settings only seems to make the picture smaller on the screen, and checking fullscreen has no effect. So as Baron has pointed out, the only way to do this is to first change the resolution in Windows display settings, you will then have to reconfigure your monitor config file to place MFCDs etc according the new resolution.

There isn't any notifications for most keyboard commands. Best you can do is turn the cockpit sounds up and reduce all other sounds a bit, adjust volume as desired. That way you'll be able to hear cockpit switches being activated on keypress.

I've just had a look at the T-45 mod for you and the export names are:- MFDL MFDR So you need to put entries in your monitor config file with reference to above. (see below) Alternatively, you could change those names to LEFT_MFCD and RIGHT_MFCD and then they will export into the same positions as the A10, F18 etc. In the files VNAO_T45\Cockpit\Scripts\Displays\MFDL\Indicator\init.lua ----> try_find_assigned_viewport("MFDL") to try_find_assigned_viewport("LEFT_MFCD") and VNAO_T45\Cockpit\Scripts\Displays\MFDR\Indicator\init.lua ----> try_find_assigned_viewport("MFDR") to try_find_assigned_viewport("RIGHT_MFCD") eg LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } MFDL = { x = 5130; y = 360; width = 825; height = 825; } MFDR = { x = 2560; y = 360; width = 1720; height = 1080; } It works but they don't look great, going to need a bit of modifying the code for the font I reckon

I've just had a look and the export names are MFDL MFDR So you need to put entries in your monitor config file with reference to above. (see below) Alternatively, you could change those names to LEFT_MFCD and RIGHT_MFCD In the files VNAO_T45\Cockpit\Scripts\Displays\MFDL\Indicator\init.lua ----> try_find_assigned_viewport("MFDL") and VNAO_T45\Cockpit\Scripts\Displays\MFDR\Indicator\init.lua ----> try_find_assigned_viewport("MFDR") eg LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } MFDL = { x = 5130; y = 360; width = 825; height = 825; } MFDR = { x = 2560; y = 360; width = 1720; height = 1080; } It works but they don't look great, going to need a bit of modifying the code for the font I reckon

I appreciate you taking the time to leave a thank you note, cheers

You'll get a resolution of 6400x2160 in DCS

If I remember correctly, you can highlight the monitor in windows display settings and use the arrow keys to move it around a bit more accurately. You might have to hold CTRL for the arrow keys to work. Been a while since I had to do it.

That's down to the monitors 1 and 2 not being perfectly aligned on the bottom edge with monitor 3. That's why you're getting a resolution option of 2167. One or both of the monitors is 7 pixels below the bottom edge of monitor 3. On windows display settings screen. Move monitor 3 up and down as well as trying 1 and 2 to get them lined up perfectly. Or just choose the 2167 resolution in DCS, that should get rid of the desktop showing on the bottom edge.

https://m.twitch.tv/videos/1897761024 BoB flight starts at 1:25:40 Looks and sounds fabulous

I have no idea how to export that display using a mega2560, but I have another solution. If you can use your 3.5inch TFT as a regular windows display, then you can export the CMWS display with a little modification to the .lua files of the Apache. If you go to the file DCS World\Mods\aircraft\AH-64D\Cockpit\Scripts\ASE\CMWS\CMWS_init.lua and add these two lines to the bottom of the code dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("CMWS") Then you can export the CMWS in the same way as exporting a MFCD using the monitor config file. Where you would have an entry in your monitor config file like CMWS = { x = 2560; y = 0; width = 300; height = 200; }

The bomblets don't seem to necessarily explode the tanks like they do in DCS, but disable them, maybe? The only difference between the CBU-97 and CBU-105 is that the 105 has a guidance kit on the main weapon cannister, all of the internals are the same. Like the difference between a MK-82 bomb and a GBU-38 Looks pretty effective to me

Are the sound files encrypted? I don't own the F-15E but the AV8B and M-2000 don't have encrypted sounds. If not, just go in to the sdef for the ECS and reduce the gain number. And if you put that modified file in your saved games folder, it shouldn't upset integrity checks. Just a thought.

If they would all just give them a unique name and default name we could choose either or. eg turn try_find_assigned_viewport("LEFT_MFCD") into try_find_assigned_viewport("WSO_LEFT_MFCD", "LEFT_MFCD") Then if you make an entry in your config file for WSO_LEFT_MFCD, that would take priority over LEFT_MFCD Several modules already follow this approach so it's not something new, and would take a few moments to implement. The Ka50 does it with the ABRIS and Shkval try_find_assigned_viewport("ABRIS","RIGHT_MFCD") try_find_assigned_viewport("Shkval","LEFT_MFCD") The JF-17 does it with all its displays try_find_assigned_viewport('JF17_LEFT_MFCD', 'LEFT_MFCD') and the Apache does it with the TEDAC, albeit slightly differently if not try_find_assigned_viewport("TEDAC") then try_find_assigned_viewport("CENTER_MFCD") end

Wouldn't it just be easier to put the front seat CENTER_MFCD in the same position as a rear seat OUTER_MFCD?

Depends on if you're concerned about the integrity check or not for servers running the option require pure scripts = true I do not currently own the F-15E, but you may be able to modify the names of the exports and then you could create separate entries for all 7 screens in the config file. You can use notepad++ to search within files. Under search, Find in files Run a search for LEFT_MFCD and RIGHT_MFCD, you'll find entries along the lines of try_find_assigned_viewport("LEFT_MFCD") It will then depend how they are managing the switching of the displays. The Apache has only one entry for LEFT and RIGHT MFCD's and I'm not good enough with the code to figure out how the switching takes place and whether or not that could be used in the monitor config file.

I'll be honest and say I don't fully understand your question, but have you tried the viewDy offset in the monitor config file? Adjusting the viewDy value adjusts the view up and down, but I have no idea how that effects the position of the HUD. viewDX will adjust the position left and right. These values would normally be used to line up multi-displays so the horizon/cockpit lined up correctly.

The UIMainView defines where the following are placed The Game main menu The F10 Map Mission Editor The boundaries of the Comms Menu (Right) and subtitles (left) GU_MAIN_VIEWPORT I've only found The gunner reticle in combined arms tanks etc

You have the right file. To be honest with you it has been a long time since I made this change, so I don't exactly remember how the number changed the location but... line 18 local aspect = LockOn_Options.screen.aspect I changed that to local aspect = -1.34 I think making it more negative moves it left.

They look amazing!

It's not really a problem until you try to play on a server that has the Require Pure Scripts = true option set.

You can use the switched condition to add and remove the radio menu items as part of coalition moves in and out of the zone. In the below example, there are two target areas. Four trucks start out of both zones, and there are no available radio messages. 2 trucks head towards the zones, 2 lead trucks, and 2 trailing behind. Once the lead trucks reach the zones, two radio items are available in the F10-Other. They are displayed in the order they are created. I then destroyed the two lead trucks, radio items are removed Once the trailing trucks reach the zone, the radio items come back. radio trigger.miz Sorry if I'm teaching you how to suck eggs here. Best I can do. As for target types, all I can think of is setting multiple message triggers that have several conditions for activation. eg Part of coalition in zone 1 enables Radio item 1 selecting Radio item 1 sets flag 1 to 1(true) Message trigger conditions = Flag 1 is 1 and unit/group 1 is in zone (unit 1 is a truck) Message to send - truck spotted in area 1 Message trigger conditions = Flag 1 is 1 and unit/group 2 is in zone (unit 2 is a Smerch) Message to send - Smerch spotted in area 1 That is going to take forever to set up though.

Ikarus doesn't do displays, only gauges. But you can do a bit of modding to make DCS export the screen, it is only the screen mind you. The mod folder below allows the export of the following, define a location in your monitor config file for the ones you want to export. ARC_210 RWR A10C_CMSP A10C2 exports.zip These mod files will not pass integrity check on servers running "pure script = true" option, but otherwise they are fine to use in multiplayer.

For exporting MFCDs see, it's a bit of a read mind, but I've had good feedback when the steps are followed. By default, only the MFCD and EHSI are exportable, but you can export the DED, RWR, and CMDS counters. However, this part modifies game files and will break the integrity check for servers running the "pure scripts = true" option. Here's the modded files required to export the RWR, CMDS counter panel, and DED For your monitor config file they are called F16_RWR F16_CMDS DED F16 display exports.zip

Looks like the "chase" or "formation camera", possibly LCTRL+F4