Whisper

It's probably a little more complicated than "SARH should have warning, must be addressed", depending on the missile launched, its launching platform, and the actual ability of the RWR to detect a radar wave change between the STT lock and the actual launch, if such a change actually exists for the considered launching platform radar. I'm no expert, but having cases of this launch being not detected (by mean of radar pattern change) by a 80's RWR for SARH missiles seems plausible to me.

Edit : wrongly read the op. No further comment

Stop doing things in the sim that nobody does IRL and shout "it's unrealistic!". We don't know the IRL behavior, actually, since nobody tried it IRL... You may very well hit an unwanted behavior, but that's because you are going way past the normal flight parameters. Labelling a whole module "dumbass" because something looks strange when using it 200% outside of it's normal enveloppe is.... weird, to keep it civil (unlike you). If you expect the sim to model perfectly all behaviors of all aircrafts in every possible (even unknown & untested) scenarios, you're over estimating the engine.

I hope you will make the effort to know what you're talking about with the rest of your drivel on these boards rather than taking an excerpt of a post to shit on it and disregard actual content. It's scary to me a simple sentence like the rc example can be interpreted as "we model our bird like it was a rc chopper". That's not what was said, but that's how you chose it to go shitting on pple. Since you seem to also like grossly generalizing on people, namely developpers, with your awesome knowledge, you look like these guys I see at work who talk very loud and force their opinion on everybody else being over confident in their own prowess. The louder you speak, the less you know, it seems. I urge everyone @work to avoid following their advice, so I'll kindly ask Polychop to simply keep correcting their bird like they are currently doing. Damned, I've been polite!

My own issue with RWR is how really close from the center the threats are displayed when radar energy received is high. It's basically on center and you cannot tell anymore the direction of the emitter.

If the lock break is actually because of ennemy beaming, it may hurt your pride, but it has nothing to do with radar being "stupid", rather, it's working as intended ;) If you need the kill, shoot from a position which prevents break of lock (notably, from below) If you need the ennemy to evade, just shoot. Actually, it probably depends on your opponent and his missile warning capabilities. AFAIK if you are versus a current incarnation of mirage, or mig21, you just need to lock in PIC, the opponent will get a lock warning but no launch warning, so launching doesn't do much in terms of making him react. If he seems to wait for eyeball on missile, then shoot. Other FC3 aircrafts may have better missile launching capabilities and get a different warning for launch, I don't know. As for switching to ENT, currently I don't have enough attempts for me to be sure it really helps with keeping lock on beaming targets. I know the pair of times I tried (when being above target), I didn't lose lock. That's not enough of a test sampling to draw definitive conclusions, but it seems to be working.

1. Afaik lock warning will happen only when going in PIC. that's for human targets. No clue of the amount of cheating the AI has access to :) 2. Monitor your target direction changes during your approach, does it go perpendicular to you? If so, your target is beaming, as explained above, and is trying to have a speed relative to you equal of the speed of ground relative to you, so that your radar filters out the echo and breaks lock. I usually change the PRF setting in this case to ENT (not BFR!) To keep PID lock. It seems to work well, as long as target is not too far away. If below target,keep PRF to HFR.

Well, we started training for guided bombs tossing with our group, it actually works. Lasing element in A10C, tossing element in 2000C. I'd like to add a scouting element in Gazelle to relay IP information. Awaiting INS implementation on Mirage ;) Success rate is around 50% Some civilians have suffered, I'm afraid.

Do the opposite : have your collective drive the slow down. By that I mean that you should first drop collective until you get a negative vertical speed, continue dropping it and keep the vertical null by nosing up until v speed returns to zero. You'll do this until you get really slow, at which point you must prepare for a sudden collective raise (and corresponding right pedal input) because she drops like a brick at a certain point.

Difference being, without GBU in mind, conceptors of INS system didn't include a way to lock and guide a bomb release from INS coordinates. Unless I completely misunderstood Jojo :)

While issue is looked at, a workaround is to lower the weight on the nosewheel by applying slight stick backpressure very soon during take off.

Dammit, I missed your answer! More lines to add than NADIR, I didn't think bout the usual ones.... Thanks a ton, gotta test that asap.

That's real Air Cavalry :)

I tried a similar thing for the RWR, no cigar :( Has anyone been able to export RWR?

342L doesn't have a Viviane sight

Beware, though. I didn't have any investment in mind. But since I got the Gazelle, my order for MFG Crosswind rudders is on the line. Expecting it for July. In the meantime, I handle it with X-55 twist, it's quite some work, but doable. Ultra touchy when facing threat in low speed conditions, though. Really a challenge.

On top of crosswind making the issue really bigger, I think cold / icy conditions also make it impossible. The planes is gliding like crazy as soon as you look at the brake lever. Anyone seen this too?

You need to map 'VTB Viewport ON/OFF' in category 'Cockpit Displays & Illumination' to a key combination, and use this key combination to have your VTB export appear in-game

Yes, I had to very far more subtle on the pedals to get it right. Flying the Gazelle helped tremendously ;)

I didn't get this behavior myself, just far more rudder sensitivity during takeoff, resulting in me snakeing on the runway on my first attempts before I could adapt. loadouts tried : usual CAP (Magx2 530x2 central tank), GBU12 support (center tank, GBU12x2, 530x2, Magx2)

Well, when close enough of the Huey, he is apparently inside the cone of the locked beam of the SAM, even though the beam is locked on the Huey. It's a radar beam, not a coherent laser light :) It has an aperture angle (eng?), it's quite logical you can be within the beam even if not locked. Though I've no clue if the actual values are realistic. I'm actually baffled the sim behaves like that, tbh.

That's actually a very good point, the Viviane could well be a game changer. It's that heavy, the gazelle structure had to be reinforced and rotor was changed to support the added weight.

Gazelle laser is not a designation one, just a ranging laser.

I've gotten the Ka50 super recently, after I got Gazelle. So I'm probably far away from the "flown correctly" part you mention ;) BUT atm I vastly prefer the trim & auto-pilot features of the Gazelle over the Shark. The magnetic brake trim of the Gazelle is to the point, simpler, and functional. I'm fighting the Shark trim all the time atm without ever finding the sweet spot I need, even going as far as catastrophic trim settings (ie : ends up in the ground). It really really has unnatural behavior to me (I'm not complaining, I just don't understand the bird yet :) ) Same with auto-pilot. I actually rarely use the speed or alt mode in either bird. The trim system of the gazelle makes the need for en-route autopilot redundant, if you ask me. The flight plan autopilot for Shark works fine, I guess. That's probably the only auto-pilot feature I've made working fine up to now ;) I kinda agree with Rogue Trooper. Outside of the super touchy part (getting into hover), the Gazelle feels really safe, because I find her intuitive. Mind you, she's my first DCS chopper, Ka50 is my second. That maybe explains, I don't have previous experience.

What's the effect of "Throttle as slider" ?