Jump to content

Clarion

Members
  • Posts

    8
  • Joined

  • Last visited

  1. The signage and markings are the same as the signage for a displaced threshold as defined by the FAA: https://www.faa.gov/air_traffic/publications/atpubs/aim_html/chap2_section_3.html Obviously Beirut-Rafic isn't within FAA jurisdiction but the signage and markings are consistent with the FAA so I assume it is an international standard. If it was intended to only be a taxiway they would have kept the markings for a taxiway and used a demarcation bar at the runway threshold. However, if it is a fault with the map, then this topic should be moved to the map's forum?
  2. When taking off runway 21 at Beirut-Rafic, Jester doesn't understand what the displaced threshold is and gets very upset with you since he thinks you are taxiing way too fast.
  3. Prior to the update today you could set up the FCR in TWS in both A-A mode and Missile Override mode and it would remember that. Now if you switch away from those modes (e.g. switching between them with the dogfight switch), it forgets you were in TWS and drops you back into RWS.
  4. Also: IFF only works once from the WSO seat. After the one IFF interrogate, the WSO can no longer IFF.
  5. I don't know why it works exactly but I think it's because if you're stretching a lower resolution over a larger screen now each individual logical pixel is larger meaning when an aircraft is distant it's apparent size will be larger since the resolution has less granularity. You don't have to trust me though, you can try it yourself. Set up a test mission with a bunch of aircraft flying co-altitude with you on the same heading and airspeed at different distances. Try this mission with your normal settings and see how hard it is to spot each of them. Then temporarily turn off your multi-monitor configuration and set your resolution to 1080p with fullscreen and see how hard it is to spot them. You can even take screenshots and compare side-by-side. The LUA I'm trying to use is in my original post.
  6. Yep, I change the resolution in the DCS settings as well (and check fullscreen) but no matter what combination of resolutions I try in the LUA config and the DCS settings, the closest I can get is having a 1080p camera viewport with unused black space on my monitor. Other way around Stretching 1080p onto a 1440p monitor helps me with spotting a great deal.
  7. I've always had trouble visually spotting in DCS. The primary piece of advice people will give you to help with spotting is to switch to 1080p resolution. I tried this out with a single monitor and it does help. However, I can't get this to work right with my multi-monitor setup. I have two monitors with the main camera viewport on my primary monitor and then MFDs on my second monitor. I've been playing around with the multi-monitor config file but I can't get it to stretch the 1080p camera viewport to occupy the entire 1440p monitor. The closest I can get is the camera viewport with blackbars around it on my main monitor. Is it possible to stretch the 1080p across the primary monitor? Below is the monitor setup LUA I've been using. I normally use a very similar config but instead with 1440p. _ = function(p) return p; end; name = _('MFCDS on Second Monitor (1080p)'); Description = 'Main monitor is viewport, secondary monitor with both MFCDs' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920 / 1080; } } LEFT_MFCD = { x = 1920; y = 0; width = 900; height = 900; } F14_HSD = { x = 1920; y = 0; width = 900; height = 900; } RIGHT_MFCD = { x = 1920 + ( 1920 / 2 ); y = 0; width = 900; height = 900; } F14_VDI = { x = 1920 + ( 1920 / 2 ); y = 0; width = 900; height = 900; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center
×
×
  • Create New...