Ramsay

IIRC "Error code 500" is windows time and date not synchronised.

IRL the AV-8B's AWLS and Hornet's ICLS are the same thing. When the LHD-1 Wasp's AWLS was certified in 1999, it was certified using F/A-18A's and simulated landing approaches. SME's say AWLS was rarely used and TACAN was the preferred/only Case 3 method. It's not clear if the Tarawa was fitted with the equipment/radar/aerials necessary for AWLS. Edit - to answer your question TL;DR: Gameplay. Detail: When the AV-8B was released, ICLS wasn't modelled in DCS, I'd *guess* that, as AWLS wasn't used much IRL, Razbam decided to model it as an ILS to give it a "function" in DCS and add a gameplay element. While I agree with your sentiment, IMHO removing a gameplay element would not sit well with a large portion of the community/existing owners i.e. I held a poll and of the few that responded, there was a 6:4 split in favour of removing AWLS=ILS. Modelling AWLS realistically ... • wouldn't necessarily add AWLS to the Tarawa i.e. pictures don't show it having AWLS equipment • would remove "AWLS/ILS" from airbases • requires the removal and/or reworking of training missions including voice lines. • might require dev time to create a portable AN/TPN-30B unit to add a TACAN/ICLS beacon to land bases, via the ME It's a lot of rework, for very little reward and likely a lot of complaints from those that didn't care or didn't want it. IMHO Razbam should move on (but perhaps explain their AWLS logic/choices better) and continue focusing on getting the AV-8B complete and of "finished" quality.

Just guessing - The hull is quite strong and compartmentalised, while the superstructure is relatively soft and squishy and is where the weapons and radar/radio masts are. The Pre-service 1974 AGM-84A SAC shows it sea skimming at 50-200 ft for most of it's cruise with a pop up / top down attack near the target. From a surface/air launch, it pulls out of it's initial dive 3-6 NMI after launch and cruises at 50-200 ft ASL for a max range of 61 - 66 NMI i.e. it had similar attack profile to the DCS RB-15F and C-802AK. With 2x C-802AK fired as a pair with different terminal attack profiles - while the pop-up/top down attack is engaged by CIWS, etc., the sea skimmer often gets through. Very different from ED's RBL profiles, which have the AGM-84D descending (from 5,000 ft) into anti-missile defences at 6 NMI and then popping back up at 2-3 NMI for a terminal attack. IIRC BN said the Harpoon's radar was increased, l can't wait to see if the cruise profiles have also improved in the next patch.

The Harpoon is probably the weakest of DCS's anti-ship missiles v.s. the CIWS/anti-missile defences of the Neustrashimyy - if you have the time/modules, I suggest doing side by side tests with the RB-15F (Viggen) and/or C-802AK (JF-17) firing in salvos of 2-4 at a time. You may also want to check how the different Harpoon flight profiles BO and RBL low (5,000), medium (15,000) and high (35,000) altitude cruise perform, as the higher altitude profiles have failed to hit unarmed cargo ships in the past. As it's a modern aircraft, the JF-17 is my preferred launch platform, so it would be my REDFOR choice (even though I mostly fly the JF-17 as blue). The C-101's Sea Eagle could also be included for completeness but as it's target can only be set in the ME, IMHO it's a low priority. I'm waiting for the new OB patch to drop before re-testing, OTOH you may wish to do BEFORE-AFTER comparisons.

Your picture look's similar to Asus's "Sonic Radar" overlay (a 2D representation of 3D sounds to give an "edge" in FPS shooters). This picture of the Dolby Atmos overlay is very similar - perhaps that's it ? https://www.reddit.com/r/csgo/comments/crm1hi/weird_sound_radar_thing_again/

• DCS 2.5.5 was the DCS version, at this time last year. • DCS 2.5.6 is the current DCS version. There will be an update to Open Beta 2.5.6.xxx next week that will add SEA mode, etc. to the Hornet radar amongst other updates/fixes, once tested, it or a subsequent update/fix will move to the "stable" branch at some point. • DCS 2.7.x is a planned future update, set to release in a few months time (ED have decided to skip releasing DCS 2.6.x and move straight to 2.7.x).

I haven't seen that and testing in a quick SA-342M MP flight (4 HOT3, 65% Fuel, Cruise 70% TQ) on the "4YA_Syria_Capture_Bases_BLUE_v28A" PvE training server - I flew for 45 minutes without issue. I'm not sure how familiar you are with the Gazelle - 4 HOT3 and 100% fuel will put you over weight and the high torque load will quickly destroy the engine/clutch/gearbox. The same is true for the centrifugal clutch if you don't allow enough time for the Rotor and Engine needles to slowly sync when engaging the fuel flow lever i.e. the needles must have sync'ed between 27-34,000 RPM, BEFORE slowly moving the fuel flow lever to Full.

I don't see anything obviously wrong with the screenshots from the aerobatic server, it has no blue player slots by design and there are red F-15C slots at Anapa, Senaki and Kutaisi (it even has slots for the Hercules, so likely expects that mod to be installed). You *should* be able to click on the player slot of an aircraft you own, and then click "Breifing" to load the mission/enter the server. If you chose an aircraft you don't own, the mission should still load but instead of "loading" into the cockpit, you'll load into a 3rd person view.

Last time I entered VRS in the DCS Huey I had a descent rate of approx. ~850 fpm in a stop turn while using an aggressive amount of collective, easing off on the collective and bank allowed me to recover safely. Requirements for VRS are • speed below ETL • descent rate more than 300 fpm (R22, exact value depends on rotor diameter, aircraft weight and air density) • 20-100% power/torque applied Note: The lighter the helicopter and larger the rotor, the easier it is to enter VRS. IIRC the consensus on a helicopter forum was that realistic values for entering VRS IRL was 40-60% TQ and 0.65 of the downwash. RL pilots are trained to use lower values when flying to add a safety margin that allows for instrument lag, pilot response, etc.

The Yak's ADF audio was working last time I tested (there's a Compass/Morse toggle switch on the ADF panel that needs to be set to Morse to hear the ID code).

The hot spot tracker has a short < 3nm range, so is hardly equivalent of "labels", it'd be closer to the Su-27's IRST (but with much shorter range) which has been part of DCS for a long time.

It's a pretty map • large detailed cities/air bases • sloped runways with FSX like PAPI lighting but has WIP issues with • optimisation i.e. high textures = +24GB memory use (ATM most systems require a 16-32GB page file to avoid CTD's due to memory issues) • navigation/ILS beacons with wrong frequencies i.e. some NDB kHz set as MHz • object draw distances i.e. visible tree line pop-in I don't regret buying it but also can't 100% recommend it as it took ~2 years for Normandy to reach a "finished" state.

I don't know about the F/A-18C or Harrier* but applying the parking brake while awaiting takeoff clearance is standard procedure for the Mirage i.e. there have been 2 Mirage accident reports (2008 and 2013) were the pilot "forgot" to release the brake. https://www.defense.gouv.fr/content/download/395731/5929409/Télécharger le rapport public BEAD-air-A-2013-014-I.pdf The Harrier's parking brake throttle stop prevents such an accident. *The 2012 AV-8B VMAT-203 Flight Syllabus Guide, says a common taxiing error is • Forgetting to set the parking brake and turn off the NWS (anti-skid switch – on) when stopped.

Requires a ground mapping radar i.e. RDM, rather than the M-2000C's RDI radar. https://theaviationist.com/2019/12/09/photos-allegedly-show-greek-mirage-2000-targeting-a-turkish-frigate-with-exocet-missile-during-a-show-of-force/

Unfortunately your .trk file is missing the important "track" and "track_data" folders it needs to play back. Rather it opens like a mission file and I can't see which slot you used or cockpit interactions.

I haven't tested the Harpoon lately (waiting for the radar SEA mode) - as I find them frustrating/pointless ATM. Can you share a track.

Use a dropbox link or similar file sharing site.

You should include a track demonstrating the problem.

Not AFAIK. The default eye position has changed over the years and the new "improved" 2.5.6 cockpit has resized the repositioned the HUD text, not always for the better. It may help to reposition your pilots head and save a different default "snap view"

Strange, you should have more folders that, if using standalone Open Beta, the save path would be • Saved Games\DCS.openbeta and the path for your custom joystick and keyboard assignments, etc. would be • Saved Games\DCS.openbeta\Config\Input\[module]

• Saved Games\DCS\Config\autoexec.cfg You may have to create it using notepad++ if it doesn't already exist.

Got it, if you are talking of dissymmetry of lift, retreating blade stall, etc. https://youtu.be/iPyUZLV8duM?t=288

Do you have a source for that ? A smaller main rotor means the Mi-24 has to push out the same volume/mass of air faster (assuming Mi-8 and Mi-24 are similar weights) and is therefore less susceptible to VRS or do you mean something different when you say "stall" ?

@PSYKOnz To explain why the laser range is 8.1 nm and not 8.0 nm ---> The designator's range is defined (in the .lua) as 15 km = 8.099 nm = ~8.1 nm

̶M̶a̶n̶y̶ ̶p̶l̶a̶y̶e̶r̶s̶ ̶h̶a̶v̶e̶ ̶e̶x̶p̶e̶r̶i̶e̶n̶c̶e̶d̶ ̶T̶A̶C̶A̶N̶ ̶f̶r̶e̶e̶z̶e̶s̶ ̶i̶n̶ ̶D̶C̶S̶ ̶2̶.̶5̶.̶x̶,̶ ̶p̶e̶r̶h̶a̶p̶s̶ ̶t̶h̶i̶s̶ ̶i̶s̶ ̶w̶h̶a̶t̶ ̶i̶s̶ ̶h̶a̶p̶p̶e̶n̶i̶n̶g̶ ̶t̶o̶ ̶y̶o̶u̶ ̶?̶ Removing the track data (coverting it to a .miz) and taking the first FA-18C slot at Kobuleti - I was able to reproduce in SP, the TACAN behaviour you see in MP, it doesn't look like the typical "TACAN freeze", so I'm at a loss The TNN mission uses mist, scripting, late activated units and lots of TACANs, so it's not immediately obvious where the bug lies.