myHelljumper

The manual is in your install DCS World/Mods/aircraft/M-2000C/Doc/DCS M-2000C Flight Manual EN.pdf The mirage can't carry Mk-84, the AG weapons are Mk-82, Mk-82S, BLG-66 (belugas), GBU-12, GBU-16, GBU-24 and rocket pods. There is not mixing possible IRL, no BLG-66 with rockets, no Mk-82 with GBUs, nothing. As I said, you can only mix magics and gun with one other type. Right now there is a bug were some mix are working were they should not. I would advise you stay away from the Grim Reapers if you want to really learn the plane, their tutorials are often not accurate and sometimes they just give wrong info.

I don't think they are up to date with most of the last changes, you can do them but if you stay stuck on something, most likely it's because it has been updated. I would advise you to read the manual that comes with the module as it is almost up to date with all the changes, or, as you already have, use the chuck guide that is easier/lighter to learn. IIRC the info below is correct, but I might be misremembering some stuff, so if I do, please someone correct me :). So, the aircraft has been designed in the 70s as a interceptor with secondary AG capabilities. This means that memory and computing power was limited. The aircraft can only have 3 weapon profiles at all times with the guns and magic profiles always loaded in the aircraft memory. This means that in addition to the magics and guns, you can only have one other weapon loaded on the plane, even 530D can't mix with anything else. IRL if you use a mixed load, the PCA would display an error message and may not be usable at all.

You can just try to switch your install to release, and test if it works then.

Have you tried a repair ? Are you on OB or release ?

Ok, I will try to test it. Were you able to do the 2 first mission of the campaign without problems ?

Are you tuning to the correct radio with the battery on ? I think you need to press spacebar to trigger the dialog. Did you read the briefing that is displayed before the mission start ?

Yes, it's indicated in a lot of places that the campaign does not work with the easy coms option, so you need to disable it.

Do you have the easy coms option activated ? Have you at minimum switched your battery on ?

It's the pull-up cue as you said, but it's bugged right now, you need to turn your radar altimeter on for it to disappear.

I think you need to re-read the bug report ^^.

Are you aligning your INS ? Are you not forcing the plane to use the "horizon secour" mode ?

I looked into the problem and comparing Sedenion's file to the default files I found where it is coming from : Those tow dashes are the source of the problem. So I made a JSGME fix for this with only the two dashes removed, using Sedenion's mod fixes it too : M-2000C Bullseye fix.rar Just put the "M-2000C Bullseye fix" folder in your JSGME folder, activated it and VOILA !

That's interesting, thanks for the info.

Yeah, Steph21 got it right :)

Hello, This one showed up in todays (2.5.6.57949) or last week's update (2.5.6.57530). The cursor position from waypoint info disappear when the distance that should be displayed is greater than 10nm, it happens with the waypoint 00 or any other waypoints. Here is a track from the latest update : VTB_bullseye_bug.trk

If you use them at night, the brightness/gain is good enough.

There is a lot of sun light in your screenshot, it's normal that the NVG are not useful in this case. IIRC the 2000 NVG gain is not adjustable, but I will let someone with a better memory than me confirm it :).

Yes you are right, the nozzle looks similar to those images.

I was not able to find markings here on AdA aircraft, it really looks like a texture bug. Also it's present in all the default skins and it is not present in the texture template IIRC.

If you look at the track you can see that the bug happens as I pass the QFE setting. I'm using the scroll wheel. To reproduce, put a hotstart aircraft anywhere and change the setting one notch at a time, while passing the QFE setting (altimeter reads 0 on the ground) and you will see it going in the opposite direction from the scroll for one notch, then goring in the correct direction again.

Hello, When the external texture was updated a long time ago, the engine exhaust nozzle color has seemed a bit of, it darker and more shiny than it looks to be IRL. Ingame : IRL :

Hello, When changing the altimeter setting, there is a bug that makes the value go in the opposite direction for one click when going to the QFE setting. Track : Altimeter_setting_bug.trk

Hello, When we are displaying a waypoint on the radar screen it's position is not impacted by the aircraft's INS drift, its position is always correct. Here is a track where I illustrate the issue, it's a bit long but it really shows the problem. I start the aircraft at _ with a class 4 alignment (4nm/h drift) and my 1st waypoint is on the tacan station at _. I setup my tacan to _'s tacan station (31X). After take-off I fly the aircraft to the waypoint and we can already see a small drift on the waypoint display on the VTB from the IDN info, but that it has not drifted from the tacan station. After that I turn away and start an orbit while accelerating time in order to accumulate drift. After 40 minutes I turn to the waypoint and you can see that the waypoint on the radar screen has not drifted at all and is exactly on the tacan station while the INS has accumulated drift. VTB_BUT_display_bug.trk

Hello, For a long time, there have been a small texture bug on the our mirage 2000 strakes. Here are some screenshots of the issue : [ATTACH=JSON]{"data-align":"none","data-size":"full","data-tempid":"temp_261443_1604840565842_720","title":"Screen_201108_135043.png"}[/ATTACH]

Yes, it's still a problem. Here is a track on the lastest OB : INS_air_ALN_bug.trk