Raven (Elysian Angel)

Oh thanks I didn’t know about that mod either. Finally text no longer taking up 2/3 of my screen in VR after all those years…

Yes an I’m simply using 100%/100% and still it’s the module with strongest forces, the way I have it set up…

In pretty much all documentation, when talking about a missile's speed you need to add the speed of the launching aircraft to it.

What's that? A mod? There's no such thing as "JF-17C" in real life, so I'm surprised to see it mentioned in DCS

Mine doesn’t The VPForce software is brilliant for its customisability.

Here you go: Jester - We lost cabin pressure - 20250522.trk

In one of the latest 10 Percent True interviews, he said that since the production line had stopped, the Saudi birds were taken out of his squadron so they are the exact same model: they had to give up 12 out of 24 aircraft for 36 pilots so they started rotating them out to different units too. They are very interesting interviews :-)

The FM changes are brilliant and I love them! Jester still calls out: "We lost cabin pressure!" though. I did a test yesterday where I climbed to 50k ft and when descending he panicked again... This is the exact same scenario that I used to reproduce this bug prior to latest patch.

Not according to "Muddy" Watrous, who flew Soesterberg birds out of Incirlik.

As I said, if you do that you can no longer see the top half of the HUD.

WTB pedal trim special options, PST!

Yes it’s not an absolute limit, but the documents say you need at least a few seconds for the missile seeker to lock on to the target, which should be done from 6 o’clock low within 30 degrees angles-off-tail. And it says that if you fire while pulling more than 2G this implies that you’re likely not in the envelope for the seeker to have obtained a valid lock. So you could technically fire the missile at higher G, it will most likely not guide. The question is if DCS keeps all that into account. I doubt it, since IRL the seeker got confused by reflections from the ground for example - IR seeker modelling in DCS seems extremely simplistic to me. There are other documents that have pictures of the launch envelopes in them. I just picked a declassified source that specifically talks about the 2G-rule.

That was in the previous patch (2.9.15.9408) But yes, the F-4 feels a lot more docile and precise now when taking off and landing, and while doing landing circuits. It is a very noticeable improvement!

As of today's patch 2.9.16.10523 this is still happening

That's the question, isn't it? Personally I'd love to see early heatseakers behave more like they did in reality, though. I'm sure I'm not the only one who's been hit in the face by an R-3S while I'm manoeuvring and pumping flares in my F-4 - and that's just preposterous.

The "2G rule" is well documented for the AIM-9B and every single pilot interview that talks about the missile says the exact same thing: you shouldn't fire when you're pulling more than 2G. I'll send you a link to NAVWEPS OP 2309 Vol. 1 third revision: AIM-9B GUIDED MISSILE (FORMERLY SIDEWINDER 1A) DESCRIPTION AND OPERATION (U) Appendix B talks about the 2G rule. It says: "The rule was developed when the firing envelopes for this missile were determined (see NAVWEPS OD 12663)".

Seems to: TechPowerUp lists it as the most recent version. The real-life limit for AIM-9B was 2 (two) G. Why not stick to that limit to make that weapon more interesting and realistic?

No, I'm not going to create yet another thread about a bug that's been around for years and discussed plenty already.

Off-topic here but does that also include the bug that causes the F-14 FFB to not work if it's not the first module you fly in the current DCS session? That one is also quite annoying - and has been around forever.

Someone didn't read the FAQ

I was referring to the fact that the DCS website/store uses the wrong unit, everywhere. Either you keep the unit, but then all the numbers are 8x too low, or the numbers are correct, but then it's MB and GB instead of Mb and Gb. And yes, it matters.

Except it’s megabyte and not megabit

Yes, it’s tricky. Thanks for checking my track despite its length. This is how this issue presents itself to me these days: I used to be able to see it instantly after spawning in, but now it only happens after a long(ish) flight. I’ve had it happen again in helicopters yesterday but only after flying for 30+ minutes and then coming in to land. Perhaps, but it’s a different issue then. I make regular long flights and for me it only happens in the SA map. I haven’t seen it anywhere else (I world have mentioned it if I did).

Alignment after startup takes significantly longer when the mission date is set at a pre-GPS year, that would indicate it is not active

How is that a surprise?