Biggus

You are very likely correct.

I've posted in the Discord a couple of times over the last month with no replies. I'm just wondering whether the lack of feedback from the F-4E flap deployment is something that is fixable or a known issue? The slats give great feedback, but there's nothing when the flaps go down.

Great vid, @graywo1fg. Looking forward to mine arriving!

I had a preorder with a retailer here in Australia. This morning I received a call from the retailer informing me that the ETA had been pushed back from October 27 to sometime in 2025. They offered (and I accepted) a refund, and I've just ordered directly with Moza. At this stage I'll be shocked if it arrives before December, but some small part of me holds out some hope that they've actually got the bases in stock and they'll be able to ship it within a couple of weeks.

Every patch I grow more confident that it's not a VRAM issue... It might get worse with elevated VRAM usage, but it's not the core issue.

I've quickly grown accustomed to Jester asking about alignment much earlier than he did before. Perhaps there should be a check to see if the helmet is on and a generator is receiving power before he asks, though? Could we also perhaps have a special option to default Jester to always being prepared for flight under 50 feet? I don't mind interacting with Jester but 95% of that interaction is me telling him that we're going low and then him responding with one of the same four or five lines of dialogue in response. Or perhaps there might be a smarter way to go about managing that, like having Jester remember how low I went on my last flight, then him telling me how low we went and asking if we'd like to tell him our lowest point will be higher or lower than that?

Any MP server, and any of the SAM systems. When the Phantom released, I spent a few hours testing them on Grayflag without much to show for it. It was stated in this thread that they weren't working online (or weren't working if you didn't spawn with them loaded), so I shelved them. I'm asking now because I'm not particularly keen on potentially wasting several hours testing if that issue hasn't been resolved.

Has anyone noticed whether Shrikes work properly in an MP environment? Or whether they work after rearming?

Perhaps grip weight is an important part of the equation when dealing with an extension.

Joining the Moza discord did a lot to help with my decision. I've got five weeks until it's in my hands, so I'm sure things like hardware trim will be sorted by then.

After seeing Jabbers vid early on, I was pretty set on just building a Rhino. Yesterday I ordered an AB9. I'm hopeful that it wasn't a mistake.

Again, I'd encourage you to read the section on the HSI in the manual. If you haven't set the HSI control knobs to nav comp, the HSI isn't using the INS as the active input. For reference, when you spawn in the tutorial, your navigation selection panel is set up like this: I'm sure Jester has actually set the INS to your desired waypoint, but you have not set the HSI up to provide you with steering information for the INS.

The navigation training mission has a bit of a trap in it if you haven't done your homework. The HSI knobs are in a different position to how one would normally spawn in a fresh jet. Jester also seems to be suppressed a bit so he doesn't talk over the instructor. The mission doesn't really teach you how to use the INS. It's all VOR and TACAN. There are INS waypoints and you can ask Jester to steer you to them, but you'll need to set the HSI appropriately in order to get steering information to them. It is worth spending a little bit of time reading the manual's description of the HSI to learn how it functions.

If it doesn't pass IC, it's not a solution for all of us.

Might not just be the laptop hardware or VRAM. Things like Tacview can generate a stutter too.

Just to share my long and bitter experience guys, but I'd recommend avoiding concluding that you've managed to eliminate the bug in module x until you've spent more than a few days testing it. Full system restarts, mission reloads, flying a few missions on other maps and then returning to SA, etc. I've fallen into the trap of concluding that the bug has disappeared or module x does not seem to exhibit the issue, only for it to return in the not-too-distant future. There's a random element at play. If you're experiencing the bug, please add to one of the bug reports. @MAXsenna does that mod pass IC?

Agree that a J makes the most sense, and an S would probably be a good second choice for a naval Phantom. A module with a J from roughly the same time frame as our current E, and then perhaps a Super J or a pre-slats S would be a dream come true. I doubt we'd get both a J and a slatted S due to the flight model changes, but I can dream!

That's probably part of why it's hard to diagnose and fix.

Like I said a page or so ago, dropping texture quality didn't help me. But more power to you that you've got acceptable performance with that change.

And when you pull up and pass 900, the frame rate comes back just as quickly.

It happens in both but I'm mostly flatscreen.

For me, it's consistent. Everywhere on the map I get a large drop in frame rate as I descend below 900ft AGL. It's gotten better for me in the last few patches, but it's still not quite usable consistently. Typically I'll have 80+ fps at altitude and down under 900 I'll be down to high 30s on an otherwise empty map.

There's a third possibility - there's no fix for it, or there's a fix that requires ED to do something in the way that they build or stream textures and ED aren't prioritising it. That survey a few months back about the look and feel of the map, I can't help but wonder whether this issue was a factor in prompting the question. I'm at the point where I'm wondering about two things: Does this issue exist on Kola, and is Razbam/ED willing to process refunds for people still experiencing this bug after so many years?

Bumping this following discussion in the map performance thread. Drastic frame reduction under 900ft AGL remains an issue. Performance has absolutely improved, but this bug renders the map largely unusable for me.

That's true, ram and the loading of a vast number of textures. The latter of which I think is probably the more relevant part for this bug. It's a reliable trigger for the 900ft frame drop under circumstances where a mission will load without having the drop occurring.