Ramsay

It's a spring centered switch.

Because in the *real* it is a spring loaded, 3 position switch and in the *real*, it remembers the previously selected elevation for it's different modes and tracks the elevation of locked targets, none of which works if the radar elevation is bound to a axis. Perhaps later RB can add a radar axis that can be bound as a virtual 3 position switch but not in this patch.

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.

Some players read up on the RL documentation and wonder why it doesn't work like the real. Others assume DCS is correct but then don't understand why there's no way to enter an ILS frequency for unsupported maps such as Nevada, Syria and Marianas. Errors matter to quite a few players as it confuses what should be a "simple" system (a microwave landing system with a limited beam width and 20 fixed freq. channels). As I use DCS to learn/appreciate how combat aircraft work in the real world, it was important (to me) to get AWLS modelling fixed/correct in the first year of the AV-8B's EA release. IMHO it's become a moot point as the years have passed and Razbam have doubled down on their implementation i.e. by adding the AWLS "ILS" pages to the kneeboard, At least I've come to understand Razbam's position, ignore their AWLS implementation and move on (glass half full, etc.) Obviously you are entitled to play DCS how you like and have your own opinion but this is a bug thread and IMHO the OP's question was valid.

The approximate Magnetic Declinations of the maps in DCS for the default mission date (2016) are • +6°E Caucasus • +1°E Marianas • +12°E Nevada • +2°E Persian Gulf • +4°E Syria The Normandy/Channel maps • -12°W 1944 • -1°W 2016

F-16C DED > LIST > MISC > MVAR F/A-18C HSI > DATA > A/C

Correct. Common got'ya are • Designator, LST and LGB need to have the same code (default is 1688 but harrier designator resets to 1111 with weight on wheels, IRL a software upgrade fixed that). • IRL codes are physically set on the bomb while on the ground, some modules mimic this restriction (while others allow it to be changed mid air as the AI JTAC can't be asked to change it's laser code). • In DCS the laser spot is at the end of a 8 NM (15km) yard stick, so the designating aircraft must remain within 8 NM of the target until impact (else the spot floats mid air). • The default DCS AI JTAC will lase for 5 minutes max (CTLD lase/smoke lasts as long as needed)

Radar As I'm sure you are aware, radar backscatter from helicopter blades isn't modelled by any radar in DCS* (I'm not sure why you are singling out the Gazelle ?). As blade backscatter isn't modelled, it's relatively easy for a DCS helicopter to break a radar "lock" by notching or getting lost in ground clutter, therefore once it's detected, I'll get closer and switch to A2A IR missiles, however doing so, does mean I'm fighting the helicopter in it's own domain and opening myself up to ground fire and manpads. This is how a 1996 Boeing Patent describes helicopter radar detection To paraphrase the rest of the patent, helicopters are detected in a similar manner to other ground targets and a Fast Fourier Transform used to detect the signature pulses from the rotor blades, thus differentiating helicopter signatures from other ground targets. The rotor blade radar returns don't sound that much different to other ground returns ? IR Emissions DCS's IR emissions have two levels, 'nominal/running' and 'afterburner', as DCS helicopters inc. the Gazelle, don't have an afterburner , they always emits the same IR signature hot or cold (modified by aspect, range and los). The usual reason to lose an IR lock is a change in aspect or break in line of sight, it's been my experience that Gazelles don't go "invisible" without a reason. * I haven't tested Heatblur's F-14

It's a small, single engine helicopter that's often nap of the earth and mixed in with ground clutter, it likely shouldn't be "easy to track". Never had an issue getting shot down in the Gazelle myself and I've certainly shot down AI Gazelles in MP with the Mirage. These days, I mostly fly other modules due to the long ingress times of the Gazelle and more often die to NOE CFIG than to other players/AI. It has an excellent RWR and radio contact with AWACS, making it easy to recognise when you've been illuminated by a radar and dip below a ridge line to break it's line of sight. This is very different from the Huey, where you might not recognise there's a threat (without using the F10 map) If you think you've found an issue, please post a track. Not sure if MP kill tracking is an ED or PC problem though, so it's worth a bump as I know it annoys PvP players shot down by the Mistral.

IIRC the night lighting of the Tarawa was realistic (off) at one time but users asked for it to be more like the WIP preview screen shots. It's a case of not being able to please all the people, all of the time. I tend towards having some (unrealistic) lighting on the deck and island but 'feel' the ambient lighting levels of the non-navigation deck lights should be reduced i.e. of the 3 carriers, only the Tarawa has it's island number lit. Note that the Roosevelt (Supercarrier) increases it's lighting when a player spawns on it (not sure how well it's lighting syncs in MP), while the Tarawa always has max illumination. ... If DCS was wholly realistic, there'd be no street lighting, etc. in the towns or along the coastal roads. Also note that while the Tarawa's deck lights are too bright, it's missing navigation lights from it's masts/rigging, so there's an opportunity to reduce the deck intensity for the "realists", while adding mast lights in compensation, for those who want it lit like a Christmas tree.

Auto start can't know which map you're on or whether the sand filter is fitted, it's on you to do a pre-fight check after start-up (remember this "test" version has accelerated damage).

It also needs to be switched ON.

Yes, AFAIK it reduces performance when fitted and the scavenger system uses bleed air while operating. Gazelle SA-341/2 PUREair System https://shop.pall.co.uk/uk/en/aerospace/commercial-rotary-wing/engine-protection-1/zidgri78llm https://www.pall.com/content/dam/pall/aerospace-defense/literature-library/non-gated/AEGAZESEN.pdf Because using bleed air reduces performance and increases fuel consumption (perhaps ~5%).