Ramsay

Unfortunately DCS's ATC behaviour is a hard coded ED feature and the ATC/ILS desync that occurs with a moderate headwind can and does effect all maps. AFAIK it's not something a map team can fix and requires ED to rework/fix the core DCS ATC/ILS logic, however it appears to have a low priority (perhaps because it's non-combat related). There's the promise of a DCS ATC rework sometime in the future but that still appears a long way off, so for now - players need to keep DCS's idiosyncrasies in mind when flying or designing missions.

Have you tried a Install Repair ? Which mission/module are you testing this in ? A quick test using Open Beta with the Gazelle 342L and F-15E in Single Player showed no issue using LALT+Left Mouse button.

Only by creating/editing a flight plan using the Mission Editor before loading/flying a mission.

No, set the cp value using it's TRUE heading, that doesn't change over time.

The best guide to using the FD with a VOR approach I'm aware of is in Chuck's guide on page 152. https://chucksguides.com/aircraft/dcs/c-101cc/ It covers the steps but unfortunately the FD and HSI pictures are a little confusing as the Heading bug wasn't set to match the 45° intercept the FD uses once the VOR radial is reached/captured (note it's also possible for the FD to steer away from the radial if it has the "wrong" initial heading). As the VOR radial only gives lateral FD guidance, vertical/Altitude guidance (if required) is set using the regular FD "Altitude" mode. Tested using C-101EB and C-101CC, DCS Open Beta 2.9.2.49940

The DCS Open Beta F-15E radar is working in Single Player, I'm not on the Stable branch or flown MP recently - so can't comment on your specifics.

These are my favourites for the TPOD HTS ... and SSS modes. https://forum.dcs.world/topic/324103-help-with-ir-mavs/?do=findComment&comment=5199684

TL;DR: No, it's the MSL altitude, so -9 is scanning 9,000 ft BELOW Sea Level. Detail: From page 311, DCS_F-15E_Flight_Manual_EN, 2023-12-12.pdf

It's a general/long standing DCS bug/feature that only single player missions/campaigns log their flight hours in the log book i.e. IIRC training missions and multiplayer aren't counted. Once you start using the mission editor or fly some user created Single Player missions - you should find your logbook updates as expected. Logbook Doesn't Count Training Mission Flight Hours Tested DCS Open Beta Multi-thread 2.9.2.49629, Caucasus SP F-15E Air spawn.

I'm not connected to Polychop in anyway, however I appreciate they have stuck around (rather than walked away) to maintain and improve the Gazelle. Comment: This is my own personal take on the "situation" - Yes, I would have liked a Gazelle update this month. IMHO everything else you've said is off topic / unhelpful. Detail: The original Polychop team dissolved several years ago, however a couple of the original dev's kept the "Polychop" name and have dedicated their time to developing an improved flight model, a new module - the Kiowa and to maintaining/improving the existing Gazelle. After a serious illness/accident ? timelines changed and a couple of new members/volunteers joined the team to "help" - including rebuilding the underlying Gazelle code from scratch, the new flight model, 3D assets and textures, weapons, etc. which we enjoy today. Remember the people you are complaining to are the ones that stuck around / joined to "fix" the module. • The work is done part time (usually along side a full time paid job) and schedules change • the code may have been written by another coder or no longer work as intended • it often requires research, development and testing (this isn't a production line with known solutions) • there are "internal" dev development plans, these aren't available to the public as everything is "subject to change" and depend on technical progress, internal testing, changing prioritisations, etc. • With ED you have a free trial to test before purchase. • For Steam you have 2 weeks / 2 hours play to decide on your purchase. After that, you've bought the product "as is", outside of exceptional circumstances - that's the end of the matter.

No, the NS430 GS value can be close to IAS when low/slow, but high and fast it follows the higher GS, under reporting by ~10% For a F-14B at 0.8 IMN @ 30,000 ft, • NS430 gave GS = 432 Kt • Cockpit IAS = ~310 KIAS • Cockpit Info Bar (LCtrl+Y) IAS = 293 KIAS • F10 Map GS = 479 For info. 0.8 IMN Airspeed converter https://aerotoolbox.com/airspeed-conversions/

Open Beta looks excellent with most (if not all) of the NS430 Magnetic and True bearings reading correctly. I'm not sure about the Ground Speed (perhaps still WIP) as it seems to report a speed higher than IAS but ~5-10% less than the GS reported by other methods i.e. F10 map, INS, etc. this seems confirmed by ETE overestimating the time taken to fly a route leg. Either way, GS is much better than it was, please pass on my thanks to which ever team is responsible. Detail: ✔ Distance 31.6 NM ? Ground Speed 383 KTS (correct value ~424 KTS) ✔ Ground Track 128°M (IMHO within limits) ETE 8:14 (incorrect should be approx. 4:28) ✔ Desired Track 128°M ✔ Bearing to waypoint 128°M (IMHO within limits) null Tested in DCS Open Beta Multi-thread 2.9.2.49629 using F-5E, F-14B, SA-342L and MB-339A, Caucasus Map

Testing with the latest Open Beta 2.9.2.49629 - this doesn't seem fixed i.e. behaviour with RNAV and TACAN CDI, etc. remains the same when tested from Nellis.

The DCS AV-8B N/A is regularly included in Steam Sales i.e. 50% discount in Sept., 30% discount in the Summer Sale, etc. https://steamdb.info/app/759130/

In the case of the F-15E's Auto Acquisition Switch, the "standard terminology" used by SME's, Razbam, etc. is Forward, Aft and Down. I assumed the OP was familiar with the AACQ switch as well as giving the relevant page(s) in the DCS manual. In long hand the RL F-15E workbook says to "Push down on the auto acquisition switch to return to search", so you'll need to take your complaint to the USAF/Boeing.

AACQ is an abbreviation for the Auto Acquisition Switch found on the the F-15E pilot stick - it's a spring centred, two position plus depress switch used to change A2G HRM Map size, TPOD FoV, etc. I'm sure you know it but are getting confused by similar abbreviations used in differing airframes. See page 318 of DCS_F-15E_Flight_Manual_EN.pdf, 2023-12-12

TL;DR: AACQ DOWN returns (from TWS) to SEARCH (RWS) Detail: For more detail see page 326 of DCS_F-15E_Flight_Manual_EN.pdf, 2023-12-12

The binds are "Joystick Abstractions" and only appear when a joystick is plugged in. They can't be bound to the keyboard by default. Hence why @FierceLV is asking for the keyboard assignments to be fixed to work as intended. You would need to modify the default keyboard file to add them i.e. copy the relevant "AN/APG-70 Radar" section(s) from • DCS World\Mods\aircraft\F-15E\Input\F-15E\joystick\default.lua to • DCS World\Mods\aircraft\F-15E\Input\F-15E\keyboard\default.lua Your install looks correct. Tested in DCS World Open Beta 2.9.1.48335

Not AFAIK. Correct. No the limitation is barometric, AFAIK the low air pressure makes cooling the laser/electronics difficult. Above 25,000 ft ISA? the laser Safes to protect the pod from damage.

TL;DR: Al Dhafra's ILS is bugged and has been for a long time - the issue effects all modules. https://forum.dcs.world/topic/334755-al-dhafra-air-base-ils-issues/?do=findComment&comment=4411274 Detail: To land at Al Dhafra (zero wind) using the Mirage's ILS / synthetic runway :- 1. Ignore ATC's instructions to land on 13L and plan to line up for 31R 2. Tune ILS to 109.10MHz 3. Prep Waypoint CP/PD = 308°T / 03.0° (if using a landing waypoint - it will have the wrong direction). 4. Line up on final for 31R (306°M) i.e. using TCN 96X 5. Follow normal landing procedures using APP mode, Autopilot, etc. as desired. 6. Once Localiser and Glide Slope are captured - the synthetic runway will appear in the HUD. Tested using A-10C II and Mirage 2000C, DCS Open Beta Multi-thread 2.9.148335

Correct

Sounds like you may be using a very old mission as the Mirage 2000C mission editor default should be 234 chaff / 64 flares i.e. the maximum allowable of each type, this is NOT the same as the amount carried/dispensable. This is explained in the DCS M-2000C Manual on page 375 The closest you can get to 30 flares is by equipping either :- • the older Eclair pod adds 16 flare and 16 chaff = total loadout of 32 flare / 128 chaff. or • the newer Eclair-M pod with a 2/4 loadout of 16 flare and 72 chaff = total loadout of 32 flare / 184 chaff You can't fit a partially filled decoy cartridge i.e. a 8 shot flare cartridge with only 6 flares.

TL;DR: You change the amount of chaff and flare carried by choosing different Eclair pod loadouts. Detail: You can not change the amount carried internally (112 chaff / 16 flares), however the Eclair/Eclair-M counter measure pods have different chaff/flare loadouts to choose from. The exact amount of chaff and flare carried can be confirmed via the kneeboard.

There are 6 dispenser cartridges and each one holds 30x chaff or 30x flares, so you can carry a max of 180 chaff or 180 flares or a combination of both. Cartridge selection is made using the aircraft's Special Options tab "•••" in the Mission Editor.

I usually cycle the Maverick Cage/Uncage button to get a 2nd/3rd Laser Maverick to detect the spot i.e. there seems to be a desync between the HUD/MFD symbology and the 2nd Mav's cage status. IIRC this is an already reported bug. https://forum.dcs.world/topic/316305-reported-tpod-situal-awareness-cue-moving-erratic/