Ramsay

I've known there were range penalties i.e. for look up, look down and cold targets Not sure how much is new, as I took a break from the Mirage to explore other modules and only started a A2A Mirage refresher on the 24th of July. Razbam are working on a more realistic A2A radar but AFAIK, it's not likely to be ready for a couple of months.

The NS430 2D pop still works in the Mi-24P for me - hot ramp start, Batumi, Steam Open Beta 2.7.5.10869

What is, Viewport export ? I play using a 40" TV, is that realistic ? What makes the Mirage's VTB export particularly egregious, the fact that it works and is useful, or that others don't play the same way as you ?

Shame, it's been along standing "feature" of the module, I always assumed it was Razbam's version the A-10C's “Hud Only View” where MFD's appear in the bottom left and bottom right corners of the screen. AFAIK only the Grim Reaper's ever misidentified the Mirage's VTB export as a helmet display. It's not a cheat as not everyone has the space/money for a home built cockpit with 2-5 displays, etc. or have the eyesight to easily the read the VTB. IMHO just because something is accessible doesn't make it "bad" and VTB readability shouldn't be restricted to those with the biggest wallets because someone else's realism might be offended. I thought this debate had been put to bed years ago (an export isn't a cheat if it's presenting the same info as the real cockpit and single monitor and multi-monitor viewport exports should be equally equivalent/valid) but it seems not. Really disappointed if Razbam are considering putting time and effort into making viewport exports less useful/easy for single monitor users. Do you have a source for this info or are you simply speculating ?

OP did but it was placed in the "wish list" section, if you read one of the last posts in the original thread, you'll see it was suggested that the "bug" section may be a better place to report the problem. Seems reasonable (after the OP has been bumping the original thread for +12 months), to ensure ED are aware and it gets placed on a bug tracker, etc.

Testing in SP I wasn't been able to reproduce your issue, I tested using the AI F-5E and had an E3 providing link-16/bogy dope calls. I flew the M-2000C (France) and F/A-18C (USA) with friendly USA F-5E's escorting the E3 and enemy Russian F-5E's spawned (via MOOSE) as a Redfor CAP on the Caucasus map. • Redfor F-5E's IFF'ed as unknown/hostile • Blufor F-5E's IFF'ed as unknown/friendly (positive IFF depended on distance/aspect) As QuiGon said, I'd need a track file to see how you've setup your mission, coalitions and supporting assets to test further. Tested Open Beta 2.7.4.9847

AFAIK the initial DCS Mirage 2000 release had a mix RDI, RDM and Mirage 2000 D elements, this wasn't so much by design, as the difficulty in getting solid information of what the M 2000C RDI did/did not have. The French AdA was significantly impressed with what Razbam had achieved, that they saw an opportunity to work with Razbam and use DCS a training aid. With the addition of DCS's 2.5.x ground radar and detailed SME information from the AdA, Razbam are fixing errors and updating the DCS Mirage 2000C to represent a older M2000C as operated today by the Armée de l'Air, Escadron de Chasse 2-5 Ile de France (a training squadron) i.e. with a more modern VHF/UHF radio, NVG filters fitted to the instrument lighting, realistic radar modelling, etc., etc. It's been a FAQ this last year - AFAIK the short answer, is NO and not as part of the current module. Razbam's current focus is to finish their existing modules (M-2000C, AV-8B N/A and MiG-19) and later work on their "planned" F-15E, MiG-23ML, Pucara and BO-105 projects. Comment Long answer is "perhaps" if Razbam ever get the opportunity to create a Mirage 2000-5 module for the AdA i.e. distant future, there are no current plans.

Perhaps you're thinking of "VTB Viewport ON/OFF" that shows a VTB overlay in the top right of the screen (IIRC it's not bound to a key by default). IIRC the graphical effect of raising/lowering the helmet sun visor was removed as it didn't cover the players full field of view in VR. AFAIK the Mirage's visor has never display the VTB by itself and VTB export is purely a DCS option to help playability/readability of the VTB. Viewing the Grim Reaper's video confirms he used the VTB Viewport, https://youtu.be/xHnRi1RVYCM Tested Open Beta 2.7.4.9847

I'm not 100% sure what you are doing as, AFAIK (from RedKite's videos) the ARC-U2 (R828) ADF uses preset channels in the 20-59.9 MHz range and drives the thick No. 2 ADF => needle. While the ARC-15 on the left hand wall has adjustable dials in the kHz range and drives the thin No. 1 ADF --> needle and is used to track NDB's and inner/outer markers. Assuming you are using the ARC-15 to tune to the aerodrome markers, I can't reproduce your issue. So yes, there is a reason why ED ask for a short track when it's possible. Tested in Open Beta 2.7.4.9847, hot ramp start, zero wind.

More than 4 JDAM shouldn't be an issue. • Use the TGP and UFC TOO to create target points T1 to T4 • ARM the GBU-38's and select T1 to T4 on the ODU. • Fly your preferred attack heading and altitude towards the target area. • When in optimum range press and hold pickle until all bombs are released • Break to avoid overflying the target area. AFAIK TOO is WIP so YMMV. This video from TEACypher shows him using the TGP and TOO to drop GBU-54 x2 but it's the same method to drop GBU-38 x4, etc. Attached is a short track of me using the TGP and TOO to drop GBU-38 x4 Tested Open Beta 2.7.4.9847 AV-8B TGP TOO and JDAM, 2_7_4.trk

... with no mention of airfield altitude or air temperature - how are we supposed to help you or check what the "charts" say for your weight ?

You designate a target (T0) with the TGP, then use TOO to assign it to an available target point i.e. T01, then repeat (IIRC a max of 10 target points). See TEACypher's video for more detail on using TOO APKWS isn't really designed for that, they are relatively short ranged and have to be supported until impact. However it is possible in DCS using active pause from 4-5 NM (perhaps you can do better). • Create target points T01-T05 using TGP Designations and TOO. • Select T01, check TGP is slaved to designation. • Use WINC to step to the next target point T02, check TGP moves with it, repeat for other target points. • Select APKWS (A20) • Step to T01 using WINC, etc • Lase with TGP • Fire 1st APKWS • after ~5 sec fire 2nd APKWS, repeat for the others with 5 second intervals • Watch the TGP, when the 1st APKWS hits - use WINC to step to the next target T02, repeat WINC for the others as each target is hit. AFAIK it's not really practical IRL, as you'll only get precise TGP coordinates from under 10-15 NM and the rockets have a max range of ~11 km (7 NM) when fired from an aircraft (wiki). Attached is a short track - unfortunately it's not very efficient as it's a while since I've flown the Harrier. AV-8B TOO and APKWS, 2_7_4.trk

Please share a short track including your cold start and an attempt to engage auto-hover.

Same here (no issue). Only thing of note is that your track shows you have Easy Coms enabled in Options>Gameplay (Sometimes requires the coms menu #(\) key to be used instead of push to talk, varies between modules). Tested in Open Beta 2.7.4.9847

Map from same skydiver site http://www.skydivecyprus.org/map--directions.html

Doh..., yes you're correct, I forgot the AI treats helicopters similar to a jet with hot/cold exhaust aspects. (I previously tested Igla ranges vs the Gazelle by flying decreasing circles round a manpad until they started firing, hence my mistaken logic).

AFAIK the more complex behaviour you are see is because you are testing using a player controlled Avenger and the CA cockpit/UI is taking LOS, aspect and range into account to determine when the player gets a good tone/lock. IIRC the AI (igla manpads) isn't as sophisticated, I know ED have made some recent improvement with the AI's LOS, so would need to retest. I've trawled through the .lua's and databases but unfortunately haven't determined if the issue lies with the Gazelle or ED's Avenger/unit database (perhaps not updated for a 3rd party module). As you say, adding/removing the IR suppressors has an effect on the Avenger's range for the Mi-8/Mi-24. They use the ME special options tab to add/remove their suppressors, while the Gazelle uses the loadout menu - I wonder what they are doing different ? In terms of the detection range, the Gazelle is much smaller and has a single engine compared to the bigger twin engine helicopters, so it's hard to say if the Avenger/stinger is under/over performing vs the Gazelle. The Ka-50 has IR suppressed exhausts, so is working as expected.

AFAIK DCS aircraft have only 2 IR signatures Normal (parked or engine running) and Afterburner, and as helicopters don't have an AB, they have a single heat signature. Do you have a track/mission loadout from another module where IR suppressors have an effect on range, perhaps it's being treated like the Su-25T's IR jammer ?

AFAIK the FAA consider ICLS as a "type" of ILS and list it as such on publicly available charts. The AN/TPN-22 (Iraq 2005) is a PAR that supports ACL (AFAIK it was decommissioned in 2014 in favour of a lighter / more mobile system). A 2018 FAA example for Cherry Point, RWY 26R The AN/TPN-30 is (was?) also used for expeditionary fields, either singularly or as a linked LOC/GS pair. Certainly lighter PAR systems are a better fit for the USMC's current mission statement/profile but I'm not sure what's being used at the "home" Naval Air Stations. https://www.navair.navy.mil/node/21801

Check "Game Flight" and "Game Avionics" modes aren't set in Options>Gameplay

Totally different situation, Razbam were proposing to remove a "legacy" weapon(s) the AV-8B has used in the past and for which there is documentation. IR Maverick and Sidearm, Operation Southern Watch*, VMA-311, ~1996 Zuni Rockets, Operation Iraqi Freedom IV*, VMA-311, ~2006 * AV-8B Harrier II Units of Operation Iraqi Freedom I-VI, Osprey

The RAAF Flight Manual for the Mirage IIIO &IIID has a caution not to lower it's nose wheel onto the ground at speeds above 190 KIAS. Circuit entry and landing, page 252 Didn't find any issues (blown tyres) testing touch & goes/landing at Akrotiri RWY 28, 20°C, No wind 3x Normal MLW* (~9800 kg / ~59%) :- On speed AoA = 145 KIAS 3x Uprated MLW** (~12000 kg / ~73%) :- On speed AoA = 165 KIAS Uprated MLW touch & go testing method On landing :- • HUD inverted T aerobrake plus airbrakes until nose wheel drops at ~135 KIAS • Reset trim • Engauge AB • Rotate ~150 KIAS, HUD inverted T level with horizon line • Main wheels lift clear (VS +100 ft/min) @ ~180 IAS (DCS stiction ?) DCS Open Beta 2.7.3.8494 * CLEAN AIRCRAFT + 2050 kg Internal Fuel ** STANDARD AIR-TO-GROUND ( MT Wing Tanks / 4X MK-82S) + 2600 kg Internal Fuel

DCS doesn't model contrast lock, rather it uses line of sight, distance and (some times) time of day to determine if an object is lockable. IR Mav's used to lock at a max range of 7-5 nm with the sighting cross near the base of the target (I haven't tested recently). IRL IR Mav's can lock on shadows, etc., so difficulty in DCS is somewhat realistic but occurs for different reasons. Practice, digital zoom/fov and adjusting your attack azimuth usually helps.

TL;DR: It sounds like you may have inadvertently switched between Release and OpenBeta versions, if you are sure you don't have duplicate "Saved Games\DCS.xxx" folders, I'm at a loss. Detail: DCS saves it's files to "Saved Games\DCS" by default, if the folder is missing it creates a new one at the location. In the main DCS install location(s) "C:\Program Files (x86)\DCS World" (or similar), dcs_variant.txt is used to manage multiple saves/versions when there is more than one DCS install. For example, if dcs_variant.txt contains the text openbeta the save path is "Saved Games\DCS.openbeta". This is an example of save folders on a PC with 3 DCS installs - a default (Steam Open Beta) install and 2 legacy standalone installs (using dcs_variant.txt in their install folders).

Yes, both the Hind ($69.99) and Syria ($59.99) changed to full price at the start of Steam's Summer Sale. https://store.steampowered.com/app/223750/DCS_World_Steam_Edition/?cc=us AFAIK it's a result of a consumer protection algorithm designed to prevent dev's changing (increasing) the price just before a sale starts. If I understand correctly, ED applied some price changes the previous month and they triggered Steam's consumer protection when the sale started.