LOD seems okay but i think there is a problem about resolution. both buildings and terrain were kinda 480p over Abu&Dubai. graphic quality is so low now, nothing like before.
and after watching the intro it gets worst…
(I know those’re not captured on Xbox)
Yeh mate it’s dodgy for sure. Try clearing rolling cache and set it to at least 64 GB. Warning: you’re not going to get that space back, FYI!
But it helps… Fly around the same locations for a while… Report back
1.30.11.0 Beta here, XBOX Series X, low quality textures, pop-up for many building and environment. Try to fly near Mt. Rushmore, trees appear as on PlayStation 2
Can you post pictures or video?
Low quality textures are likely not LOD related but the trees typically are.
Would be nice to see what you are reporting.
That, friend, appears to be more of a server proximity issue.
Is your rolling cache on? Have you tried to reset your console and router and then launch the game?
I’m on Series X too and the world looks pristine most of the time, even when I’m flying several thousand feet up in the air and zoom in .. things look as I’d expect.
This issue has returned in today’s beta update 1.30.12.0
https://forums.flightsimulator.com/t/release-notes-1-30-12-0-january-17-2023/570441
It would be cool if you can share an image of this to confirm, or at least compare with others
Issue also present in the xCloud version of MSFS (being run by a series X virtually).
Not only visuals but performance was much better back in SU10. Now, not only the frame rate feels lower and the whole experience clunkier, ground textures are absolute horrendous. Even airport runways are super blurry while you’re on the ground rolling on the runway. Not a lie / exageration, my vanilla FSX has better ground textures than MSFS in it’s current state.
Made this video yesterday: https://www.youtube-nocookie.com/embed/lCUDAji3IkM
At 0:45 look at the texture resolution of the runway. Other airports are exactly like that, even after landing, not to mention the town as a whole around the airport is also super low-res.
Here’s a new demonstration from today. It was shot at basically the same location at the demonstration I made when the issue occurred the first time. For comparison, the original video can be found in my original post or on the same Youtube channel.
I can say with certainty that the same issue is reoccurring. Above a certain threshold, texture quality and polygon count both plummet. You’ll notice it mostly on roads, parking lots, and rooftops.
The graphical downgrade is back on Xbox Series X. I’m seeing incredibly blurry ground textures, a very sharp and noticable LOD change with changing altitude just a few meters. Ground textures look again like over compressed jpeg pictures, just like in SU11.
Asobo, this is beyond disappointing if you intend to release the update in this state. I hope this is just a bug in the latest beta version which will be fixed soon.
When taking these screens I’ve chosen Robin dr400, one of the smallest planes, which shouldn’t affect graphics quality like an airliner could.
These pictures are showing the sharp LOD degradation when moving just a few meters up. One moment ground is looking ok, and then everything turns to water painting. Just like in SU11.
And below a video showing the LOD problem that has returned on Xbox Series X.
This downgrade issue is really easy to reproduce. Start on a parking space, switch to drone camera, gain some altitude. You will see a dramatic change in terrain LOD and it occurs every time you pass a fixed altitude, the ground turns to blurry water painting.
It has nothing to do with servers, it’s hard coded in the current veta version.
Thanks for sharing, same problem here
This is what i am talking about. It looks worst at 3000-5000 ft.
There is a chance this is a server issue, but it likely is a texture downgrade since so many are reporting the same thing.
If we can also confirm a LOD downgrade, then it would point to the same issue we had with SU11. If it is only a texture issue, the source of the issue could be something different than the SU11 problem.
No issues here with blurry runways! Runway numbers are clearly visible (and readable) from 3,4 and 5000 ft! But there is still an issue with scenery popping in! This ‘bug’ was introduced with SU 9!
How is this server issue can you please explain us? Same thing happens with paid airports, textures looks like above screenshots, some textures looks washed out, discolored, 8bit, less detailed. Static Objects on airports, like cars, lamps, taxiway signs, static planes keep appearing or dissappearing in front of me, or while taking off and landing. How is this related to server issue on a paid airport? Nothing like this happened on su10. Paid airports should have maximum non changing LODs right?
All of this related to server issues please?
Thanks.
I said there is a chance it is a server issue. I do not see definitive proof it is a server issue.
I’m looking to isolate and reproduce this issue like anyone else in here.
I will be on console within the hour to try and reproduce this issue myself. It takes longer to confirm things looking at other people’s photos from a phone. MUCH smaller screen.
Yes a definite issue thank you for sharing. I expect it will fall on deaf ears though. I think we’re looking at the update in its current form on beta. Call me cynical, but this is almost what happened last time. Prior to SU11 on beta, simmers reported poor graphical issues but was inexplicably ignored and the update was released. I did express my views in a prior post but was deleted by admin because I said a naughty word. If it’s not fixed after this update then myself and I suspect a lot of others will have lost patience.
A good sign is a community manager posted about it in this thread and asked if anyone could confirm the issue.
Personal Comments
Don’t think they ignored the issue.
They had 40th anniversary content to release-would you make simmers unhappy by delaying long-awaited content or wait to release something based on an issue like this?
Maybe they didn’t have a solution to the issue, either.
But this thread was marked bug-logged during the beta, meaning the devs could reproduce the issue. So they were probably working on a fix and it took longer to release a fix.
They found the source of the issue just a few days after the last major update released.