Steph21

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.

1.1.1 is the latest, they have included MAV search info in it that was not in 1.1.0 as it was not implemented yet when it was released. So typo in the change log indeed.

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.

Still don't see a difference in latest version. Has the fix been pushed in the last couple of updates or is it yet to be published on a future update?

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).

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...