Akiazusa

Hi, in a night mission,I noticed the backlights for the rear panel seems not working. (I mean this switch and knob by the way) No matter how I adjust the knob or turn the switch,it always looks like this,only the WCS BIT lights up in the dark. I searched some videos online and I think maybe it should look like this when it's turned on?(pic from old BS2 video) Here is a short track.Ka50 back panel lights.trk Also here are my graphics settings in case if they are useful. This one may cause some headaches for cold start during night,hope for a fix. Thank you.

I guess I'm not the only one who got confused a lot when trying to use vertical navigation VNAV on the shark. It seems that the VNAV cue which is circled in the pic above,only wokrs when the waypoints are created using mission editor. If the waypoints are created in game using ABRIS itself,the VNAV cue will never follow the VNAV plan u created,it will just stay(guide u) to the aircraft spawn altitude. Or if u use the ABRIS in game to change the VNAV altitude of waypoints which u created using mission editor,the VNAV cue will still follow the plan created by ME and will not affect by the changes u made on ABRIS. 2 tracks: The first one,waypoint is created using ME at 500m,and the VNAV cue guided the aircraft passing it at 500m as expected. Ka50 VNAV using Mission editor.trk The second one,waypoint is created using ABRIS at 500m,and a VNAV plan is created using ABRIS,but the VNAV cue didn't follow the VNAV plan,and keep guiding the aircraft to the ground. Ka50 VNAV without using Mission editor.trk Not really a big deal,but since all other functions of VNAV pages and supages are all working as expected,only this VNAV cue on NAV page/ARC page/HSI page is not working.so anychance for a fix when there are free time? Thanks. Ka50 VNAV without using Mission editor.trk

It's known,and the fix file should be already on ed's hand 2 month ago,it's actually a new feature,which should show a red PCM on radar screen when ECM is working ,but sadly ed only pushed parts of the new files in the last update,causing the problem,according to the discord.

It's known,and the fix file should be already on ed's hand 2 month ago,it's actually a new feature,which should show a red PCM on radar screen when ECM is working ,but sadly ed only pushed parts of the new files in the last update,causing the problem,according to the discord.

The patch should including a fix for the alarm panel lights test switch,and a new feature which will show a Red "PCM" on the radar screen when the ECM system is working. Now only parts of the patch files made their way into the game,causing a Green "PCM" shows on the radar screen and is always there no matter if the ECM is working.

Clearly the Mirage 2000 dev is still working on the module,according to the discord,one patch including some fixes and new functions to the M2000 was submitted one month before the September update,but u guys didn't include it in the September update.So that's an accident,okay,and we wait another 6 weeks to see if it's in the October update,and in this update,u guys did includes their patch,but only parts of it,and break the module. WHY? So we have to wait another 6 weeks? come on

IIRC that might be some leftover things from the old version of the Mirage,where due to lack of classified info,something was implemented not as accurately as the current version,and they got updated/fixed/reworked after the collaboration between the Razbam and the French Airforce As razo said,binding the MICRoB trigger second stage is already enough. you can also bind the first stage if you what to use the virtual gun tracers. Other triggers are not used,just leftover bindings,they don't have functions.

Might because of the cold weather in the CAMPAIGN mission,try turning on the pitot heat,giving it sometime to warm up,finally resetting the FBW by the reset switch,it should fix the problem. (If you set up a cold weather in the free flight mode,you will most likely end up in the same situation.) Also check whether your dcs world is up-to-date,there was a bug in the previous version of the mirage causing problem during crosswind take off,but it should be fixed already.

I think this bug has already been fixed in the last update...... I can take off with 25kts(the crosswind limit of m-2000c) crosswind now with no problem. It has already been fixed,but just not mentioned in the game change log. Also I think the reason of Mirage 2000 is still getting update after the mess is because

Have you checked these in your Axis Assign settings? Make sure they are assigned correctly. Or maybe you can try deleting the M-2000C folder in C:\Users\username\Saved Games\DCS.openbeta\Config\Input then run the game,let the game recreate one(which should reset all input settings related to Mirage back to default),and see if it fix the problem.

Maybe try doing a repair? I'm playing the Mirage on 2.9.7.59263 and TrackIR works fine on my computer.

If the GPU is connected,some systems which are powered by the QRA bus will still be powered after after you clicking this switch(like the INS system for example). Since it's a new feature been added recently,there is little info about it in the game manual,I'm not sure if it's normal for the can't clicking it back part,maybe there is a safety lock or something,but if you start the engine then(QRA style start up),that switch will jump back automatically and your electric power will be restored,the INS will be ready since there is no need to realignment, and you are good to go.

This is because when the radar of the Mirage is scanning with 2 bars and 4 bars selected,those bars are actually overlapping each other a bit,the overlap of different bars can lead to duplicated contacts. You can use 1 bar search to avoid this.

IIRC there is no HUD display of that aside from the circle around the G and D telling you the missile is locked or not. But a continuous 650 Hz tone will sound if the missile autodirector is locked,otherwise the tone will be a 650 Hz chopped at 1 Hz. Usually you need to point the aircraft nose to the general location around the radar lock before firing the missile.

Hi, I've updated OP to reflect the data checking done for Cl-δA and Cn-δA, and listed the remaining issues that could contribute to each other.