Tiramisu

I do not understand the hysteria in here. ED has already made a free update for the MiG-29. So why shouldn't they make a free update for the Ka-50, too? I am sorry to hear that some people had to buy the Ka-50 again to play it in DCS, but that was a different thing.

I would like to talk about some general problems I have with my AI wingman. Maybe you guys could help me out a little, because right now single player is my only viable option. - The "cover me" option does not seem to work very well. Sometimes the AI even attacks ground targets instead of bandits, when I tell him to cover me, which is a useless and dangerous behavior. For the most time me and my AI wingman are fighting on our own, without helping each other, because the communication between us is extremely bad. I am not even sure how his target designation works, so I am not able to predict who he is going to attack or where he is going. I loose him out of sight very easily during combat. - Sometimes my wingman refuses to attack bandits that are in front of us, even when his radar is on. I think the reson might be that this coward is breaking offensive too early, in case I give him the "engage bandits" command after he has been already targeted by a hostile missile. Then instead of at least harassing the enemy with his own missile, he breaks off and basically becomes useless. The problem is that I loose my wingman out of sight, if I tell him to engage bandits too early, but if my engage-command comes too late he just starts to run away from the enemy. - In some situations my Wingman constantly spams reports about (mud)spikes even when ground targets should be impossible to see (like when we are flying at 20k feet). I would like to even disable this kind of AI report in general, because it is pretty much useless. I have already selected different radio frequencies in the ME to not get bothered by other AIs, but it helps very little since my wingman is still reporting every single ground targets he is seeing (instead of summing them up or something).

Finally I have found the reason for this bug. Here is the workaround for this problem: https://forums.eagle.ru/showthread.php?t=231176

Problem: Your Voice Attack Commands occasionally do not work either because you have to repeat your command or because your command does not open the main comms menu at first resulting in wrong commands. Cause: These problems are actually bugs in DCS. The first bug is causing your button for the "communication menu" (which is \ by default) to not work after this button has not been used for a while. In this case it will only respond on a second key press, which is why you might sometimes have to repeat your commands in Voice Attack before it works. The second bug in DCS causes your comms menu to sometimes start in a submenu, when you open up your comms menu for the first time in a mission. Solution: Let's assume your key for the "communication menu" is \ and the other keys are F1-F12. Then all your commands that are using \ need some additional key commands for the workaround, i.e. instead of press "\" ...you need the following key press sequence: press "\" press "F12" press "\" press "F11" ...And that is basically it. :) The way this workaround works is that the first \ might or might not open your comms menu, but it assures that the second \ press will definitely be accepted by DCS. The F12 between both key presses makes sure the second \ press does not close the comms menu again in case the first \ has been already accepted by DCS. Last but not least F11 is going to make sure you go back to the main comms menu in case you start in a submenu. This is a simple fix, but it took me a long time to find out why this was happening and how to fix it. So I hope this helps other people. Btw.: In case you are not already using your numkeys for some important commands, I recommend using them for the comms menu options instead of the default F1-F12 keys, because they might interfere with your camera keys otherwise. You can read the guide here: https://forums.eagle.ru/showthread.php?t=66715

It was an accident, but still it feels good to be in the exclusive club of afterburner killers. :police:

But the MiG-21 was made to startup and takeoff in a very short time, especially when the enemy is making a surprise attack or something. In such a scenario the ground crew would not have much time to clean anything.

I would also love to see an early version release. But let's give them some time until the map has reached the standards of DCS 2.5. Right now it rather looks like DCS 1.5

The MiG-21 is a low maintenance-aircraft, so a dirty canopy is exactly what I would expect. :D I got to say that despite of making your life a little bit harder in dogfights, I still have no serious problems with it. I only wish that they fixed that occasional shimmering of the canopy glass when the sun shines on it. But even this is no real issue for me.

The Mosquito sounds pretty neat. Maybe it will finally get me into the WW2 part of DCS. But I think most of us want some big jet engine bomber. I have played flight simulators for purely civilian aircraft like the Boeing 767, which can be a real pleasure when it is realistically modelled. Put in a few bombs and it will get even more interesting! :)

I never thought it would be possible in DCS, but apparently you can use your afterburner as a weapon against lightly armored targets like trucks. Watch the tacview replay at 12 minutes and 20 seconds: https://drive.google.com/file/d/1-YxV13fvtmDQSMJle4A3uR8s0hvcqklH/view?usp=sharing You can see how I have burnt two Ural-375 trucks with my Mirage-2000 in one go without firing any weapons.

What is the MiG-19 going to be like compared to the MiG-15 (or even compared to the MiG-21)?

Hier: https://drive.google.com/file/d/107Z_pEr18jXLxw8HBOzCl_aCuA4oJQ6C/view?usp=sharing Das Replay zeigt wie ich den Nachbrenner einfach nur mit dem Schubregler ein- und ausschalte. Wenn man während des Replays das Logfenster aufruft, sieht man was ich meine.

Die Nachricht taucht aber jedes Mal auf, wenn ich den Nachbrenner anmache. Es passiert zwar nicht sofort etwas, aber nach ein paar Minuten lässt sich die MiG nicht mehr neustarten.

Danke für eure Antworten! Am nosecone liegt es bei mir vermutlich nicht, weil ich da nichts verstelle. Ich habe jetzt mal während der Mission den Logbildschirm aufgemacht (Taste Ä) und festgestellt, dass jedes mal "Engine Shutdown" angezeigt wird, wenn ich den Nachbrenner anmache. Sobald ich den Schub wieder herunterregle und der Nachbrenner ausgeht, erscheint "Engine Startup" im Logfenster. Vielleicht hat dieses merkwürdige Verhalten etwas mit der Mission zu tun, denn bei anderen Missionen hatte ich früher nie so große Probleme mit dem Triebwerk.

Ich habe auch einige dringende Fragen: 1. Ist es wirklich nicht möglich die Verzögerung vor dem Abfeuern von AA-Raketen zu umgehen? Das hat mir schon ziemlich viele Abschüsse versaut, dass ich den Feind vorher mehrere Sekunden lang anvisieren muss. Zumindest bei der Su-33 weiß ich, dass es einen Launch Override gibt. Dann müsste es das bei der MiG-21 vielleicht auch geben. 2. Wie kann man Treibwerksschäden verhindern? Laut meinen Missionslogs hat mein Triebwerk ständig Probleme und geht nach einer Weile aus, obwohl ich negative Gs (bzw. 0 G) vermeide und meistens unter 1 Mach bleibe. Als Beispiel hätte ich hier die Tacview- und Logdatei einer interessanten Mission anzubieten, die ich leider wegen dem Triebwerk vorzeitig beenden musste: https://drive.google.com/file/d/1r5ucoShHXEqtqCS9_l55yzHGssNMgsxI/view?usp=sharing (Mein Callsign lautet dabei "Purple Shrapnel".) Schon nach einer halben Minute wurden in der Logdatei die Ereignisse "Engine Shutdown" und "Engine Startup" aufgezeichnet. Ich musste zwar selber erstmal keinen Restart durchführen, aber die Probleme hätten eigentlich gar nicht erst so früh auftreten dürfen, weil ich bis dahin nicht mal extreme Manöver durchgeführt hatte. Und so ging es dann weiter, bis ich irgendwann nach nur etwa fünf Minuten zur Basis zurückzufliegen musste. Ich hatte da nämlich gemerkt hatte, dass mein Afterburner nicht mehr die volle Leistungsfähigkeit hatte, was meiner Erfahrung nach ein Zeichen dafür ist, dass das Triebwerk der MiG-21 kurz vor dem Kollaps steht. Wäre echt nett, wenn mir jemand weiterhelfen könnte. :thumbup:

Bei mir werden schon ganz zu Anfang die Replays falsch abgespielt. Selbst wenn ich kein Replay abspiele, verfällt die MiG beim Missionsstart in dem Zustand, in dem sie zuletzt in der Mission davor war. Wenn ich z.B. in einer Mission fest am Steuerknüppel ziehe und dabei umkomme, dann macht die MiG beim Neustart der Mission von alleine eine ähnlich wilde Bewegung. Da werden anscheinend die Steuereingaben nicht richtig zurückgesetzt.

Will the ED engineers find some inspirations from the MOOSE framework or any other community work?

You can easily find this out yourself, if you use the Compare-Plugin in Notepad++ (for installing it you can use the plugin manager). Try it! :)

Yeah, me too. ;) I just wondered why DCS would not allow SPAAA to be used against those weapons. Edit: Oh never mind. I just confused you with the other posting user. :D

Tugunskas do not work either. AA cannons can take out missiles or even bombs in real life by radar-locking them. In fact this is one of their main purposes like you can read here: https://www.quora.com/How-effective-are-anti-aircraft-guns-against-todays-aircraft-Are-there-any-good-enough-to-destroy-bombers-or-other-aircraft-from-the-ground Is there any reason for this restriction? HARM missiles do not seem to be that fast. I mean the SPAAAs in DCS are not even trying to shoot at them.

For me it works. You just have to convert your sound file to ogg. E.g. you can use the VLC player for converting it in a ogg-file.

Nachdem ich das jetzt ausprobiert habe, muss ich sagen, das ist ein richtig geiler Tipp!:joystick: Früher bin ich mit der MiG oft rumgeeiert, weil ich nicht genau wusste, in welcher Richtung ich nach Feinden Ausschau halten soll. Jetzt bin ich endlich in der Lage herauszufinden, wo die Action stattfindet. Gerade eben konnte ich sogar, kurz nachdem meine Turbine den Geist aufgegeben hat, eine F-5E-3 aufspüren und mit einer Rakete abschießen. Was für ein geiles Gefühl! :D

Is it possible to use anti aircraft guns like the Russian Shilka against air to ground missiles like the AGM-88C? I do not like to waste SAM missiles to intercept them. So for my SA-10 I have set "Engage Air Weapons" to off, because I only want them to attack aircraft, while the Shilkas are supposed to shoot at the AGM-88s comming close to them. Unfortunately the Shilkas are doing absolutely nothing. Even when I put a radar unit in the group of the Shilkas, they still do not intecept the AGMs, that are flying very close to them.

It seems like this is even a general bug, so it can also occurs to other aircraft. So please excuse me, if this bug is not caused by the MiG-21 in particular. Anyway this bug needs to be fixed and I hope it will get redirected to ED, if it turns out that this is not caused by the MiG-21 itself. You can download the bugged mission here: https://www.digitalcombatsimulator.com/de/files/myfiles/ In that mission you will find a MiG-21 of the red coalition and ground radar of the blue coalition. The MiG has a CAS-task to destroy the radar, but it ignores it. Even if you delete both units and set them up again, the bug will still occur. In case you wonder how to recreate this bug: Set up a CAS-mission and set a "Hawk ... MPQ-55" radar of a nation like Bahrain as a target for that aircraft. Then everything will work perfectly and the MiG will attack it. However, if you change the nation of that radar group to USA and set it to a patriot radar (which is not available to Bahrain), then the bug will occur. It will corrupt your whole mission file in a way that you cannot use that file any more, if you want to use CAS-missions. I hope my bug-report will help to prevent frustrations for other users. :)

I do not know why the MiG-21 AI sometimes refuses to attack ground targets, but it starts to get really annoying. I have set up a CAS mission and gave them a proper loadout, but they either turn away from the target or they go RTB instantly after mission start. In other missions the Mig-21 AI does not have these problems, even when the setup is the same. So this looks very much like a bug. Edit: Maybe this bug occurs, when you change the nationality of a target, even when it belongs to the same coalition. Also the bug remains, even when you delete the old units and create new units. In that case you have to create a whole new mission from the scratch.