Ramsay

Testing in SP using T0, T01, T02 and T03 (Right Alt + Right Shift + 8). The kneeboard's target list didn't update but the MFD CAS page worked as intended. Tested DCS Open Beta 2.7.8.16140

I did go back and fly your mission. https://forums.eagle.ru/topic/287989-syntetic-runway/?do=findComment&comment=4837100 Over flew the airfield "going missed" [Approach], turned to 230°M and flew past the IAF and flew circles and figure eights both sides of the runway centerline. Activating APP mode did cause issues when facing away from the runway, with the "open box" HUD guidance steering me away from the localiser at times (not always). This was somewhat similar to the old behaviour of the "upside down house" when flying away from a waypoint, which steered you away from the waypoint (since fixed), so may be a bug but could also be due to flying a back course. It's likely that the Mirage system expects/requires the pilot to approach the centerline intercept at a reasonable angle (45°) and not be flying away. Using the HSI and ADI to steer myself back towards the runway, the synthetic centerline/runway always appeared provided the LOC/GS was captured and I was facing the runway i.e. my lateral deviation was less than 7º.

TL;DR: The HUD's closed box/open box localiser guidance did seem to get confused and need APP mode reset if enabled when pointing away from the runway ? I didn't have an issue with the synthetic centerline or runway. I couldn't say if this was a bug as I'd expect pilots to use the HSI (bearing and distance) and ADI ILS bars (LOC and GS) in combination with the HUD's synthetic guidance to line up to capture the localiser Detail I did find that after going "missed" and flying a back course to the IAF there was a reflected synthetic runway in the sky in the opposite direction to the *real* runway and the open box that should guide me to the localiser, instead guided me in circles but once I turned APP mode OFF and ON, it behaved as normal but perhaps jumped/changed azimuth guidance when the open box changed to a closed box a little suddenly rather than smoothly i.e. open box would have me flying left and suddenly change to closed box (captured LOC ?) which required a sharp turn right to line up on the runway direction/centerline. I couldn't say if this was a bug as I'd expect pilots to use the HSI (bearing and distance) and ADI ILS bars (LOC and GS) in combination with the HUD's synthetic guidance but the HUD's closed box/open box localiser guidance did seem to get confused and need APP mode reset if enabled when pointing away from the runway ? I didn't have an issue with the synthetic centerline or runway but perhaps the unusual "runway in the sky" should have been caught like the centerline and not drawn because the aircraft's heading was a long way off that of the runway.

Incirlik's ILS and the Mirage's synthetic runway seemed to work fine, the approach and landing was a little awkward as • you are spawning at 6,500 ft • ~14 NM from the runway • have 100% fuel, so are landing at an uprated max landing weight I flew your mission but unfortunately made plenty of mistakes while using the autopilot (changing to altitude hold, etc. causing it to drop ILS guidance and similar) but the synthetic runway was working once the glide slope was captured. Hope you'll find it useful (or a least gives you a laugh).

• To get the synthetic centerline, you'll need to be close to the runway heading and be receiving the localiser signal • To get the synthetic runway, you'll need the above plus be receiving the glide slope i.e. ILS glide slope bar is active on the ADI So if you lose the localiser signal 10 NM from the airfield, the HUD's synthetic centerline will not appear. Similarly, if you fly a low approach (~2,000ft), the HUD's synthetic runway won't appear until ~6 NM as that is when you'll start to intercept the glide slope To get the synthetic runway you'll want: • ILS frequency set and in operation for the runway/direction you are using - check with ATC, audio, ADI, etc. • Destination Waypoint [BUT] with RH/DS [CP/PD] set - i.e. runway heading/Desired Glide Slope) • APP mode selected on the PCA • altimeter pressure set to QFE (height above airfield AKA Field Elevation) If you continue to have problems, please share a short track or video

This is an example of how to setup an axis for the Fuel Lever with deadzones, ... the exact deadzone values and whether you'll need to invert it, will depend on your joystick/throttle.

Fewer polys/switches is good but lots of MFD's plus the HUD (4+1=5 for the CPG) also eats frames. I expect flying low over Beirut or Aleppo will be demanding due to large number of buildings, etc. (it is for other helicopters but I don't notice framerate drops as I'm scanning outside for threats, etc.). Away from the major Syrian cities or on the Caucasus map, I'd expect framerates to be stable but perhaps not as high as you'd like. I don't think we'll know exactly how demanding the Apache is until we get it.

Section 27 (page 598 near the end) of the DCS M-2000C manual has an introduction to the campaign. • DCS World\Mods\aircraft\M-2000C\Doc\DCS M-2000C Flight Manual EN.pdf There are also .pdf versions of the kneeboard mission briefings in • DCS World\Mods\aircraft\M-2000C\Doc\Campaign\Mirage Caucasus M01.pdf, etc. You should still check the kneeboard and mission briefings though in case a later change/update hasn't been reflected in the .pdf

AFAIK the AGM-65E was an older version which the Harrier couldn't self laze, not sure of the exact reasons. The AGM-65E2 (USAF AGM-65L) is a newer variant developed around ~2012 with a digital semi-active laser seeker and can be self lased. For gameplay reasons the older missile was allowed to be self lased in DCS, now the DCS Harrier has been updated to reflect 2015 specs. both the E and E2 variants are in game. When discussing Harrier capabilities it's important to be specific about the date e.g. Sidearm stock was depleted by ~2000, the TGP was mounted on the wing stations in ~2004 and it was only after ~2012 that the TGP could be mounted on the centerline (same time as the AGM-65E2). If you have evidence of the Harrier self lasing prior to 2012, I'm sure Razbam would be willing to review your feedback.

Ground returns/clutter that the doppler gate doesn't catch, they are easy to differentiate from a real contact as they don't persist. IIRC there's a doppler setting that reduces/removes most of these false returns at the cost of a reduced detection range (55 --> 45). As a novelty you can disable the doppler filter completely and see false returns from every hill top, building, etc. but it's not something to use in battle :lol: Unknown, different radars, different frequencies.

AFAIK "Waypoint Over Fly" is not implemented. IRL when using NAV mode (rather than IFA=GPS-INS coupling) the Harrier is subject to INS drift, this position drift can be corrected by overflying a waypoint/landmark and doing an "overfly update". Checking the 2011 POH, INS position updates are done using the MFD and ODU. WOF is used to correct for GPS Altitude error, etc. i.e. waypoint is at 1000ft MSL, radar Altimeter= 500ft, GPS reads 1600ft MSL WOF adds a error correction so the Altimeter = Waypoint Altitude + Radar Altitude = 1500ft This is different to TOO, which assumes the aircraft's altitude is correct and uses the Radar Altimeter to calculate the target's altitude i.e. Target Altitude = Aircraft Altitude - Radar Altitude AFAIK DCS doesn't model these measurement/database errors and assumes the Digital Terrain Map/GPS altitudes are "perfect". Is that not what TOO does ?

No idea about TrackIR as mine is still working as normal. For the "X-56 Rhino", a number of default keybinds have changed, so it's expected that some assignments might need to be updated i.e. I had a handful of keybinds that I reassigned.

If you bought the previous "all-in-one" Steam version (£16.99) that included the 2D popup and L-39C/Mi-8 Cockpit models - you'll be missing the 3rd Party SA-342, C-101CC and C-101EB cockpit models @ £4.99ea. There's no reason to rebuy the Mi-8, L-39, etc. for the NS430 as you'll already own them (even if Steam only shows you owning the 2D version and doesn't show them in your library). If unsure, you can check the contents of your install folder i.e.

I'd recommend Syria if you have 32GB RAM and are running DCS off a SSD or NVMe m.2

Good news, 3rd party NS430 cockpit addons have been added to the Steam store. https://store.steampowered.com/app/1522410/DCS_NS_430_Navigation_System_for_SA34_Gazelle/

AFAIK the RAM footprint is only one element, the other is VRAM due the number of detailed buildings, etc. With that said, I'm fairly "happy" with my performance in Syria when there's 30 players on the 4YA PvE "Capture the Bases" server, but I'm not using very high settings, multi-monitors or VR and have Syria/DCS on a NVMe m.2

The logic behind the HUD's DLZ has been improved, so the range/fire cues are more accurate. The range of the 530D hasn't changed, so if you already had a good "feel" for it's real DCS range(s), nothing will have changed i.e. if you knew to fire at 9 nm rather than wait for the previous cue at 8 nm. The improved DLZ is particularly noticeable at higher altitudes vs faster (inbound) targets.

Engine Oil Temperature ?

My understanding is that TrackIR minigun control is broken ATM and using TrackIR interferes with "mouse look" minigun control. In testing, I had to close the TrackIR application and restart DCS to control the Gazelle's minigun (IIRC in the Huey it was sufficient to Pause TrackIR with F9 but that didn't work for the Gazelle).

It doesn't look like the center dot has changed (but everything else looks great - and I'd fear a large center dot might obscure the target in an already "busy" HUD). Make your own judgement on the WIP footage @57:37

AFAIK the minigun's controls are being worked on and unfortunately TrackIR needs to be disconnected ATM for the "camera/look" to work.

AFAIK it is not a bug, rather this is a limitation in how the AV-8B works, the TGP creates a fixed Target Point(s), not a dynamic SPI's that update as the TGP tracks a moving object, etc.

Your INS looks to be misaligned, did you enter your True Heading when doing the fast align i.e. one of your spawns has a THDG = 250°, if not set THDG defaults to 000°, so the HSI compass rose, HUD tape, etc. would be 110° off. If you can't get a good track, a video or screen shot of your HSI/INS pages after alignment would help. For ref. - 1 - Spudknocker's Startup Video 2 - Chuck's JF-17 Guide (page 81 covers THDG input) https://drive.google.com/file/d/1u5B2Kng7XusY7gK5fvyUEwxI6M6AXxXZ/view?usp=sharing

Yes, because the C802 worked when the JF-17 was first released and Deka had control of it's implementation. AFAIK, ED now control the weapon coding and third parties are reliant on ED to test their changes and work with them when making changes. The C802 relies on core DCS functions (NOT Harpoon code), when ED change/tweak these core functions for for their own weapons i.e. the Harpoon, Walleye, IR Maverick, etc., the change *can* break the function of 3rd party weapons. When things break or get missed I'm sure ED and their partners want it quickly resolved, however ED's priorities/resources don't always align and we need to be patient. While we can speculate, don't expect ED or Deka to attribute blame, as that is not how professional companies conduct business.

Storm of War is still the most popular WWII MP server by far but YMMV depending on your region.