RustBelt

That throttle picture looks like AI slop.

I have better things to review rather than pages of patch updates. To say nothing of terrible Youtube videos. That's good, I've heard no significant amount of noise. And there is quite a lot of Noise out there at any given time.

Yes usually you get Jester saying “closing the canopy” as it closes. Or you used to a couple months ago last time I did a single seat cold start.

On the Visual ID side. That’s what the Camera is for. If only you could tell jester to zoom in. Also yes, looking at a 32” flat screen image is nothing at all like actually looking at a real airplane at a distance in the real world. It’s impossible to reproduce properly on an LCD screen. Just the lack of collimation makes it impossible to tell Speck on the canopy, vs Distant aircraft, vs sneeze residue on the screen itself. To say nothing of the flattening of highlight in even a HDR display due to the rendering systems used. And unfortunately that also applies to OLED VR. The best the current render pipelines can manage is to recreate a fairly nice small format camera image. Even with ray tracing, it just can’t handle real light at a distance right. TLDR, use at least dots if not labels because it just can’t do reality justice.

I hear that a lot, but never see any real noise about it. Which leads me to assume it’s simply incremental adjustments and so not worth bothering to remember. The learning law of Primacy is no joke, and ED does nothing to combat it. Also why just do it right to begin with, is a really good idea.

If you’re going IP bombing, you’re basically doing artillery style work. Which in the real world is effective, just hosing an area with 500 pounders on ripple to make everything in a grid square miserable. The INS is good enough for that. In DCS the damage modeling makes it less worth the time to do. So it’s a mode that’s modeled, but yea don’t bother. Stick to Computer or Pilot or the Pod if you plan on hitting specific things.

Time and money spent to implement it mostly. Like every product.

Sounds like try a repair. His script may have got a hiccup in it.

The F110-400 was superior and was part of the D revision. The decision was that the reliability, fuel efficiency, and repairability was a suitable trade off to top speed since it was almost never used. (Same as disabling the glove vanes) They kept a lot of A’s due to costs and having already purchased parts for the TF-30. Only the Air Force gets to dictate exactly what they want at any expense. The Navy Air still has to fit in with the rest of the fleet’s budget limits so there’s less full fleet uniform revision. And viable spares aren’t discarded. And TF’s pulled out of A+ represented years more parts for the squadrons that stayed in A’s. Toward the end there were about an even number of in service PW and GE engines. Between A+, B, B(U), and D’s which were all squadron by squadron, or CAG by CAG roll outs.

Partially because it’s reflecting the sky in those colors too. It’s one of those challenging light effect painting madness things.

Thank you for doing their work for them. They clearly can’t.

You want to tell that to the server host not The Devs. But fixing it would be nice, and probably won’t ever happen.

Cool!

Heatblur only is required to support other ED official Modules, not User mods no matter how cool they are. The A4 mod team needs to either figure out what’s up, or figure out how to write their AI to not use cat3. Take it up with them.

If you ever figure it out, let Heatblur know.