Steph21

Bugged target ID only appears on FCR yes, you get dashed line on the HSD. I get Bugged Target ID appears in SP also, from AI wingmen for example.

So i made several tests on latest Open Beta, on INS drift value given on PCA As far as i'm concerned, 2 good news, 1 (very) bad news: - Good: Overfly update seems to give correct INS drift value. - Good: radar INS update in OBL and PI modes seem to give the same INS drift value - Bad: Radar INS update is totaly broken as far as i can tell. I'll elaborate on the latest: i've attached 2 track file from the same mission: - one where i did an overfly update, i get a ~0 Nm drift, and when i press on REC to cancel the update, drift values are removed, REC and VAL lights are off and i get back to my initial PCN window: everything is fine. - one where i did several OBL INS update, on the first one i get a 21Nm drift, REC is blinking, click on REC then a second drift value appears (instead of going back on initial PCN window) 5 Nm, click on REC again and then finally i get back on initial PCN window. I do it several times, and i still get the same behaviour. I also noticed that slant range given by radar is way off (which could explain weird drift values). Farther you are from the waypoint, bigger is the error ratio between slant range displayed in the HUD and theoretical slant range. Attached also an example where we can see a radar slant range of 16,6km when plane is at 4840 Feet AGL(1,47km) and 4 Nm (7,4km) from the waypoint. If i'm not too bad at maths it should be displaying a 7,54 km slant range instead of 16,6km I also tested it on a instant action mission and i get the same stuff (so not related to my mission). Wonder if you guys can reproduce the same stuff. Will report it in bug section if that's the case :thumbup: Overfly INS update.trk OBL INS update.trk

You might want to do a small bump up at around 5NM of the target if you can't see the target area properly, and/or you want to reduce bombs spread. But indeed, if you can, level flight at 300ft/500 KCAS is the way to go :thumbup:

Yes it's correct. It shouldn't be differentiated, as radar INS update (Recalage Oblique) can be done in two ways: with OBL mode or with PI mode, and they should behave the same. It should even be the same than with overfly, as the INS treats the Radar INS Update as an overfly update. I'll try with overfly and OBL updates using the same mission used for the PI track, to compare drift displayed on PCN. It should display the same, whatever method is used for INS Update.

Wild guess: you're starting too high. As stated in several topics on the subject, you should be low and fast in M2KC for CCPI with Mk82SE, like level flight at 300ft/500KCAS, or a bit higher and in a shallow dive (for example small bump up up to around 3000 ft and then dive 10-15 °) and still at around 500 KCAS.

Indeed you can't validate the update if drift is more than 15nm, so in my case, i have to press INS update several times to lower drift in order go below 15 Nm and validate it. Indeed once i validate it, INS Udpate resest dirft to 0 whereas it displays another drift value on PCN. My whole squadron noticed the same stuff, and we all do class 1 alignment each time. We had it on Persian gulf, but i have the same issue on any map. We noticed it while doing an INS update with PI mode activated. I have to check if i get the same issue with regular radar update or with overfly update. Track is available in the bug section regarding this issue (in the thread where several issues are reported with tracks, created by MyHelljumper).

Indeed it should be around 1nm per hour for a class1 alignment. I'm not sure drift is broken, but drift value shown on pcn when performing an update clearly is. In some missions, i stayed 20mn at parking after alignment class 1 was performed, then started up and fly 20mn for a CCRP IP bomb run. When i performed a INS update on PI, drift value shown on PCN went from 40nm up to 70nm...

It could be found on internet a while ago, might still be available. It's in French though.

You can use it go on a intercept course and work with your radar to find it. Manual DO will help you to know where to look for. For example, you would get a report that a plane was seen 5mn ago at 260°/10Nm from waypoint 3, was heading 350° at 25000 , mach 0.8. You enter those data in the VTB and you'll get on VTB an extrapolation of where the target should be now helping you to intercept it. It's well explained in the m2000 RDM manual with an example. Of course, it wont be the most useful feature. We will use automatic DO way more often. Loving the work done on the Mirage the last few months!

Nice !

Anything else added? Like radar slave to Magic as they posted a video on it some weeks ago? This week change log for the mirage is a bit empty, you might have seen more info on Discord.

I would rather have them finishing off what is already in (navigation, air/air radar...) than include new half implemented stuff...

Works fine for me too, and it can't work fine on stable version (as mentionned in OP) as MAV search is only implemented on OB :smilewink: Vertical when CNM Magic or CNM Canon selected, horizontal when CNM Neutral selected and MAV selected

That's cranking, not notching :smilewink: R27-ER are easily defeated with cranking when fired that far, if you stay fast. One or two reversal will bleed their energy and you will be in range for your Amraam. Don't panic and don't go full defensive when a missile i shot at you that far, especially a SARH one. You could also notch and get back in quickly once their lock is dropped. You have to develop your own tactics by a combination of crank/notch/pump. They've got the range, you have the ARH missiles, play to your strength :thumbup: This video is a good intro to BVR tactics with the Viper:

The Antilope V radar can only provide ACM mode 10NM for self defense, not really calling that "decent A/A capability", rather 'minimum A/A Capability''. And indeed they are not equipped yet with either gun pod or MICA IR. Never heard of M2000D mission with Exocet and ARMAT. Basically, they are dropping GBUs and launching SCALP. Quite a good recap here of current payload and what is in the book: https://www.defense.gouv.fr/content/download/559579/9683699/fiche_technique_Mirage_2000D_BD.pdf Don't get me wrong, i'm a huge fan of the 2000D. Just don't think it would appeal to the mass.

AdA is interested by 2000-5F first. So if we get a new Mirage in the near future, that will be the -5F. Regarding 2000B, i don't see the point of doing it. Only used for training basically. 2000D on the other hand would be interesting, but not sure it would have a huge success outside the French community, as it's quite limited (no guns, limited to Mach 1.45, small weapons load capacity...) compared to the Strike Eagle for example and it has not been exported.

They should have updated the stable on the latest 2.5.5 version, before pushing 2.5.6 on OB. At least Stable wouldn't be so much out dated. OB hasn't been updated in the last 3 weeks. Maybe DCS updates are on COVID-19 lockdown... We probably won't get a stable update until 2.5.6 FPS issues are sorted on Open Beta, so that could take a while! Which is a pain, especially for Mirage pilots where Mirage is broken on Stable and back to really good shape on latest OB (with further improvements incoming).

Discussion about QRA switch, what it does IRL and why we don't care about it in DCS :) : https://forums.eagle.ru/showthread.php?p=3891137#post3891137

It does show you where you should go, Up/Down/Aft/Fwd. Just mentally put go in front of intsructions given by director lights.

1. They are best employed at high altitude/high speed. Fire and then crank to slow closure speed and get below your target to prevent him breaking the lock by beaming. I don't know F-4E but IIRC correctly, MIG-21 radar doesn't have look down capability, use it to your avantage. 2. SVI and Bore are used to acquire target that are in your HUD/gun cross. BAH/BA2 have wider scan pattern (so slower to cover whole scan area). 3. Go below your target after firing. The higher/faster, the more range /energy you'll get from your S530. It's a good Fox 1 missile when launched at high altitude/high speed, with high Pk. Then by going below, dopler won't have to filter ground effect thus you'll have less chance to lost lock on a beaming target.

For approach speed it's 136KCAS +4KCAS per 1000 pound of fuel/weapons/stores. For landing, use AOA indeed

IIRC TGP zoom it's controlled by MAN RNG CW/CCW on throttle, not Antena Elevation. You can map CW and CCW on push buttons, works fine.

From ED Manual, it mentions that tracking in SAM is stronger than in TWS. I haven't notice any difference in the game though. STT lock (from SAM or TWS) doesn't give launch warning, it gives lock warning. It's sometimes enough to make bandit go defensive if they are not aware of your weapon envelop. It's used IRL for example when bandit come too close of a country border. RWR gives launch warning when it detects that a radar is supporting a missile launch.

Once FBW Gain set to SEC, it's prohibited to set it back to NORM IIRC. So basically you can just shut down the Aircraft and step out. Nice idea :thumbup: I guess it doesn't have any impact in the game, so you probably can fly without caring about it.

Just tested it, in fact MAG is automatically selected for CNM Magic an CNM Canon. MAV can only be selected in CNM Neutral. While in CNM Neutral with 530 selected on PCA, MAV could be deselected by pressing MAV on PCA, when in horizontal search or narrow search