All Activity

I found myself hit by a missile in a sortie, and lost my right engine, all hydraulics power as well as control over my right wing pylons (nice to see the damage model is still a WIP, but has cool functionalities on the way!). I managed to limp home but found out when approaching the airfield that the emergency landing gear deployment handle, located under the left side of the main panel, was neither clickable or bindable. When can we hope to see it modelled? Thank you for your time

Release Version Current version number: DCS 2.9.20.15010 Next planned update: 24th September 2025

In you're using the toggle keybinds you might need to klick the buttons in the cockpit to make it disappear.

Don't mind. I made my comment with an ironic side note - difficult to express that in words only.

Концовки 3-ри №1. Возврат так как нет топлива №2.Сбиваю №3.Не сбиваю)) Раздало 50% и еще 100% где-то недочет триггеров))

Sorry Max, the question wasn’t directed at you personally Will the AI version be on your discord when you release it please.

I've played mission 03 and were instructed to force the enemy vessel to stop and return fire if necessary. There's only a flaming frigate insight and another moving spot emitting thick smoke from under water without anything for me to engage, and I was prompted RTB. I guess the moving smoke is the target vessel destroyed before the own craft reaches the destination. Doesn't appear to be expected performance.

Hi everyone, Contrary to this thread being marked as fixed and locked, there are still problems with the cursor in the F-16. I'll copy and paste what I had written there as all of it still applies: Certain pages in the F-16 have the cursor move at inconsistent speed when changing direction, leading to it appearing to jump. It's most commonly seen when going left/right and then adding some up/down. As far as I can tell the following are affected: The HUD (for instance, CCRP, DTOS, Maverick VIS etc). The HAD page (though the cursor does move more smoothly - as if its position is updated at a higher rate compared to every other page. Unsure what the rate should be). The WPN page for HARM. Everything else appears to work as it should and motion is predictable (though the rate at which the position is updated seems to be lower than the HAD page). No other module appears to suffer from the same bug (the A-10C for instance is very smooth and very consistent, with the exact same control on my stick bound), there are also no conflicts in the control set up. The track I originally posted can be found in the previous thread, as can my control profiles for both the A-10C (which shows no issues) and the F-16CM. Here's a video to show what I am seeing (this is after a recent calibration), this video is before recent updates but still depicts exactly what I am seeing with the most recent update at time of writing (2.9.20.15010). Note the following: The FCR and HSD pages don't show this issue - the cursor behaves entirely predictably and there are no sudden rapid accelerations - all good. However, the HAD, HARM WPN page and the HUD (here shown in DTOS, but the same applies to say, Maverick in VIS mode or any other mode using the HUD's cursor), show sudden, rapid accelerations when the switch is moved in a circular fashion. When I make just max X or just max Y inputs, the cursor generally moves more slowly and sudden, rapid accelerations are less frequent (though not entirely 0, you can sometimes still see the cursor suddenly start moving very quickly). The bug appears to affect the Y-axis more than it does X. The sudden, rapid acceleration of the cursor occurs when changing direction. Towards the end of the video I show my control bindings, you can see that my control moves as smoothly as I make it move. It properly re-centres to 0 and I can move it to the extremes of either end without any observable jitter. Here's a video showing what happens when I try another module, here I try the A-10s TAD cursor and the HUD cursor - note how there is no sudden rapid accelerations and the cursor behaves completely predictably and is generally very smooth. I also again show my control bindings and test, you can see that the exact same control is bound and (aside from not being inverted) the same exact settings are used: Every other module I've tested (A-10C II, AV-8B, F-4E, F-14A/B, F-15C, F/A-18C, Ka-50, Mirage 2000C, Su-25, -25T, -27S, -33) work as they do as seen in the A-10C video - smooth, predictable motions, with no sudden rapid movement - if I move the control to it's maximum values the speed of the cursor stays clamped. It is only the F-16CM and only for the HUD, HAD page and HARM WPN page that exhibit this issue, other pages (such as the FCR, the HSD, the Maverick WPN page, the TGP page etc) show no issues.

We shouldn't have to adapt at all. This is a russian aircraft, and this variant was always historically used in metric. Only the 29G was in knots, a variant this module specifically isn't. I understand the wish to make the module easier to access by those who are used to western cockpits, and i'm happy imperial units are included, but they should in no way be the default in either the tutorials, as mentioned here, or in the manual, which hasn't been mentioned so far. I'm not sure about the tutorials, but I can confirm the russian manual is in metric as opposed to the english manual, which is in imperial units.

Thanks for the clarification @BIGNEWY

So that's what the target acquistion depress button does. Was trying to figure that one out.

I believe as of now the avionics and gauges values are set through two different settings: Avionics, through the very, much too general "units" overall DCS option and gauges through the cockpit language skins, which we'd need an option for English Metric (this is meant to be a russian cockpit translated to english, not a western cockpit), and possibly Russian Imperial.

No, but doing one by yourself is pretty easy, especially with this paintkit :). https://www.digitalcombatsimulator.com/en/files/3334369

JG-3 (one sqn 21MF, two sqns 29A) and supposedly JG-2* (at reunification 2sqns 21M and one sqn 21SPS/K) were to be the two complete MiG-29 wings in LSK. JG-9 had the 23MF and ML and JG-7 (21Ms) had been disbanded by September '89. That left JG-1 (Holzdorf, 21MF and 21SPS/K) and JG-8 (Marxwalde, 21bis both subtypes) with 21s for the forseeable future. The 21SPS/K is a PFM with the gun-pod preparation. First flight at LSK was on 3 May 1988. Induction into DHS (~ QRA) at Preschen was in 1 December 1988. In terms of missing MiG-29 bases in GDR we have Falkenberg and Altenburg for GSSD and Preschen for LSK. ______ * couldn't find anything about that in JG-2's "Geschwaderchronik" though, just here: https://home.snafu.de/veith/jg2.htm Perspektivisch war durch die NVA eine Ausrüstung des JG-2 mit MiG-29 vorgesehen.

That exactly what I'm saying to you)))! You just described the correct way! that exactly what I was trying to explain, how to make it correct) Problem is its not like that in a simulation which comes with this module/ So please fix it by implementing the correct way of things you just mentioned)

Release Version Current version number: DCS 2.9.20.15010 Next planned update: 24th September 2025

It works for me but recognises it as an SU27.

I'm not part of this. Sent from my SM-A536B using Tapatalk

Kann grad nicht deine Mission testen, aber was passiert denn mit Flag 1 wenn Flag 2 gesetzt wird und umgekehrt? Machst du die Flag die nicht gesetzt werden soll denn auch wieder auf 0 (null)?

https://printskrin.ru/i/O7ISSH will there be a fix?

I have also experienced this, but only after I forgot to turn on pitot heat. I’ll see if I can see it again with it turned on.

This is a no-brainer. Of course, we can argue whether it's "a new feature for a finished module", but that doesn't make it any less missing and a bit ridiculous that even mod has it and pro modules don't.

Yup, 5-star request right there I have no use for this either, but it is indeed the best system for regular spring loaded setups!

Hallo, könnte mir jemand, der sich perfekt mit Flags / Flagwerten auskennt, weiterhelfen? Folgende Situation: der Spieler (Beute) soll vom Verfolger (Jäger) immer dann angegriffen werden, wenn er ÜBER 3000 ft AGL fliegt, darunter NICHT. Anbei liegt eine Testmission mit den - offensichtlich - nicht funktionierenden Triggern: Spieler in Trigger-Zone + über 3000 = Flag 1 gesetzt (bedeutet Jäger ROE = Feuer frei) Spieler in Trigger-Zone + unter 3000 = Flag 2 gesetzt (bedeutet Jäger ROE = Waffen gesichert) Das ganze als KONTINUIERLICHER Trigger, damit es permanent wechselt. Wo ist mein Denkfehler? Könnte ev. jemand die Mission so bearbeiten, daß es stimmt (falls Erklärungen hier zu ausufernd sind)? Muß man was mit "Flagwerten" verwenden? Spielerflugzeug ist F-15C, müßte ggf. geändert werden. ALs optische Hilfe wird eine Grafik eingeblendet "Höhe über 3000", jedes mal wenn der Spieler über 3000 ft. (914 m) ist. Und DAS funktioniert - nur der ROE-Wechsel nicht!!! Flag Test Höhe 3000 Feet.miz

did you find solutions? I have exactly same issue