Lynnux

Yes, Mirage 2000 has a maximum of 20 waypoints. Alternatively to overwriting one of them, you can a) take one of the 20 waypoints which is close to the waypoint you need (just to minimise scrolling on the map, you can take any waypoint) and create a "BAD", an offset point from this waypoint. Select the waypoint in the navigation computer On F10 map, draw a line from the chosen waypoint to the offset waypoint (= to the location where you want the new/additional waypoint) Enter the distance, direction (non-magnetic, I think) and altitude difference to the offset waypoint into the nav computer To activate the offset waypoint, click the BAD button on the nav computer I use this method e.g. with a JTAC. Try it. At the beginning it seems complicated and requires some reading/knowledge but it's fun. b) try creating your own flight path before spawning the plane. Don't know if this will override the flightpath assigned by the mission, though.

The Mirage 2000C is still a fun module. Broken training missions are a pity. You can still go with auto-startup and use Chuck's guide and the manual to learn some stuff, though. I use auto-startup on most planes because all the buttons and procedures in the jets and helicopters are too much to remember for me. Also I forget them quickly when not flying for a while. In the Mirage, Jeff and Harrier you still have to click some additional buttons during auto-startup, guess that applies to all jets and helicopters with a detailed simulation. In fact, the Mirage 2000 is one of the most pilot-friendly airplanes. Quick and easy radar modes, good navigation computer, with proper ILS setup in the mission almost autolanding, long duration with one fuel tank, high cruise speed with weapon load, stable and precise flight model (helps a lot, e.g. at AAR), good chaff and flare loadout and control, built-in ECM system (jammer), ...

Late answer since I just started playing again after a longer break: it is but it's kind of a seperate mode now. I think it's described in the radar section of the manual. A description of changes is here, you'll also find a link to the updated manual (or better look into the doc-folder of the M2K aircraft mod): Forget what I wrote above. The new manual still states the same concerning firing conditions and it's possible to fire the missile in the least restricted domain (before TIR appears). Just tried it.

I did ship hunting yesterday and created an additional waypoint during flight where I approximately expected the convoy. Slaved the TPOD to the waypoint and by coincidence already saw the ships. Not exactly knowing if this is really the case but I expect the TPOD to use a gyro to stabilise in this case and not the captured picture. Otherwise it couldn't "stay on target" when masked / out of gimbal or when not having enough ground detail (yet, e.g. sea or cloud layer at longer distance). Similar to the AGM-88B which added a gyro compared to the A model to be capable to stay on the last target after it stopped emitting. But sometimes you just want to point the your nose at the target in first place and then you might want to "release" a previous stabilisation and just follow the movement of the plane. That's not not possible in "easy mode" as far as I understood.

My favorite still is the Ducati livery, the Italian red one with the white vertical stabiliser and the "999".

As oldcrusty mentioned, Linux and windows have different timebases for the clock. I have dual boot and the Windows clock is 2 hours (my timezone with summer time) behind the Linux clock. I always have to sync the Windows clock after using Linux. Not sure you can fix this since I guess that DCS checks location and time and in Linux this will maybe always be different from Windows.

I use the analogue rudder pedals for braking, same as you want to do, I guess. I apply only one brake at a time after touchdown and always quickly switch between them. Never heard of any pilot having to do this IRL (or having the tendency to flip over during landing at all) but this works well in DCS. The Anton has a pretty strange combination of center of mass, grip and brake power. Btw. the tendency to flip is reduced with a bomb (or tank) because the center of mass will move to the rear.

Das MT Zeugs ist ja gerade in der Entwicklung und kann noch Fehler aufweisen. Deswegen gibt's da ein (englisches) Extra-Unterforum für Feedback / Bugreports: https://forum.dcs.world/forum/1144-multi-threading-bug-reports-temp/ In der FAQ steht etwas unter "Known Issues", das Dein Problem beschreibt: "Sporadic stuttering in 2D and VR" https://forum.dcs.world/topic/320618-dcs-multithreading-faq/ Übrigens, Multithreading erhöht die Grafikleistung nur wenig oder sogar garnicht, wenn die Grafikkarte am Limit ist. Kann man in der FAQ nachlesen. Am besten mal dort reinschauen, bevor man falsche Vorstellungen bekommt, was MT bewirkt.

Looks like a prototype or different Ka-50 model than the one we have in DCS. But look at the door frame on the left. It's not the rubber seal of the door but simply this "special" door frame which was updated ?

Looks like the thickness of the windows and door have been increased. There's not much change on the right side. The new window seal on the right side seems to be thinner than the old one while the new glass seems to be thicker. But on the left side you can see the rubber seal of the door now and the window is thicker. Looks like the door moved a bit back due to the rubber seal. This all adds up compared to the old Ka-50 II. I wouldn't call it a bug but there is a difference. Possibly the window position is off and the rubber seal shouldn't be visible. Your perception is good.

Exactly this is what you should do. Try all the planes and take the one that you like most for whatever reasons. No need to hurry buying stuff when you can try the WW2 planes for several weeks... 16 weeks in theory but likely you'll try 2 or 3 planes with their trial periods overlapping.

I once wrote a bug report because of inaccurate glide bombs. Turned out that I didn't give the bombs enough time to align. Beware that bomb alignment has nothing to do with INS aligment of the plane and starts with master weapon switched on.

And when launching at night time: Switch the (navigation ?) lights off and on. Assuming they've been already on...

That's just the "adversary plane" which is used on the MP server I'm playing on and therefore this problem was pronounced there. But there is a "huge" difference between caged and uncaged mode which definitely seems to be a bug. Especially when considering that the uncaged mode should ease locking the missile, not prevent it. I think this problem is still there with another airplane but not as pronounced/visible anymore. But indeed I wanted to try with a MiG-21 dropping flares and maybe let an F-18 or M2K cross from right to left. It already happened to me that the missile was switching the target despite being slaved to the radar.

And here is a simple mission which will let a MiG-15 pass in front of you from left to right. It's pitch black midnight. The MiG is invulnerable and you have unlimited ammo. So you can fire as many missiles as you want but to test the seeker performance you don't have to launch one. The MiG will ignore you. Some hints: 1. Set your throttle to a bit more than 50% before starting the mission, speeds are quite slow, stay a bit above 300 kn. 2. Switch to A2A mode when the mission has started and lock the MiG. It will be visible on the radar. 3. Assign the "T2_Press: AG Manual Mode/DGFT Missile Designator Control" to a button on your HOTAS if not done yet. So you can switch the IR seeker to "caged" and "uncaged" mode. There is an AWACS on your side but to use the datalink you have to set it up: COM2 channel "199", push right MFD "CLINK", switch from "Slave" to "Master" and switch Clink on, switch right MFD back to "HSD" It's just for convenience once you've lost the target but it may be faster to just restart the mission If you like a red target on your radar/HSD you have to switch IFF on. It's simple IFF so any mode will do (e.g. M3A). IRmissile.miz