Can I get a moderator to forward this to the Asobo/MS team and attach this tweak that was found with terrain pre-caching that seemed to fix the reported conditions? If you need a video as proof. When I land I can film it for you. Flying into OKC at the moment. Hopefully they can dig into what changed and find the bug in the algorithm. This did virtually fix my issues until the next beta.
"MeaningfulSheep475’s solution:
Ok I think I’ve found a fix. I went into the User.cfg and disabled “OffscreenTerrainPreCaching” and I have no fps drops when panning my view now
I need everyone to try this and report back so that I know whether or not this is an actual thing. And if it is indeed a fix I will start a new thread for the option to disable OffscreenTerrainPreCaching within the sim entirely".
There are multiple reports now with positive results to this tweak.
It doesn’t fix this issue. It’s a nice tweak to improve the smoothness for many in general regardless of SU version and may help reduce the occurence of this, but the massive RdrThread spike is still there even with this tweak in SU3B but not in SU2 in the exact same conditions.
It doesn’t fix the stuttering when rotating the camera - it just improves it on some hardware setups, but definitely not all. MSFS 2024 developers should focus on optimizing performance - not flightsimmers. It’s their engine, their responsibility.
We can help with testing, but it’s the developers’ job to clearly inform us if we need to change any settings - or not change anything - they should tell us exactly.
If you read what I posted. I asked for a moderator to send that report in so they can find the bug. At this point it’s only in feedback logged status which means they haven’t replicated the issue. So by directing their attention to Pre-caching they should have a narrow focus to hunt down the offending line of code. If that’s not the way it reads. I can always edit it.
I understand what you mean, but the pre-caching thing is unrelated to the cause of the bug, because it happens with it both on or off.
Yes, you might get better performance in general and it may recover quicker from this RdrThread spike thanks to the better performance overall, but it’s not the cause.
If I keep the precaching on ultra and turn my terrain LOD to 10 and don’t get the issue, does that mean that terrain LOD is now the cause? Or maybe if I turn my grass setting to low?
Can you see my point? You’re trying to point to the cause being a single setting that has already been disproved as the cause.
Every setting you change will have various effects on performance, and as this is a performance bug, it will have an effect on it too.
117 votes and feedback logged. Time to think moving this into Bug Logged section Asobo? It’s obvious there is a bug. Multiple videos presenting with it and now it’s effecting even the big dogs on YouTube during their streams.
Just curious if this thread just haven’t had its tag updated or if the team is actually struggling to reproduce this?
Reproducing this should be very easy, as you can encounter this even in 172 when using moderately complex 3rd party scenery.
This issue has been reported as far back as May in different thread, although the recent builds made it significantly worse and borderline unusable experience.
I struggle to see how it either did not have an existing bug report or how has it not yet have new one created since this thread was created, as this is a complete blocker.
The bug-logged tag is only shown once the test team has successfully reproduced the issue. At that point the issue is turned into an official bug, and the bug is assigned, prioritized, and then worked on for a future fix.
Bug test schedules are restricted to the internal Microsoft team and not shared on the forums.
Fair point. I get the process. But ask yourself why can’t they “reproduce” it? It’s happening on stock aircraft and sceneries (watch the video). This NEEDS to be addressed and FIXED. If this makes it to the mainline SU3, it would become the joke of the year.
The test team has tested it, maybe repro’d it too, but the CMs (who have to manually update the tags) have been busy with their other responsibilities.
This forum is not the only social media platform they manage; plus they probably are planning for their attendance at Gamescom in Germany later this month. Maybe they simply have not gotten around to changing the tag.
Honestly, if they haven’t reproduced it, it’s because they didn’t want to. There’s absolutely no other explanation when this is literally happening to everyone. It’s a whole different story if they haven’t found the source of the bug, but I wouldn’t believe they haven’t been able to reproduce it, not even if my life depended on it.
So far, this topic has received 117 votes & 74 replies which is only 14% of votes for the FPS performance - VRAM bug? which currently has 817 votes and 2,820 replies.
If this was “literally happening to everyone” I’d expect to see a lot more votes & posts.
I’m not trying to downplay the issue for those are affected by it, but just because daily updates on this bug are not being posted to the forums does not mean the issue is not being worked on.
So far, this topic has received 117 votes & 74 replies which is only 14% of votes for the FPS performance - VRAM bug? which currently has 817 votes and 2,820 replies. If this was “literally happening to everyone” I’d expect to see a lot more votes & posts.
The FPS performance–VRAM bug thread dates back to November 2024, and it’s on the general forum. This thread is from five days ago, it’s on the beta forum, and like you said, it already has 14% of the votes of the other one. If that doesn’t tell you something, I can’t help you.
And I know you’re not trying to downplay it by any means, but man, let’s not deny the reality in front of our eyes. By the way, could you share your LOD setting? From what I can tell, the bug gets worse the higher the LOD is
About 90% of threads in the various SU3 sections lack any tag. Even if we immediatelly discard half as duplicates, user errors, etc., that still leaves 80% of the issues reported either not acknowledged at all, tested, replicated or fixed. (from our POV as the users)
This points to at least one of two things:
1.] Lack of internal testers
2.] Lack of CMs to keep the tags updated.
Jorg likes to repeat they read everything, but do they? We have absolutely now way to know thanks to the above.
I know this is not something for you to adress as a volunteer mod, just pointing that out. The testers might be busy testing all of those, but we just don’t know, all we can do is report something, if you’re very lucky get atleast an acknowledgement in form of a tag and hope fix appears in a change long down the line.
But as SU3 Beta is towards the end of its cycle, you can see how the apparent lack of urgency from the MS/Asobo side on such a major, easily reproducible issue is frustrating to users.
I would just hate for this issue to be sitting in a testing backlog somewhere as SU3 goes public.
7 more votes in the past two hours and continuing to climb. What most people fail to do is report. They’ll just find work around and blame it as a “simism” or better yet as a lot more posts on here have started to show. The beta participant numbers are dropping quickly and they go back to SU2. I’ve been lucky enough to avoid a majority of the bugs because of the amount of VRAM I have at my disposal, that was until this one decided to show up and it’s not even listed in the changelog.
