Azrayen

Sure :) Nope. ~75 % of the lift of a wing comes from the depression ABOVE the wing, not from the surpression under it. In a typical stall, the airflow doesn't "stick" anymore to the UPPER surface of the wing (due to AoA > max(CL)), and this is why you "fall" : because you lost the depression above the wing. Not because you lack surpression below it. And there is no issue re: lack of thrust. Do not confuse lack of acceleration and lack of thrust. I beg to differ. Wings aren't the same, and this plays quite a role.

^ this :)

The VVI lower limit is currently too high (except in APP mode). That's a reported issue, already. While waiting for it to be fixed, beware of it ;)

Yes, bad idea. In approach, they won't slow you that much. But thy will kill your lift. Something you don't want. At standart AoA for approach (14°), your entire delta wing is a much more efficient A/B.

1 & 13: Always let it to 5W, the 25 position is not available / never used on this aircraft. For the rest, after a quick search: https://forums.eagle.ru/showthread.php?p=2640983 :book: ++ Az'

And it's doesn't seem weird to me that it does. UNLOAD the bloody thing to let it fly again. :pilotfly: You have Velocity Vector and Energy carets in you HUD. Use them! :detective: Why do you seem to think this isn't already in place? :smartass: Oh, and BTW, I believe "the team" has professionals in it, too ;) Look for "Meet the team" topic :book: AI use a Simplified Flight Model.

This is why I wrote "rule of thumb". It's meant to be remembered by the pilot, I'm not describing how the FM code works. And I agree with you, except that I think power (trust) is not the issue. Drag/AoA is. The load factor differs, but for the rest I'm not sure I follow you...

Errr... you're probably mistaken there. :detective: I agree there is a problem in current FM, as you described it. But it really is related to AoA (and induced drag). General rule of thumb: Stay below 15° AoA: thrust > drag = you can accelerate. Go beyond 15° AoA: drag > thrust. Now, currently, there is indeed too much of an effect; this can lead to ~irrecoverable situations if you find yourself low and slow: you don't have enough altitude to trade when you try to unload (go 0g / lower AoA). As your former F-2000 pilot said, the aircraft should be more "gentle" and remain more recoverable (given that the pilot do what he needs to). :thumbup: ++ Az' PS: AF447 was lost between Brazil and France because of AoA, not speed.

Here you are. :) 1/ PID 2/ PIC 3/ PIC/CCM. If need be, those are taken from a short flight whoose track is also available here. ++ Az'

Errr... Not quite. You should aim for 14° AoA (use dedicated brakets in the HUD as guidance for your velocity vector). If you're on glidepath and at 14° AoA, then your speed will be the proper one. And its value will depend on a variety of factors (aircraft weight being the most obvious) so it may change at each landing.

Ah, I see that the recent arrival of an aircraft across the Channel boosted interest for it in the UK :) Nice article! :) Although they share a "family name" and the delta configuration, IV-A and 2000 are completely different beasts. The IV is an oversized (2 times scale) III. The 2000 is 2 generations more recent (III - F1 - 2000). Nevertheless, same company... and tech/mind. For example, the IV was a test bed for the first applications of the FBW tech. It helped later Concorde developpement... and of course laid roots for the later-on 2000's "full" (all axis) / "exclusive" (no mech back-up) FBW tech.

Wow. Did you have such a bad day? I'm sorry if it's the case. Otherwise, humor is free. As is speech BTW. Good day! :) Yes there are. Better refresh rate (already written above) before launch. And quicker launch as the missile doesn't have to wait for the radar to switch to STT as this is already done. ++ Az'

You pressed Shift key during start-up. It does make SF prompt the activation window.

Surely the answer must be "in 2 more weeks".

The USAF never did that.

The manual is outdated on this. It's a knob to set the VAD. It is not a heading selector per se.

Even in 2.0.5.3521? The one that is out since yesterday? If that's so, maybe you have conflicting inputs => check your options/controls settings. Think Gamepad, 2nd mouse... anything plugged to the computer that may send inputs to DCS.

Au moment de l'achat.

I believe this is on the todo list (nice things to have - when time allows) for some time ;)

We all do AFAIK. Where is the sun? Where is the sun glare? See the link? Oh my, that's a probable bug. But nothing to do with the aircraft. ;)

Old debug thingy to be removed IMO ;)

Right

It's not a "simple" trim reset, it's a full FCS reset button. But sure, it also resets trim. Now, a simpler way to achieve OP's goal (and a more realistic too) is to use the AP standby trigger. I advise to map this on a button accessible while flying, because its purpose is to be presed while you have your hand on the stick. With the HOTAS Warthog, I use the "trigger" at the front base of the stick. AP Standby => trim reset. And it's mapped (or should be!) so it's readily available.:)

*or downgrade to 2.0.4

Yes.