Exactly my thoughts. Perhaps only way for Asobo to have real detail to assist would be some means in the sim (if there is not one that I am not aware off) that could capture a debug report when a user has the issue. Has relevant info on system, connection etc captured and from this they can correlate. Otherwise with this feedback thread would be shooting in the dark for Asobo to troubleshoot I would assume
26 days after the survey was opened, I wonder where we are in the journey to getting this fixed? It seems that 68% have reported significant, moderate or severe reductions in scenery so far.
I don’t think the survey is representative. And two-thirds of 170 is just 100 users. That’s not very much compared to other problems.
Look at the very low numbers voting in the general surveys, you cannot take anything from those so they’re basically a waste of space.
A serious overhaul of the beta program has been needed for years, especially to help in serious cases relating to this thread for example. But MS are simply not interested in improving beta practice standards, that much is a fact and it’s such a shame.
I would also like those no’s broken down into the respective machines!
This is the trouble with a “survey”, it is not very academically accurate with a very small sample size and very few exclusion/selection parameters - what I mean by this is, what machine is every person using, which console is represented, what was customer usage of the internet like, were the azure servers overloaded at the time voting took place etc etc.
Reading the forum threads is about as accurate as you get except sadly the devs never bother! (and yes I know they are given reports) - I don’t know how much notice is taken of those.
Again examples - LOD reports, weather complaints, Career mode complaints ++, 1st party plane requests for fixes and so on.
If only the 2027 year planner would have a 6 month pure focus on fixing the current sim before trying to add ever more stuff. Everyone focussing on fixes and stability in the team. Not some doing this and some doing that - the old addage - too many cooks… not enough stitches in time ![]()
A lot of us have been waiting for a follow up on this. I’m also starting to wonder if this was a bug or simply something mandated by MS to cut down the cost of streaming to the user. Might not be Asobo’s choice in the end, but it would be nice to know why we’re still dealing with lower default ground resolution than we have for 5 or so years.
I’ve become so fed up with the constant complaining about everything here lately that I hardly ever bother reading this forum anymore, let alone commenting.
For me, it’s enough that MSFS24 has worked—and continues to work—really well in VR ![]()
In my experience on PC and VR every beta update should be accompanied by a reset of nVidia shader caches and the rolling cache. Certainly update the DLSS driver if using. As an example, when I updated to SU6 ..10 standard startup, without clearing caches etc., was full of significant pauses and stutters. Resetting the caches seemed to fix it.
Back onto the subject matter herein, it seems that the level of detail in some areas of scenery do vary and I think it’s related to the base scenery data being used, not the sim’s loading of it. For example, where TIN is present, level of detail is high and LOD extends out to whatever is set in Settings. For some areas I fly to test whether scenery data has changed (Swiss Alps) the same data produces the same effects for each update, but here too, base data is being updated, especially photogrammetry data. (Alpine trees no longer look like rock spikes
) To be fair though, i disclose that I’m using a 5090 and with my settings VRAM utilisation can get to 90% of capacity near dense scenery areas.
VR makes it even worse though since it blows up the sizing of everything by orders of magnitude. I only fly VR and it makes bad textures look even worse than they would in 2D.
I don’t see the point of VR (or the sim) when many textures regularly look like Flight Unlimited (1995): ![]()
lol!! What??
I only fly VR. I’m doing a 5 hour trip right now in the Sov+. on the latest beta. No issues.
Clouds on ultra along with particles on high are solid. Terrain and scenery at 200/200 is solid.
Of course it’s not perfect, but I have no idea what people are doing who get CTD’s all the time, and say everything is so awful. I’m having great experiences; which means it’s possible.
This is one of/maybe the most demanding consumer sim/game available. It needs a robust PC to get the most out of it.
? I never said everything is awful, it’s a great sim. I said that:
- Recently I’ve been seeing a lot more terrible textures and that this is a shame since it’s a huge regression since 2020.
- Bad textures, like all visual imperfections, are even more noticeable in VR because everything is much bigger than in 2D. By definition, a low res texture looks even more low res when it’s bigger.
Not sure why you feel the need to proclaim everything is perfect in a thread dedicated to ground texture issues (that have been a commonly reported issue for ages).
on PS5 Pro with PSVR2 I’m seing one blurry low res texture here and there, but nothing crazy. the fact, that this game can now smoothly render Mach 5 speeds of camera drone in VR is just impressive and an incredible experience in VR!
What plane you used?
Sorry, some of that was more of a general statement, not aimed at you, because of the huge level of complaining I see about msfs24 in general.
You did make me laugh though, when you said I proclaimed everything is perfect, while quoting my post that says “Of course it’s not perfect”. Haha! Have a great day! ![]()
About LOD, on the last flight last night from SBSP (Addon) to SBPA (native), I saw that when I was aproaching to land at night, the city light close the plane started to flickering, how was trying to load. this was happening always when I initiated the land. At take off, the same happens but according to tha plane was taking up, the city light was becoming more stable.
XBOX X
wired connection 500gb
local instalation
PMDG 737-700
Hello @IslandSimPilot,
In the OP of this thread we requested that everyone responding kindly include all of the following information when sharing concerns about reduced LOD:
- Your platform
- What aircraft you were flying
- The geographic location (either the airport code if experienced during taxi/departure/arrival or approximate position if at cruise)
- Were you using any third-party airport or scenery add-on products? If so, which one(s)?
- The phase of flight when you encountered the LOD reduction (e.g. shortly after takeoff, just before landing, while at cruise altitude, etc.)
- Your internet connection speed (please run an online speed test from the same device you use for MSFS and post a screenshot of your results)
- Any other pertinent details, such as if you only experience this during long flight sessions or only when flying over dense cities or anything else that would be useful
We also posted a reminder about sharing these important details in this post.
Thanks,
MSFS Team
Running on PC, SU6 beta 1.8.11, 7800X3D, RX 9070 XT (26.7.1), 32 GB RAM, NVMe, 1 gbit internet connection, 4K, FSR Native AA, max framerate at 36 (before FG), FSR FG, dynamic setting to 35. Rebar off. LOD around 200-400 and OLOD 150. Fenix A320. Most settings on ‘high’.
(Normally not getting VRAM overflow, but on this .11 version I do seem to have it more easily again - some airports being particularly sensitive it seems, but not even when vram recovers, textures don’t improve).
LSZH to LSGG (from Jetstream Designs).
Full resolution, uncompressed, images available via links. Remember to press ‘download’ and watch 1:1.
Low resolution and terrible looking ground textures.
Runway looking like a low res blob during approach.
Strange dividing line in landscape scenary nearing approach. Like to different satellite images, color gradings, seasons, or…
Strange dark artifacts.
Horrible runway low res ground texture on departure from build in LSZH, RWY 28.
You may be pushing it a bit doing 4K on the RX9070XT, especially at Native AA, IMO. 1440P is the sweet spot for that GPU. Try again either using 1440P or lower your upscaling to Quality to see if you have better results
In my case I use 1440P along with FSR Quality. With FSR 4.1 I see very little difference between Native AA and Quality so I went with Quality to get the better performance and lower VRAM.
no plane, its drone camera


