Azrayen

Missile size isn't the same. Missile launch type isn't the same.

GCI only, no AWACS at the time ;)

Neon, this is AoA-induced drag barrier. Not speed per se. This has been very much noticed (and discussed around here), and is one of the main focus of the future version of the FM.

What about them?

I'm not in favour of tweaking the HUD color instead of managing the cause issue. The ability to adjust HUD brightness feels more important IMO.

Hamilton, why not post your track?

LeVince, I already acknowledged this... ;) I agree, and this will be updated too. The "problem" is that the same word ("Range") is also used in mission editor, for the "Rayon d'action" of an aircraft; there, the translation is OK ;) This will require some coding to separate both. Axelerator, your choice :) but was your final word really needed?

Probably. Did you just ignore whatever is "written" and continue inputing? Ususally, when pressing INS (enter) button, all is well again.

Not at all. It's well known, it's not a "bug", simply not yet implemented. BTW: it's "Route Désirée", not "Roue". Route = Course/Route Roue = Wheel. ;) I disagree. TD (Temps Désiré, Desired Time) works, albeit guidances cues could use a Valium or two. If it flashes then goes away, that's because you're outside parameters for it to work. Parameters: the time to go to the waypoint should be between 50 and 150% of the desired time. Otherwise, difference is too great, the mode won't engage.

No doubt? Depends... Channels 1 and 2 each get their own elec power from hydraulic systems. If there is hyd pressure then they get electric power. Channel 3 is powered by the main DC bus (non sheddable). So AC->DC normally, or DC from battery if no AC source at all. Channel 4 is powered directly by the battery bus. Channel 5 (ultimate emergency) is powered directly by the battery bus too. The word is redundancy.

Uh uh a month... and a year. Yes automatic release is there. Aiming is still little forgiving though.

The dev (an me, because I'm curious) would probably need a track to see what was the target doing, and what was the fighter doing at the time of the drop lock. Then precise assessment (i.e.: bug or feature?) can be made. Unfortunately, I haven't found the time to do specific tests about that. I imagine a multiplayer test so that maneuvers are briefed (target & fighter). Regards, Az'

@p1t1o: I dare to think I'm a somehow knowledgeable person :smartass: And no, I don't believe the radar code actually modelizes the whole complexity of the side lobes. Just one of their main noticable characteristics (operationnaly), which is a 2nd threshold of target speed where you'll get a hard time seeing/locking it. This also all depends on PRF, and RDI offers its full capacity (range, lock ability) in HPRF. But this is also the setting where the "blind spots" are the most sensible. Plus it cannot lock (STT) in ILV or LPRF modes (this is specific to the 2000, not inherited from elsewhere; and accurate).

Hi BD, Nice "not-trailer" here :) May I suggest you use Kg for the T/O weight, fuel weight... in the kneeboard's datacards? That would be easier as such is the aircraft itself, and more consistent with the joker & bingo values. Keep it on! Regards, Az'

Magic / HUD may be updated in a few weeks: this is part of the "avionics" work Zeus referred to. I would advise to wait until this is released before attempting to update the guide ;) This is also valid re: air-to-ground procedures, BTW.

Zero : the phenomenon you describe is the correct one. I just never heard it be refered to as "blow out" (I associate the term more with ECS devices). Now, English isn't my native language so it's possible I missed something.

One of the side lobe is directed below the aircraft. Hits the ground. Comes back. This creates an echo seemingly staying at iso-distance (assuming ~ level flight) = iso-speed. This has to be filtered out. You may now be surprised all you want :)

Zero, IMO there is really no point further discussing the matter at hand until... I don't mean to be mean ;) It's just that I fail to see the point to continue to elaborate complex theories based on the current DCS FM that the dev himself acknowledged (twice alrealdy at least) to be incorrect in the high AoA regime... Kinda feel like beating an already (very) dead horse. :D Regards

Certainly not. You misunderstood what it's about. From the manufacturer: [FR] Ventilation (for a jet engine) = [EN] Ventilation, cranking, motoring.

Hi Eye candy: replace the pics on pages 1, 2 and 6: - no mixing S-530D with A-to-G weapons - pylons safeties now fixed = would no appear raised (safe) anymore inflight I disagree! 1/ No, those knobs don't manage receiving or transmitting, so writing this would be wrong. 2/ No, those knobs don't share a common label in Chuck's guide. You have V/UHF radio mode selector and V/UHF radio frequency mode selector OTOH, the E+A2 / R switches are described as related to "encryption". This is not correct (and I think Razbam did describe them as such, so the mistake is understandable). Those switches are related to the test feature (and the test button nearby) IRL. This is not implemented in DCS (nor in need to be, as far as I'm concerned). Indeed :) In fact, it's not an Air refueling external light-switch; there is no such thing in our aircraft. It's a switch linked to SERPAM system (zoom and look the texture at the base, it's even written there), which is a sort of flight recorder. This is not implemented in DCS (nor in need to be, as far as I'm concerned). ++ Az'

Well, I like polite requests better than patronizing demands. Unfortunately, it seems like we don't always got what we like. :)

OK. You described the main point of the doppler radar, and what you said about it is correct regarding the radar main lobe. Now you have to learn about secondary lobes / side lobes. Annnnd there it is. You get the reason why "iso-speed" (relative to the aircraft) targets are a pain in the ass, as are "stationnary" (relative to the ground) targets. I would advise Sedenion to look at this too, since he's "probably" :D not gonna see the code anytime soon ;) ++ Az' :) PS: That said, I don't rule out the possibility of an un-described bug to still be there. I'm also advocating for short tracks to be provided, as it makes the discussion far more concrete. And AFAIK, there is still one (known/unresolved) bug afflicting "PID lock + aircraft maneuvering frankly" situations.

^ this! I don't get why this discussion continues... There is nothing wrong with reminding caracteristics of delta wings. And there is nothing wrong with assessing something's not quite OK with the current FM. Both are not incompatible. There is not a "right" side and a "wrong" side. So. What about learning to let it go, and waiting for the update announced by Cpt Smiley? And in the meantime, I don't know... continue flying @ lower AoA on DCS? :joystick: Going out? :D

On peut (ou on devrait pouvoir), c'est une erreur dans la VF, que nous avons repérée & corrigée. Le correctif a été distribué automatiquement dans la version 2.1. Pour DCS 1.5, ce sera pour la prochaine mise à jour (en toute logique). Ceux qui souhaitent anticiper le mouvement peuvent remplacer le fichier \l10n\fr\LC_MESSAGES\input.mo de leur DCS 1.5 par celui contenu dans leur version 2.1, ou par celui fourni dans le .zip joint à ce post (c'est le même). Notez que la commande pour le Spit est libellée "Pas d'hélice (analogique)". ++ Az' PS : n'hésite pas à choisir un titre de topic plus explicite pour ton prochain ;) input.zip

Yep. Actually bumped an internal ticket about this. The night is dark and full of terror.