Azrayen

No no, there is no guarantee. A RWR has no idea of range. It measures received power. Radars sharing most/all of their wavelenght/waveform characteristics (such as the N001 and the N019) but with different power will simply be "felt" the same way by the RWR (same received power) at different distances (but you can't know it from your RWR). = = = = = = = On a more general note, as we're discussing RWR, I'll repost this schematics I made a few days ago: ++ Az'

Mhmm... would like that to be double checked before taking it for granted. :book: Not at all. What made you think such a thing?

Guys, winter is coming. Features too. A bit more patience :)

not anymore ZHeN.

Then manual needs to be updated to. It's part of the module, so it's also WIP ;)

Indeed. The AP stand by is just more practical because on the stick IRL.

I'm. Exactly. Personal choice, I don't like this: I use trigger to shoot, and I may need to have both the AP standby "in" and shooting at someone at the same time.

Flagrum: See a better way? The beam would be set to minimize/nullify the "jump" with standard attack profile. jojo: Yes of course, fixed beam elevation should depend on weapon type/ballistics.

I suggest a fixed reticle (at the ground-end of a fixed beam) that the pilot makes co-incide with the intended target, before pressing the "designate" button; radar then measures slant range, makes its calculations, and the system displays (or update?) the CCIP piper. All very quickly of course, thanks to the computerization. :)

And this, folks, is how it's done :) Assign AP Standby in a practical way! On the RL aircraft, this control is at the front of the stick, so that when the pilot grabs the stick he "automatically" presses it. I use the Warthog's lower trigger to emulate this in DCS.

"radar-guided launches" is not precise enough. Fox 1 or Fox 3? Sorry about that, but it's a complex issue (and that's why it's a simulator). See the attached image.

tweet, to add to your general considerations (above): :) SOP on M-2000 is no airbrakes on approach/landing (the delta wing is an efficient enough airbrake + the aibrakes kill too much lift during approach already at high AoA) Airbrakes after landing (i.e. wheels on runway) is possible but seldom used, again for not-so-great efficiency at "low" speeds (< 150kt) + possibility of undesirable side-effects on pitch (at a time when you want precise control to avoid tail strike) Airbrakes when aircraft has all 3 gears on the runway is not that effective either. = = = = = = I understand that the carbon-carbon wheel brakes of the M-2000 are quite effective at high temperature. Plus the M-2000 is a lightweight fighter compared to its peers. Both makes me think its wheel-braking is probably better than that of the mean of comparable fighters. = = = = = = Drag chute (or tail hook) on the M-2000 are "emergency" devices. A M-2000 can carry one, or the other, or none (if using Eclair pod). It's all about choice, and relates to the relatively tiny size/weight of the airframe.

I have a western perspective too... and I agree with ED ;)

It's not the roll angle, it's the roll rate (in PID only). The bug is known. Yes, for a long time. It is not yet fixed. Yes, it's annoying.

You will have to reverse this change with next update, as per last info from Zeus.

Salut, Pas mal :) Ça fonctionne ton truc mais... - La procédure de démarrage "normale" utilise le GPU ;) - Il est en principe obligatoire de fermer la verrière (ou a minima de l’entrebâiller) avant de démarrer le moteur (règle AdlA). - Le test CDVE à réaliser est le test pilote court, donc position C ("en bas") ; le TPL est lui réalisé, pas à chaque fois, au retour de vol. - Non, il ne faut pas mettre la dépollution sur marche ; sauf qd tu as besoin de dépolluer. - Mettre le brouilleur sur [] déclenche le brouillage actif ; à ne pas faire "par défaut" !! - On peut d'ores et déjà insérer des buts dans l'INU ;) - La verrière est cliquable... suffit d'utiliser la poignée qui va bien. Je me suis arrêté à 7' de vidéo. ++ Az' PS : Vu les correctifs qui vont arriver (cf Zeus), ça peut valoir le coup d'attendre une version plus stabilisée pour une mise à jour #3 de ta vid. :) PPS : Il y a une section FR sur le forum, mieux vaut l'utiliser et rester en anglais ici (enfin, j'dis ça, j'suis pas modo mais...)

Luck man: DCS: Engineers is priced at US$ 1500.- and will be released before Q3 2024. (for those who need Cpt Obvious: this post is satire)

That shouldn't change anything. Ampli switch is not a radio selector. jojo, let's have a quick test to check that?

It does?:huh: Would you have a track showing this, please?

You misunderstood my point. Yes, Airbus can use GPS as a primary navigation mean, to know where they are and where their next waypoint is. But they also still need INS (ADIRUs in fact) to get some parameters with the required precision/smoothness => Those parameters GPS can't manage, due to its very nature. Example: flight controls. ++ Az'

Yes I do. :D

Click-click AP standby.

You're probably trying to use something not yet implemented :) ZBI = Altitude Baro-Inertielle => baro-inertial altitude => standart altitude (1013/2992/760) IIRC it's used in slant range position update mode; you're probably right about bombing too (as per manual), but I can't tell from memory.

And Zeus' answer on that: Let's be patient :)

Uh? The options are the contrary... "No alignment needed" and "Disable gyro drift". So when those simplification options are ON, this DE-ACTIVATES some INS related features (to make it simpler for beginners/casual pilots). => If you want to perform the full thing as IRL, please make sure to leave those options OFF. If you've already done that, please describe what you do precisely (or make a short track and attach is there) so we have a chance to find what's wrong. ++