jonsky7

Yes, If you go into your monitor config file usually located in Saved Games\DCS\Config\Monitorsetup there is an entry at the bottom that says UIMainView = Viewports.Center The UIMainview sets the boundaries for the Main menu, F10 map, Mission editor, and the dialogs that appear in game. You can change it from the above to something like UIMainView = { x = 0; y = 0; width = 2560; height = 1440; } and limit the boundary to either one of your monitors. If you have absolutely no idea what any of that means, you might want to have a read of this thread

For Ikarus, if you go to your DCS-ExportScript folder, mine is in Saved Games/DCS/Scripts, but you may have been able to choose the install path, I don't remember. Open the Config.lua At the bottom there is a section with the title "Other", there is two values there called (line 36 and 37 for me) ExportScript.Config.ExportInterval = 0.05 ExportScript.Config.ExportLowTickInterval = 0.5 and the above are their default values. I have adjust the lowtick value to 0.1. Ikarus uses two different update timings depending on how important each "export" is. Decided by whoever wrote the scripts for each aircraft. The most important instruments should be updating every export interval, or 0.05 seconds Things like engine instruments, navigation instruments etc The rest use the low tick interval, Fuel tank contents, panel lights, switches and levers etc I assume this was done to lower the amount of CPU resource Ikarus uses.

Sorry, I haven't used Helios, so I don't know what it does when you make a profile with it. I did fancy it at one point, as I use the now not supported Ikarus to put gauges in my cougar displays when I'm flying Heli's and warbirds. Captain Zeen's profiles looked good, but no warbirds unfortunatley. Eg, in the Mosquito I have this, and the gauges are inside the TM Cougars, it uses the gauges out of the Spitfire section of Ikarus

If you're interested MAX, you can now configure your exports by aircraft type in your monitor config file. As an example: In the A-10A, which has a Right MFCD, you could export it to a position we'll call 1 Then when you jump into the Su-25T, which also uses Right MFCD, you can export it to position 2 Which would mean you wouldn't have to load separate profiles for each aircraft. See in the guide linked above for further info. it looks something like..... _ = function(p) return p; end; name = _('JB by type'); Description = 'JB by type'; Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } function reconfigure_for_unit(unit_type) if unit_type == "A-10C" then LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } elseif unit_type == "Su-25T" then LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } elseif unit_type == "A-10A" then LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } else LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } GU_MAIN_VIEWPORT = { x = 0; y = 0; width = 2560; height = 1440; } UIMainView = { x = 0; y = 0; width = 2560; height = 1440; }

You seem to have modified the ViewportHandling.lua, and this is fine if you only play single player. If you want to play multiplayer, you will need to follow the guide step-by-step and do this same alteration to the ViewportHandling-resize.lua file instead!!

Did you set the aircraft group skill option to "player" or "client" ? I think it needs to be on client. I didn't see them mention it in tutorial as the aircraft was already placed.

You can move the kneeboard anywhere you like with some modification. See this thread, scroll down a bit till you see the title about moving the kneeboard.

I believe you cannot occupy the second seat in a multicrew aircraft until the first seat is occupied. So the pilot must be in the aircraft before the navigator can join. The pilot will then get a message saying something like Diego wants to join your aircraft Accept Deny (buttons)

Ok cool, glad you got it working, as well as can be anyway. So I believe that the Su-25T Shkval screen is exported to the RIGHT_MFCD position. That code is buried within the encrypted files of the Flaming Cliffs aircraft but I'm pretty sure that it is. You didn't have an entry for either Shkval or LEFT_MFCD in you Cubesim.lua file, that's why the export wasn't working before. You can, if you wish, change the TV-Indicator init.lua line from try_find_assigned_viewport("EP13") to try_find_assigned_viewport("RIGHT_MFCD") You could then delete the EP13 entry from your cubesim file and return everything to the way you had it before and with any luck the cursor problem wouldn't be an issue.

I've had a look at your previous Cubesim.lua file, but it doesn't have the entry for the Schkval, so can you upload your most current monitor config file. Also include a screenshot of your current window display settings page, with the resolutions of your screens. As for the naming of the viewports. The init.lua files in the indicator folder of whatever instrument you are trying to export simply sets the name of that viewport/export. In your monitor config file you assign a viewport name and output it in the position you define. So the init.lua file is simply saying try_find_assigned_viewport("VIGGEN_RADAR") "hey, in the monitor config file, is there a viewport named "VIGGEN_RADAR"? If there is, export this instrument display to that position. And then in the monitor config file you have VIGGEN_RADAR = { x = 2650; y = 390; width = 960; height = 960; } Oh yes, there is a viewport called VIGGEN_RADAR, I'll export the instrument display to that position. You can name the export anything you like really. Doesn't matter if it's called VIGGEN_RADAR, AJS37_RADAR, or Robert for that matter. As long as the name in the init.lua of the instrument, and the one in your monitor config file is the same. The capitalization of the name is important, as does any underscores etc. eg Viggen_RADAR is not the same as VIGGEN_RADAR If the init.lua has a line like try_find_assigned_viewport("VIGGEN_RADAR", "LEFT_MFCD") Then the output will first search for the name VIGGEN_RADAR, and if it doesn't find it, it will search for LEFT_MFCD, and if it doesn't find that, then the display will not be exported. I've seen a few people who use cubesim display have this problem with an offset cursor, it's not about 80 pixels off is it? I usually recommend that your main screen is the most left in display settings Although that brings about it's own challenges with things like the kneeboard. Most of them can be fixed, with a bit more modification. It often takes a considerable amount of time to get this multi-monitor malarky working as you'd like it too. I persoanlly find it's worth it, it's up to you to decide if it's worth it for you. Luckily, it always seems like there is somebody to lend a hand. Oh, I've just noticed too, in one of the files you have uploaded you have try_find_assigned_viewport("Shkval","LEFT_MFCD") check the spelling of Shkval !!!

Sorry if this is solved already, I haven't read the whole thread Here is the required modified files, tested working, for the export of the Viggen Radar, and EP13 TV display Viggen Export.zip In your monitor config file you will need to define the positions of the displays, like you do for an MFD eg VIGGEN_RADAR = { x = 2650; y = 390; width = 960; height = 960; } EP13 = { x = 6210; y = 360; width = 825; height = 825; } With the names as above VIGGEN_RADAR and EP13 The export of the EP13 isn't exactly brilliant, it has an odd shape, but it works.

Ah, like I said I'm unable to view the files atm. It will be the init.lua file in the indicator folder.

I'm not at my computer right now so can't search the game files. In the game files Dcs world/mods/aircraft/ajs37/cockpit/scripts Is there a folder for the EP-13 display? If there is, in there should be a folder named display. In the display folder you are looking for the init.lua file, if there is one. Edit that file with dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("EP13") At the bottom. If that works, you should be able to edit the monitor config file with a new export called EP13 Just be aware that modifying the init.lua file will break the integrity check on some multiplayer servers. Good luck

Well they do seem to move, albeit at a very slow pace. Then when they get to the end of the line, they just dissappear. Was kind of thinking they were some sort of leftover, or misplaced civvy traffic. Either way, would be nice if they could be removed.

What's with the seemingly never ending line of what I believe are tugboats along the shore lines of England and France. Every 500m or so, in a perfect line following the coastline. They don't show on the map of the mission editor, so not sure how to remove them. boats france.trk boats uk.trk

Currently for Ai flights of more than 1 aircraft, numbers 2-4 do not switch off the left landing light after take-off, or at all throughout the mission. The flight lead does which is expected. Track attached and miz Ai wingman lights.trk Ai wingman lights.miz Cheers

Do you mean the close ups of cockpit details? Can you link the specific video you mean, and include timestamps of particular clips you're interested in?

This works for 3-way switch for flaps in the Su-25T, not really tested in any other FC3 with 3 position Flap lever. {down = iCommandPlaneFlapsOff, up = iCommandPlaneFlaps, name = _('Flaps Up else Centre (3-way Switch)'), category = {_('Systems'), _('Custom')}}, {down = iCommandPlaneFlapsOn, up = iCommandPlaneFlaps, name = _('Flaps Landing else Centre (3-way Switch)'), category = {_('Systems'), _('Custom')}}, Basically you have a "Flaps UP" command, and when that key is released the "Flaps UP/Down Toggle" command is used to get the Lever to the centre position. And you have a "Flaps Landing" or all the way down position, and when that is released the "Flaps UP/Down Toggle" command is used to get the Lever to the centre position.

I don't use VR myself but a nice find none-the-less Where do add the line? Top, bottom, anywhere? Cheers

Either that or not freeze. A frozen display doesn't really serve much purpose. That screen space can be used for something else while in the pilot seat. Thanks for the reply!

Hi @ZuluThreeZero I'm sorry to say that ED has not given us the ability to define a multicrew position in the monitor setup file, at least not that I know of. The TEDAC remaining on screen but FROZEN when switching from CPG to PLT seat seems to be a "bug" I've just raised it as such

When joining the Helo in the PLT seat, the defined TEDAC export position has no output - Good When switching to the CPG seat, the TEDAC export position shows the TEDAC screen- Good When switching back to the PLT seat the TEDAC screen remains visible but is now frozen - Bad! May I ask for the TEDAC export to switch off completely when switching back the PLT seat please. Many thanks.

The EHSI is exportable by default. No mods necessary. in the monitor config file it is simple named EHSI ie RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } EHSI = { x = 2561; y = 370; width = 520; height = 520; } The RWR, DED, and CMDS panels are exportable but require modifying game files, modifying these files will break the integrity check on servers running the pure scripts option. The RWR does not export the "crosshair", only the symbols. These are my modified files, you can use a mod manager like OvGME, or overwrite the game files. F-16 exports.zip To use the exports you need to configure your monitor setup file to look for LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } EHSI = { x = 2561; y = 370; width = 520; height = 520; } F16_RWR = { x = 2561; y = 880; width = 520; height = 520; } F16_CMDS = { x = 6170; y = 1345; width = 820; height = 120; } F16_DED { x = 6170; y = 1345; width = 820; height = 120; } feel free to ask further questions visit these

Those displays are not exportable by default. In order to export those displays some modifications to the game files are required. Might it be that you may have forgotten that you modded those files in the past? If you need a reminder, check this post

I can't get to my computer at the moment, I'm on holiday. Is the sight not filling monitor 1? Do you use monitor 1 as your main display, like cockpit view etc? In windows settings, is monitor 1 or 2 set to main display? You could try deleting the viewdx viewdy and aspect parameters from uimainview and gumainviewport entries. I have them setup like mfd.