All Activity

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)?

http://[URL=https://fastpic.org/view/126/2025/0924/_d51a97492533233c8922bf6d3939ca48.jpg.html][IMG]https://i126.fastpic.org/thumb/2025/0924/48/_d51a97492533233c8922bf6d3939ca48.jpeg[/IMG][/URL]

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

I've experienced the same in the Instant Action, cold and dark flight. Regards, John

Back when I was on non-FFB base this has practically eliminated the twitchyness of the Instant trim and made me fly a lot more stable when trimming often. Instant is preferred to others as it doesn't lock you out of maneuvering until you center the cyclic, but the twitching on trim does make inexperienced people think they are doing something wrong and can introduce slight PIOs. Having this Fade In/Out method is the best method anyone has done so far to ease out the trim transitions for non-FFB users and I'm willing to bet that's still a high majority of users as FFB bases still aren't really the cheap option. So yeah, long way for me to say that I'd really like this to be added, even if I won't have use for it

Hmm, i will try to do that as well. I will share my experience if it is successful.

Will the AI version be available on your discord please?

We haven’t made many changes to the headset firmware or the client. What if you roll back to version 1.41.2v? Does the issue still persist?

Тяжёлые условия службы на земле))

Let me know if the shortcut key doesn’t work after you enable “controllerless mode.”

I asked the team for a better explanation, 1. Lamps indicate IGNITION (right and left), 2. At 35% N2 right ignition switches off, lamp off. 3. At 50% N2 left ignition switches on, lamp on, APU disconnects from right engine and starts idling. 4. After approximately 10 seconds, left engine starts to spool-up. The main thing to note here, using the lamps to judge if the start up sequence is correct is not a good way to go. Basically the time between two lamps does not correspond to timing in manual. This is the time engine spools-up from 35 to 50%. I hope that helps explain why we are confident the timings for the engines are correct in DCS. thank you

I have been landing and taking off from Holzdorf's aux grass strip without any issues. Even with a full tank and A/G ordnance she'll take off in military just fine. A grass runway is never unprepared. Quite the contrary.

I reported this in the ED Discord as well. Latest update is that they’ve replicated the issue, it’s been reported, and they’ll be looking into it.

You can thank him by marking his post as solution, instead of yours. Since he actually provided the solution

After some time spend in DCS and Optiscaler, I found that its good for freeflight, but definitely not for ACM combat. At BVR, can be used (with distant missile trails also blured a bit). In A-G without TGP optics, it blures units edges to much. At this time, Im considering if I want to still play such a hidious looking game anymore....

Second this. Fade in/out trim is by far the best trim (at least in my opinion) for flying helicopters. All DCS helicopters should have fade in/out.

No I did that. Waiting 30-40 seconds doesn't work if I do all the switches at once with the cage. I also never disable the main gyro switch, as that is usually an extra step for testing, and I'm looking at doing the fastest startup scramble time as possible, which means I'm trying to get the Gyros warmed and aligned, the AFCS damper test done, and the fast alignment completed all at the same time, which In theory should happen if I use the cage.

I am confused. You mention you know differential stabilator is shut off with lowered LEF then mention that they are only roll? They are not, above 24 degrees you still have +/-5 degree aileron deflection. Yes the aileron rudder crossover should be modeled for high AOA. Understand that any “ARM-150” actuator is reserved for dampener system as they are the fastest actuators available. For example stabilizer ARM-150 has 3 degrees authority. The aileron-rudder crossover box is simply high jacking this actuator to reduce adverse yaw/roll reversal, which is the reason it was added in order to make MiG-29 safe to fly at such high AOA.