Steph21

1- There is an issue locking target with PPI display when indeed target is at a high ATA. They tried to sort it out with an option call TDC aperture IIRC. The larger the input, the bigger zone around the TDC will be taken into account when trying to lock the target. But it doesn't work that well. Easiest workaround though is to use B Scan display instead of PPI, as there is no issue using B Scan. I'm pretty sure it used to work fine with PPI before, so i'm not sure what screwed it up. It's a pain cause i like PPI better, and French Air Force is using PPI display from what i could see from pictures/videos. 2- I don't have that issue. Maybe try to shrink to the scan zone by playing with azimuth and Bar setting. Play with antena elevation also. The DO track (ghost yellow contact appearing when lock is dropped) should help you find your target back. Also you can get below the target to deny beaming opportunity. And by the way, beaming is used to talk about the target, and notching to talk about your aircraft ;)

Having the FPM caged is a bug reported here: https://forums.eagle.ru/showthread.php?p=4354911#post4354911 There's no functionality to cage/uncage FPM in the M2000C AFAIK (like you have in F-16 or F-18 for example)

When validating the update, it should move the cross to the exact coordinate location (basically it's resetting INS drift to 0)which is a bug already reported as it should move it to the point designated during the update. You seem to do everything correctly, so just silly question : don't you have the disable drift option activated ? :D Cause in this case, you will still get INS drift value on the PCN but as drift is disabled, your waypoint will be on the correct location hence it wont be updated once you validate the update. Regarding the altitude offset, i've reported it in the bug section. It's a display bug only, calculation seems to take into account the data entered in feet.

This has been fixed several weeks ago. Works as intended now as standard CCPL automatic release

Keep in mind that you are delivering Mk82 Snake Eye in CCIP with the Mirage, so high drag bombs. So use rather level bombing (as mentioned by Jojo) or shallow dive. It's not like delivering Low Drag Mk 82 in CCIP on the US plane like A10, F18 or F16. The profile recommended in the manual would work with BLG 66 in the game, but not with Mk82 SE. Level bombing at 300Ft AGL and 500KCAS works great as Jojo said :thumbup:

Is it ? cause -1-1 gives same DI respectively for Aim9 and Aim120 (with launcher + adapter) for station 2,3,7 or 8 :book:

Small addition, if you unselect RDO on PCA, DO track won't be created on VTB when manually unlocking a target

Flying in close formation can be used to cause issue with sorting. That works well against the Mirage 2000C and its RDI Radar because indeed there are no expend option. You have to wait for the bandits to come closer to be able to sort them, or sometimes you can't and have to wait for the merge. Don't compare a F-16C Block 50 and a Mirage 2000C. Mirage 2000-5 can be compared to F-16C Block 50, and has expend option and Fox3 capability.

NCTR depends indeed of range but also of Target Aspect, so it's not always available. It's the same for all aircrafts. For example, won't be available with Beaming/Draging targets. But it works fine on the Mirage 2000C, try the guns guns guns instant mission and you'll have it for example.

See screenshot from the manual. It only appears with weight on wheels.

Align the inverted T, displayed at the bottom of the hud with WoW, with the horizon bar. You'll then have the correct pitch for take off rotation and aerobraking when landing ;) it's designed for it.

It's available and should be used for all approach. Mirage is way easier to manage than the F-16 imo.

From the -1 of the block 50, nav/position lights are powered by the emergency AC bus n°2, so powered by main generator or standby generator or EPU generator. So clearly not by battery. Might be different on other block that you saw with your friend. Seems that no external lights are powered by DC power in general from the -1

Double circle means you are in the No escape zone. So yes it varies with speed and altitude.

You wont be able to see aircraft that have no datalink unless they are seen by the radar of other aircraft connected to the network like Awacs or F16/F18 for example.

1- M2000C doesn't have datalink. Only the 2000D and 2000-5 2- VHF / UHF Radio code and easy comms have nothing to do with datalink ;)

It's not really about complaining because there are bugs on the Open Beta. It's more about how such basic stuff is not spotted during basic testing. It's not like it's a bug appearing when you do a very specific set of actions in a specific set up. We are talking of stuff that you can notice easily when jumping on a instant action Air to Air mission and do basic flying.

Yes it is, or fly on the Stable. I haven't updated the Open Beta yet, but how the hell this: DCS F-16C by ED Added ability to create new waypoints. Low altitude, Low fuel, High speed wobbling - fixed can cause everything listed in this post....amazing

https://forums.eagle.ru/showthread.php?t=247769

Razbam mentioned they plan to do it and French Air force mentionned last year they were very interested by it if it can be done quickly. No news since, so there's a small hope. But Razbam made it clear : M2000C has to be finished first.

I provided an example in our discussion with Ramsey around INS update : https://forums.eagle.ru/showpost.php?p=4351072&postcount=12 Took also some screenshots at several distances. Will create a thread about it in the bug section. Haven't tested it with AG weapon selected though, only with OBL.

Yep, this bird is a total mess on the ground. You're even supposed to slow down to taxi speed before enabling NWS after landing (<30 kts) The 60kts are mentionned for take off.

What are you calling amplifying L16 data ? If that's the PC71 shown above the datalink track on your screenshot, it's referred as Bugged Target ID in the manual, hence my answer. It shows the Datalink ID of the friendly aircraft that is targeting this datalink contact. It's only shown on the FCR. If it's not, then i've no clue what you are talking about :thumbup:

Works only in Nav mode for INS Update. The switch handles Magic seeker in AA or AG mode.

Yes i've disabled INS drift on purpose. I have the same behavior with drift enabled, except of course that waypoint '+' is drifting and getting back on perfect position once update is validated (whatever the update precision).