razo+r

Have you checked the key assignements? Perhaps it got lost or something.

You got a short track perhaps? If you established contact via the ARC210, there is no reason he should stop communicating with you via that radio. Do you have easy comms off? Confirmed you are still using the correct Mic Switch?

They're probably country-specific. Did you select an appropriate country for it to show?

Welche neuen Symbole?

Probably the videos of F-18s flying at airshows taking off with flaps set to auto. So kind of a special/unique application, unrelated to naval ops.

It should be pretty obvious as it takes up half of the space.

Problem is screenshots don't tell the whole tale, there are many factors influencing the behaviour and a screenshot just doesn't show that. Thats why a track is needed. The screenshots you provided are basically useless and far from obvious as they only show the expected/normal behaviour.

Open the mission with the mission editor, open the weather tab and adjust it to your liking. Yes, the DRIFT C/O switch on the ICP. Hard to say what happened without a short track.

Yes, it is still in early access.

Turn off the historical filter (the watch/clock icon at the bottom in the editor).

Which mission? Which airfield? Which parking spot?

Well, easy to make sure if it's crosswind or not. You have wind information in the briefing screen. What's the wind listed there? As an alternative, in the main screen of the DED, if you flip the DCS switch to the right (to SEQ), you enable a wind readout below the STP line on your DED. If that doesn't say 0, you have wind.

In that case the track desynced. I will try that tomorrow. Did it say or report any fault in the debriefing? Or just general "engine failure"? How does the engine stall? Instant seizure? Slowly fading? Sputtering? Have you also tried properly warming up your engine prior to reving your engine?

Yes and later on you put it again into manual mode and pressing the "reduce engine rpm" button. That's what I see in the track.

The engine doesn't stop, you are just completely feathering the prop manually, which puts the engine to almost 0 RPM and producing no power. In the track, after takeoff, you put the throttle to Idle, switch the governor to manual and reduce the RPM as far as possible. Not sure if intentional or not. Either keep the governor on and in auto mode, or check your bindings that you don't have the prop rpm setting bound to a switch so it keeps feathering the prop.

Can't watch the track because I don't have CW Germany. If you could replicate it on another map, I could take a look.

It's at the bottom on the ICP labeled with DRIFT C/O.

Not planned so far for the A-10C.

At this point you might aswell just upload a short track (not video) of the issue...

Via the rearming menu, the same place where you select what weapons you want to load onto your Apache, like Hellfires or rockets. There's an additional slot there where you can select the FCR.

Make sure to turn off the historical filter or enter an appropriate date, then you should find it just like in the picture above.

Ne das ist normal. Das kann passieren, wenn du zu lange gerade fliegst. Dann einfach die Flügel wackeln / ein Paar kurven drehen und gut ist. Falls nicht, INS überprüfen.

Normally, at least on airfield, you have the option to select which space they occupy in the editor. Is that also the case on the supercarrier?Alternativly you could look into using static aircraft instead if you aren't intending to let them fly.

You got some short tracks for us? There can be so many variables messing around, hard to pinpoint with a description only.

Ordne die Tasks anderst an, zuerst Unsichtbar, Unsterblich und dann kreisen. Die Reihenordnung spielt eine Rolle. Zum Beispiel muss ein Tasks abgeschlossen sein, bevor der nächste aktiviert wird. Da Kreisen eigentlich unendlich dauert, werden die anderen nicht aktiviert. Oder zumindest so erkläre ich mir das.