Jump to content

jonsky7

Members
  • Posts

    1376
  • Joined

  • Last visited

Everything posted by jonsky7

  1. 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.
  2. 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
  3. 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
  4. 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?
  5. 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.
  6. I don't use VR myself but a nice find none-the-less Where do add the line? Top, bottom, anywhere? Cheers
  7. 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!
  8. 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
  9. 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.
  10. 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
  11. 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
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. 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
  17. 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
  18. I appreciate you taking the time to leave a thank you note, cheers
  19. You'll get a resolution of 6400x2160 in DCS
  20. 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.
  21. 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.
  22. https://m.twitch.tv/videos/1897761024 BoB flight starts at 1:25:40 Looks and sounds fabulous
  23. 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; }
  24. 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
  25. 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.
×
×
  • Create New...