myHelljumper

As said elsewhere, it could be correct behavior. In order to have intercept symbology on your HUD you should use the police mode, it's selected by the POL button on the PCA.

Reported and acknowledged here :) : https://forums.eagle.ru/forum/english/licensed-third-party-projects/razbam/m-2000/bug-reports/289897-reported-cockpit-lighting

Too bad the mirage list is not a long as the harrier list, surely we will see that next time :). I'm sure the 2/5 move to Nigeria for Barkhane ops did not help with the SME availability...

Can confirm.

I'm not happy about this but if it's fixed later it's okay then I guess...... at least you are honest. The SME sees it form today's battlefield perspective, as Tugais said, in the 80s-90s that mode could've been relevant to the aircraft mission. It sure is in DCS, we don't have 2000D to tell us when to drop the bombs.... You guys would need to add this to the manual so newcomers know that the PI fix is bugged and won't be fixed for some time.

The AP test is not necessary for the AP to work. Do you align the INS ? Is your HUD in the M (on) position and not the Test position (1 click vs 2 clicks) ?

I think what he talk about is when you have emptied all the rocket pods, the RK3 disapear from the PCA so you can't select them to jettison them.

Yes, current behavior might be correct, but I would find it logical for all the "+" keys to work. We will see :). I understood what the left window in Delta ALT was doing, but could not bother to explain it as well as you did, thanks for that :). And that's a mind fack :D

Just take a look at the track, It's an air-start and the track duration is under 15 minutes, so it's not a INS drift problem. If I take the RB M-2000C manual procedure "Bombing with initial point" : The number 8 is not possible because the plane does not use the IP as a reference when we try to update. Then the fix range is too high and the fix is not taken into account by the plane. It's a bit tricky to see, maybe it would be easier if we could talk about it on discord, I'm available for that if you want :).

Thanks ;)

Hello, When editing the altitude of a waypoint and selecting if the it's positive or negative, only the "+" and "-" keys of the same side as the edited window are working. For example if you edit the altitude in feet so left window, only the "1" and "7" keys are working to select if the altitude is positive or negative, the "3" and "9" keys aren't doing anything. Also, when entering the Delta ALT of a BAD, only the meter input (right window) is working correctly, if you enter an altitude in feet (left window) it does not takes the input correctly. Also, the positive or negative altitude bug is present in the delta ALT edition too. Here is a track where I illustrate all of the above : PCN_ALT_bugs.trk

When doing a CCPL PI bombing run, the INS update on the PI point is not working correctly and is impossible to do. You can see in the track, i'm updating very close to the HUD waypoint position marker but the PCN tells me i'm aiming more that 15 nm from the point which makes it impossible for the INS to use the update. Track : CCPL_PI_update_bug.trk

Hello, When the INS is damaged or has been programmed to fail the ADI freezes, that's expected behavior. But we should be able to put it in the "pôle" position so it doesn't provide disorienting information to the pilot. That's the only time when the pilot should use the "pôle" position on the ADI. Track : ADI_INS_fail_bug.trk

If the INS is in off, all the INS dependent informations are still displayed. When the INS fails by damage or programed failure the behavior is correct. IMO, INS fail and INS off should result in the same loss of functionalities. As said by prowler we should loose : HUD: fpm HUD: Pitch ladder HUD: NAV data HUD: heading scale, while the aux gyro is not engaged. HUD: Attack modes HSI: compass rose freezes while it is in NAV, as long as the AUX gyro is not engaged. Main ADI: Freezes RADAR: Goes into preheat mode. Track of the issue : INS_OFF_bug.trk And a quick mission with the INS failure happening 1-2 minutes in the flight : M-2000C_INS_Failure.miz

Perfect, hope they find a solution for this :).

IIRC the APP mode is disabled when the front gear is touching the ground, I don't know if it's realistic, but I binded the seat up and down buttons to the flap switch on my Warthog throttle so it does not bother me. Wouldn't hurt to ask the SME how it is IRL tho :).

I don't think we want more than that. IMO it's great to have the SME input on the RWR with the "real" threat codes but as DCS is a sandbox, it makes sense to have most of the threats identified by the RWR.

My squadron has been using the radar altimeter for two week without having the FPS problem, so I think it's fixed. Good news :).

Yes, but the fact that the error is same each time means that there is a bug with the system. If the error was random I would agree with you :).

You should not try to look at the cockpit with the NVGs, you should look below the NVG for that.

Yes, that's it.

This is not productive and off-topic, I stand by what I said but I will stop now.

I'm talking about the 2000C not the -5, the -5 is a air superiority fighter.

IMO it fits the interceptor role better than the air superiority role. The Super-Mirage 4000 would've been an air superiority fighter. edit: of course it's not a bad ASF, but clearly other ASF like the F-15 or Su-27 have some big advantages

It did not stop the AdA from pushing it in this rôle ^^.