jonsky7

To the Devs Would it be possible to implement the 0.5 second delay when activating the trimmer like the Huey has please? Thanks

So I've had an idea but I can't test it because I don't know how to implement it. When flying helicopters in DCS with consumer level self-centering non FFB joysticks we have to live with some drawbacks compared to helicopters in real life. Mainly that once trimmed, you lose the ability to fully deflect the cyclic, which I assume is not the case in a real helicopter. For example, flying the Huey in fast forward flight requires a lot of forward cyclic input, so you hit the force trim and the cyclic is held forward which is great. But now when you pull full aft on your joystick, the in game cyclic only moves slight aft of the centre position and not all the way back. Same for left and right. I know that on the large airliners I work on, aileron trim adjusts the centering cam position of the control wheel, and it will sit on a tilt, but you can still fully turn the wheel in either direction. What I thought might work is to be able to over saturate the axis in much the same way as we can under saturate them now, so you could move the slider to 150% or whatever. This would obviously mean that the in game cyclic stick would reach its limit before you hit the travel stop of your actual on desk joystick, it would however enable full deflection of the cyclic when force trim is applied. Is there a lua file I could edit to test it?

Hi, When flying the helicopters in DCS, there's a limitation where once you've clicked the force trimmer you may not be able to achieve full deflection in all directions. This is obviously a limitation with self-centering non FFB joysticks and flying helicopters in games. For example, fast forward flight in the Huey needs quite a lot of forward stick input, so you press the trimmer and the new centre is created. But this now means that when you pull full back on the joystick, the in game cyclic stick is only slight aft of it's actual centre position and so you lose some control authority. As helicopters also usually need some roll trim, you lose some left right authority. What I'm trying to achieve is full control authority independent of trimmer position. One idea is to use "relative axis" to move the joystick position instead of using force trim, but I don't know if it will work, mainly because I don't know if it's possible or even how to do it. any ideas?

You're very welcome, glad you found it useful. That tool is pretty sweet too As for your F18 lua, you can use the same file as your F16, the F18 MPCD is called "CENTER_MFCD" If you want a separate file, Make sure you save it in saved games\DCS\Config\Monitorsetup Make sure it has an individual filename, and make sure the name in the code is unique. Alternatively, what I do, is rename the viewports in their respective lua's, and my monitor config file has separate entries for each aircraft. For example the F16 left MFD is %%%\DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\MFD\indicator\MFD_left_init.lua Near the bottom of the code you will find try_find_assigned_viewport("LEFT_MFCD") and I change it to try_find_assigned_viewport("F16_LEFT_MFCD") I have included my modded files they are OvGME ready and pass integrity check, and my monitor config file if you care to have a look. You will need to modify the co-ordinates to suit you of course. I have another guide for RWR's etc Display Exports.zip

The control panel pops up in the bottom right of the total resolution used, which is not visible to you at the minute because there's no screen there to display it. This also happens with the NS430 pop-up window, and the Mi8 gunner panel. The easiest way to fix it is by moving your monitor "1" to the right corner instead of the left and adjust your viewports as required. Alternatively you can edit the lua file (use notepad++), it passes integrity check too. DCS World\Mods\aircraft\Uh-1H\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua and DCS World\Mods\aircraft\Mi-8TV2\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua line 60 orginal base.init_pos = {aspect + shift_X,firstLineY + shift_Y} for the Huey mine looks like base.init_pos = {aspect + shift_X - 4.6,firstLineY + shift_Y + 1.2} ---{aspect + shift_X,firstLineY + shift_Y} You will have to play around with numbers (-4.6 and +1.2), and I can't fathom out the relationship, I just know that "shift_X - number" makes the indicator go left "shift_X + number" would make it go right but not useful as it already all the way to the right. "shift_Y + number" makes it go up the screen I have included my OvGME ready files, but you will have to adjust the numbers for you! Crew indicator move.zip

I'm experiencing some sound issues in some external views, sounds like a cd skipping. Also, in free camera, the speed in the status bar isn't constant like it used to be, it's bouncing around, just thought I'd mention it as I thought it might be related. Wing or backward view free camera when in motion and "wingman" view seem to be affected. Anyone else or just me? Track file sound bug.trk

Seems a bit off to me, as the option is in the "Gameplay" tab, I would assume it was meant for the player only. If I choose Immortal, I'm not expecting everything else to be immortal with me. Pretty certain it was only the player that was affected previously, not sure when it changed.

Hi, I like to use unlimited ammo now and again. Since 2.7, choosing unlimited ammo now applies to all units not just myself, new feature or bug? Rather liked it just altering my own unit's ammo supply

Very nice!

Personally, I was on a MP server using the Caucasus map. Using CTLD I picked up a HumVee crate at the CTLD spawn point, and dropped it off near a road. I used the set path in the F10 map, first waypoint was near the road close to the initial unpacking point, and the second on the road very near to first waypoint. The third waypoint was far away, maybe 30nm, but on the road also. I was very impressed with the speed the route was mapped out. But then the Humvee started moving and it was nowhere the road, driving across fields and got stuck in a forest. edit: Seems flawless on SP though

It certainly is awful at the minute

Hi, I would like to use the paddle axis as two buttons and and axis. So I have the Paddle acting as an axis and then also a button press at full travel. I would also like a button press as soon as I start to depress the lever. At the moment, using the Edges2 setting in the axes to button section: Button 28 is pressed when the lever is released, button 28 is released as I start to squeeze the paddle, then button 27 presses when the paddle is fully squeezed. I would basically like to invert button 28, so button 28 is pressed as soon as the lever is squeezed, and then button 27 is also pressed when the lever is fully squeezed against the stick. Is this possible? Thanks

Sorry, I don't know how to do that, or even if you can do that. EDIT: The entry UIMainView = Viewports.Center in the monitor config file, declares the position of the User interface. This controls the position of the Main Menu, the mission editor, and also the boundaries of the UI within the cockpit. So if we restrict those boundaries to your centre monitor, the comms messages should stay on your centre monitor too. So we can replace UIMainView = Viewports.Center with UIMainView = { x = 2560; y = 0; width = 2560; height = 1440; } I think these values will be correct for your setup.

There's currently a bug, should be fixed at next update according to this

OK skuzzlebutt Few pointers 1. You're saving in the wrong location, you want to save your config file in Your saved games folder/DCS/Config/monitorsetup 2. Align the left edges of monitor 1 and 3 in windows display settings. 3. Don't count monitor 2 in the resolution calculation if you don't want to use it for dcs. DCS does not like to use monitors that are left of the "main display" set in windows display settings. That may not concern you if you plan to use monitor 2 for Web etc. 4. Check the maximum resolution your graphics card can output. 5. Your DCS resolution will be 3440x2520 6. Try the following config. You must do step 2 for this to have a chance. _ = function(p) return p; end; name = _('custom'); Description = 'main monitor and mfds' Viewports = { Center = { x = 0; y = 0; width = 3440; height = 1440; viewDx = 0; viewDy = 0; aspect = 3440/1440; } } LEFT_MFCD = { x = 10; y = 1440; width = 825; height = 825; } RIGHT_MFCD = { x = 1099; y = 1440; width = 825; height = 825; } GUI = { x = 0; y = 0; width = 3440; height = 1440; } UIMainView = GUI I made the following thread which may be easier to follow.

+1

I don't have a track file at the moment but it seems like the GPS Guided JDAM accuracy is off lately. They will often over fly the target and then try to steer back on themselves, even when in optimum launch parameters, very close to 100 in the AV8 for example. They seem very susceptible to windy conditions which makes the problem worse. Setting a shallower terminal dive angle doesn't seem to make much difference to their trajectory. Cheers

In windows display settings, put your two cubesim monitors under your main monitor Sorry for poor drawing, I'm on my phone. Make sure you align the left and right cubesims to the left and right edges of your main monitor. Then your config file should look like _ = function(p) return p; end; name = _('Gumbie'); Description = 'main monitor and cubesims' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1080; viewDx = 0; viewDy = 0; aspect = 2560/1080; } } LEFT_MFCD = { x = 0; y = 1080; width = 800; height = 600; } RIGHT_MFCD = { x = 1760; y = 1080; width = 800; height = 600; } GUI = { x = 0; y = 0; width = 2560; height = 1080; } UIMainView = GUI The resolution for DCS will be 2560x1680 This should leave your second large monitor free for twitch etc.

Are you changing the "name" of the setup in the lua file, or just changing the filename of the lua file? It is the name in the code that is displayed in DCS settings, not the filename. Also, your monitor config files should be saved in saved games/DCS/Config/monitorsetup. _ = function(p) return p; end; name = _('MYMONITOR'); <<---- THIS LINE Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports =

The maximum digital resolution of the RTX 3080 is 7680x4320 https://www.nvidia.com/en-gb/geforce/graphics-cards/30-series/rtx-3080/#:~:text=1 - 1 - Up to 4k,or HDMI2.1%2BDSC.

How to move "Indicators" Breaks "Pure Scripts" Integrity Check Not quite as easy as positioning exported displays, the position of these indicators is tied to the "total resolution" setting. Which is why they end up in odd places when using a multi-monitor setup. In this section you can find out how to move: 1. Controls Indicator 2. Crew Status Indicator 3. Autopilot Indicators 4. Cargo Indicators Controls Indicators The controls indicator file is normally located DCS > Mods > aircraft > *aircraft name* > Cockpit > Scripts > ControlsIndicator > ControlsIndicator_page.lua *CH-47F file is located in the GCBase folder, not CH-47F folder. In that file search for the line that starts with base.init_pos e.g. Apache Line 153 = base.init_pos = {-aspect + size_w_05 + margin, -(1 - size_h_05 - margin)} The first value (-aspect + size_w_05 + margin) controls the horizontal position. Increasing this value moves the indicator to the right, while decreasing it moves it to the left. The second value (-(1 - size_h_05 - margin)) controls the vertical position. Increasing this value moves the indicator upward, while decreasing it moves it downward. For example, if you want to shift the indicator slightly to the center, up and right from default, you might adjust it as follows: base.init_pos = {-aspect + size_w_05 + margin + 0.1, -(1 - size_h_05 - margin + 0.2)} Mi-8MTV2 The Mi-8MTV2 also has autopilot indicators, they are in the same file as the controls indicator DCS > Mods > aircraft > Mi-8MTV2 > Cockpit > Scripts > ControlsIndicator > ControlsIndicator_page.lua Line 276 = autopilot_base.init_pos = {0,(1 - autopilot_height)} Same method as the controls indicator Crew Status Indicator The Crew Status indicator file is normally located DCS > Mods > aircraft > *aircraft name* > Cockpit > Scripts > AI > ControlPanel > g_panel_page.lua *CH-47F file is located in the GCBase folder, not CH-47F folder. Again, in that file search for the line that starts with base.init_pos Same for the controls indicator above regarding moving the position (CH-47F) Line 62 = base.init_pos = {aspect + shift_X,firstLineY + shift_Y} I changed that to base.init_pos = {aspect + shift_X - 5.2,firstLineY + shift_Y + 1.6} and this moved it a lot left (2 screens), and quite a lot up (from bottom of screen to top) Cargo Indicators DCS > Mods > aircraft > *aircraft name* > Cockpit > Scripts > CargoIndicator > CargoIndicator_page.lua Original local aspect = LockOn_Options.screen.aspect Modified local aspect = -1 That's what I have done anyway, there is also base.init_pos = {aspect-box_width,1.0-box_height} I imagine altering that in the same way as the other types of indicator would work. Autopilot Indicators George/Petrovich George and Petrovic are now fixed and are based on the UIMainView setting in your monitor config file. I have included these instructions anyway, you may wish to move these indicators off the main screen. George - Apache DCS > Mods > aircraft > AH-64D > Cockpit > Scripts > AI > PrestonAI_page_common.lua The Weap_control_pos adjusts the position of the small round circle where you can tell the gunner to switch weapons etc The Compass_pos adjusts the compass position (pilot commands window) when in the gunners seat Line 24 = compass_pos = {-0.82, -0.7} Line 25 = weap_control_pos = {0.8, -0.75} The coordinate system used here seems to be normalized to the size of the screen or viewport, where the value ranges from -1 to 1: -1 is the leftmost (or bottommost) edge. 0 is the center of the screen. 1 is the rightmost (or topmost) edge. Values greater than 1 will move the indicator onto the next screen in whatever direction. Petrovich - Mi-24P DCS > Mods > aircraft > Mi-24P > Cockpit > Scripts > HelperAI > HelperAI_page_common.lua The compass position controls both Line 20 = compass_pos = {-0.75 , -0.5} Follow the same method as for George AI cheers Jon

For those gauges you need another program like ikarus Or Helios

Here you go. Resolution for DCS is 3520x1080 in DCS settings menu Select kewldude27 for monitor setup in DCS settings. for two smaller displays, when you replace the power cord. _ = function(p) return p; end; name = _('kewldude27'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920/1080; } } LEFT_MFCD = { x = 1920; y = 600; width = 800; height = 480; } RIGHT_MFCD = { x = 2720; y = 600; width = 800; height = 480; } GUI = { x = 0; y = 0; width = 1920; height = 1080; } UIMainView = GUI Or running only one of your smaller displays _ = function(p) return p; end; name = _('kewldude27'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920/1080; } } LEFT_MFCD = { x = 1920; y = 600; width = 400; height = 480; } RIGHT_MFCD = { x = 2320; y = 600; width = 400; height = 480; } GUI = { x = 0; y = 0; width = 1920; height = 1080; } UIMainView = GUI Alternative guide

Displays Table and AppSettings.lua Some information I've been playing with and thought I would share with you. The information comes from one of the default monitor config files but didn't really explain (not to me anyway) what it was actually for and how to use it. From what I understand: Normally, DCS creates a displays table each time you run it and uses your Windows "Main Display" as the origin (X=0, Y=0). DCS DOES NOT seem to accept negative values for viewports or exports. We can however manually configure a "Displays table" in your monitor config file that tells DCS where ALL your monitors are in reference to your Windows "Main Display" It will then create a new display area that covers all of your monitors and then: The left edge of all your displays will be x=0 and the top edge of your displays will be y=0 So now there is no need for your main display to be the left and top most display. We can then use the monitor on the left, as all viewport and export positions will be positive. It seems from a bit of testing that monitors can be listed in any order and do not necessarily correspond to the numbers windows assigns your displays. As long as you define your monitors in reference to your "Main Display" The default display table created by DCS would result in something like: (2 is my main) and with the Display Table it would be or maybe you would prefer. This doesn't really solve a lot of issues, other than being able to export MFCD's etc to a monitor left, or above, your main display. Unfortunately, I don't think it will fix things like the opening position of the kneeboard and crew screens, George and Petrovich etc. and there are still areas of the resolution that there is no physical display to show anything output into those areas. Of course this means that your Center view and any exports will have to be modified to their new positions relative to the new x=0, y=0. I have put the displays table at the top of the monitor config file, and this seems to work. eg. Appsettings.lua The appsettings.lua file is located Saved Games > DCS > Config > appsettings.lua It seems that this may be related to the displays table. Several users have edited this file to stop DCS turning screens black when they are not required by the user. I haven't done much testing with it at this time. Cheers Jon

Did we get anywhere with this?