jonsky7

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?

Check out this guide

I noticed this, Had a group of 4 infantry. Selected "Embark" from the Menu - First man got in, others did nothing Selected Disembark from the menu, the other 3 got in lol, flew them to my destination, they all got out when selecting disembark again.

Introducing my Voice Attack Profile for the NS430 GPS Module Choose between standard Voice Attack keypress mode, or DCS-BIOS Direct to DCS mode. It allows text entry by speech for quickly setting up Direct-To destinations and user waypoints. Use a single voice command to enter "Direct-to" Any airfield, on any map Use an automatic position entry command to get directions to any random position on the map. Press any button Rotate any knob Open any page on the unit Automatically switch between Imperial and Metric units. Save and recall data fields on the Deviation page and the Map page. The download package contains: The Voice attack profile Keyboard.diff.lua for the required keybinds for the NS430 Module when using standard mode. A couple of sound files for clicks, it also uses a couple of sounds built into voice attack, and text to speech. A READ_ME with instructions on available voice commands, and how to install Available in the User Files Section https://www.digitalcombatsimulator.com/en/files/3315023/ Get DCS-BIOS here DCS-BIOS: https://github.com/DCSFlightpanels/dcs-bios/releases v2.02 Demo Video, All data for the South Atlantic map was retrieved by DimOn's really great kneeboard files https://www.digitalcombatsimulator.com/en/files/3312200/?sphrase_id=18258131 (I don't own this map at the moment) IMPORTANT - CHOOSE BETWEEN STANDARD MODE OR DCS-BIOS MODE

Strange, if you open "set up USB game controllers" in windows, and go to the properties of your joystick. When you hold a joystick button, does the corresponding light in the properties window stay lit, or does it just flash?

Was there any way to do this for the keyboard? So one key press is one notch. I've tried adjusting the timings in voice attack, but I can't get it to be consistent. Sometimes one press in voice attack is one notch and sometimes it's two with the exact same timing. EDIT: Never mind, I looked at @CHIC code and applied the same to the keyboard default.lua. I also made it so that there is individual bindings for scrolling as the default, and in steps which I've added. I can't see how to make it one step per click but then scroll if you hold it down, and I couldn't find any aircraft where that happens on a similar dial. So here is version 1.25 of the mod, OvGME ready GPS Rotary Encoder Fix v1.25.zip

OMG, thanks for this, I couldn't for the life of me figure out why every time I changed the pattern length it would change to 9843ft. That must be the maximum length if feet.

Having this issue also, attached a log file, but the game just hangs, rather than crashing. Also on Syria map, multiplayer. dcs.log

Thanks Flappie, Though my issue is not exactly same as the post you linked, I've had a read and can't see any harm in doing it, so I'll give it a try. DCS is currently crashing for me, and at least a couple of other people in the server I play, when zooming all the way in on the F10 map, rather than when I switch back to the cockpit. It only happens when zooming all the way (or within a couple of mouse wheel detents of all the way in) Cheers Just leaving this here for ease of finding it again. https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

Had a fair few instances of the game crashing when zooming into the F10 Map. Cheers Jon dcs.log dcs.log-20210103-203347.zip

In the event of taking a few rounds, or having a heavy landing, I lose the ability to access the comms menu. I've experienced this in two ways, either The comms menu opens but the only option is F12 Exit, or the comms menu will not open at all. The pilots do not look dead, and in fact I can still interact with the cockpit. Now I understand that the radios might be inoperative, but there are more "options" in that menu. This is not normally an issue, but it removes access to the "Request Repair" option even if somewhat successful at returning to base. In multiplayer a heavy landing might be the result of a daring tactical raid to drop off troops (CTLD) in the heat of battle. Am I doing something wrong, pretty sure I'm hitting the right buttons.

I experienced this too, but I don't think it was with the AV8 or using the APKWS, I found that if I just carried a TPOD he would lase for me, for Laser spot tracking. Not the ideal solution but maybe a workaround to try.

Did you find a solution to this please?