kotor633

Hi@all, the specialists for the KA-50 are primarily addressed here: I found the following video on youtube on the subject of trimming in the KA-50: In summary, the message of the video is, at least that's how I understand it, that the autopilots yaw, roll, heading are sufficient if I want to cover long distances. E.g. from WP 1 to WP 2 or similar. However, as soon as I need more precise inputs, it is advisable to switch on the Flight Director autopilot. Since this refines the entries on the stick again. Is this right? Did I understand that correctly? Because I would conclude from this that it makes sense to activate the FD autopilot in combat operations. So that I can maneuver more precisely over the ground.

Hi, I watched your video and tried it earlier. Your tips are really a good addition. And I think it's great that you point out again that you have to be careful with the collective and the joystick.

You're welcome. I made the same mistake back then.

Hi, I also use DSR. Did you set both, screen resolution and DCS, to the same resolution?

Yes, I really like the analogue design. And yes, I find it easier to flick a few switches. Compared to Apache. I find typing on the MFDs too cumbersome. What I've seen in previous videos is enough for me. Then there's the monocle. You will be overwhelmed with information. I just don't like it. You don't have all that with the Mi. Those who have fun with the Apach and have no problem with it are granted it. That's how it should be. But what I will do is that later I will test Apache for 14 days. Rather, I'd rather wait and see how the Bo-105 develops. I think it will be knitted similarly simply. But that's all off topic...

Hi, Neither nor. For me personally, the Mi-24 & Mi-8 are the measure of all things in DCS. The KA-50 may become interesting again for me in version 3. But to stay with the original question: The KA-50. Apache is too complex for me, I don't have the time or inclination for that.

Hi, meine Vorredner haben zu dieser Thematik eigentlich schon alles gesagt. Nur ist die Aussage, das du der Anwendung selbst nicht mehr RAM zuweisen kannst so nicht ganz korrekt. Zumindest nach meinem Kenntnisstand. Du kannst über den Task Manager die Priorität für die Anwendung festlegen (Um es nicht jedesmal machen zu müssen kannst du dazu auch einen REG Eintrag vornehmen). Echtzeit kann ich dir sagen ist tödlich, finger weg. Aber 'Über normal' bzw. 'Hoch' wäre mal ein Versuch wert. Ich selbst habe permanent die Prio auf Hoch (48 GB RAM, 18 GB Auslagerung). Auf meinem Rechknecht läuft, wärend ich DCS zocke, noch oft youtube im Hintergrund. Ansonsten habe ich Anwendungen die ich wenig oder nicht benutze deaktivert bzw. deinstalliert. Auch der Autostart ist ein Blick wert (auch Kleinvieh macht Mist). Ich nutze kein VR. Seit ich diese Einstellung verwende hat mir DCS nie Probleme bereitet.

Hi, a look at the manual would have answered your question: "If the target lock is lost, the memory mode will continue to illuminate the target's last known trajectory and try to re-acquire it for 8 seconds." Page 490, MISSILE GUIDANCE But you write that the rocket shot you down after you destroyed the carrier plane. Then there shouldn't be a conductive radar source anymore...

Hi, schließe mich da an. Eigentlich ist war dieses Modul überhaupt nicht auf meinem Radar. Aber was man in den letzten beiden Video von Redkite gesehen hat, macht es einen doch neugierig. Das was man zu sehen bekommt ist echt gut.

Just to name a 'small' improvement, which I think contributes immensely to the improved 'feeling': Depending on the angle from which you look at the VTB, you can no longer read it. It's the little details that make the difference too.

Hi, Can you please tell us where you read that? I looked it up in the DCS Mirage manual. I can only find the following entry: "Selectable range are 10, 20, 40, 80, 160 and 320 nm. In the 320 nm setting, no radar image (HFR contacts/BFR returns) is displayed as this range is intended to be used with a DO track." Or does that mean something completely different? (Unfortunately, I'm not very familiar with the Mirage yet, but I'm working on it )

Hi@all, Maybe this will help a little more with the discussion here: Also a very good tutorial, for the Mi-8, but what applies to this module can be transferred almost 1:1 to the Mi-24: https://www.youtube.com/channel/UCcsJYdaffnVHiituz7dnogw

Hi, I've asked that in the past too. It would be nice if we could play the Red Flag campaign and Stone Shield with the Tank Killer. As far as I can remember the answer, there are currently no resources available for this (or something like that).

What does that have to do with my question? What does that have to do with my question? Can you answer my question? Or can you at least contribute something useful to my question? A hint or something? No? Then just let it be.

That there always has to be at least one joker who just blows hot air in response to a normal question in a post... Can you answer my question? Or can you at least contribute something useful to my question? A hint or something? No? Little one, just let it be!

You are right, thank you. As i said: 'permanently remove'. I know that a Mouseclick remove the camera. But you have to do it every time you step into the cockpit. And the camera has no use in DCS anyway. And my question is aimed at whether one or the other LUA file has to be configured so that the camera can be permanently hidden. And why is the F-4 called here? What does my question have to do with the F-4 or what interests me about the F-4... The Mig-21 doesn't give you a better view of the front either. And?

Hello, Is it possible to permanently remove the small camera in the front of the pilot's cockpit? E.g. via a LUA file? Realism or not: I just find it annoying. @Heatblur: Would it be conceivable that you add an additional entry in the options for this?

Hello, just press the standard keyboard shortcut CTRL+C when sitting in the virtual cockpit of the M2k. It doesn't work like it says in the manual. I also recommend Chuck's Guide https://www.mudspike.com/chucks-guides-dcs-mirage-2000c/. And a little tip: In the future, post such module-specific questions in the dedicated sub-forum https://forum.dcs.world/forum/248-m-2000/. Otherwise, I wish you a lot of fun learning the M2k.

Thanks

I agree with you.

Hi@all, Is it just me? With every update that the M2k receives, I get more and more interested in this module. Yes, it cannot compete with a FA-18, JF-17 or F-16 in terms of armament. And that means fewer options. But that also makes it a little easier to handle. And that's what I like so much about this module. But if you take a look at the (really very good!) manual, you will notice that it is not that easy to handle (e.g. the topic of air-to-gound employment or the topic of radar). You realize that you have to invest a lot of time now (I don't think that was necessary with the Mirage in the past. At least that's how I remember it). I will probably do it by deactivating pretty much all modules (except for my beloved Mi-24) so that I can only concentrate on the M2k. It's just a pity that it took so long and so much bad blood was spilled...

Hi, Replaced the old pitch and roll error model with a quaternion based model. -> What exactly is that supposed to be? What kind of change does this bring?

Fixed: Rain drops seem oversized compared to other modules. Fixed: SPU-8 - when communicating via intercom, the indication of the selected current radio station on the widget does not disappear Fixed: Pedal trim does not work if FFB is enabled. -> Wasn't there more? Disappointing.