Really hope they fix this before release.
Note that this topic is bug-logged , so the test team is both aware of it and has managed to reproduce the issue in their test lab.
bug-logged
The issue reported by the community has been successfully reproduced by our test team and turned into an official bug. The bug is now being assigned, prioritized, and worked on for a future fix.
funny, for a bug that exists, almost if not, since release of FS2020
From what others have posted, there definitely do seem to be similar issues that have affected FS2020 for a long time. Having said that, I have flown the same areas regularly since the release of FS2020, and the issues I’m seeing (at least the areas in which I’m seeing them) are definitely new and were introduced with this beta.
This issue has been FIXED in 1.5.19.0! Thanks so much, Asobo!
definitly not, it may have “changed” for a better and correct display of groundtexture in specific places, but the underlining issue is still there and it is still the same that exists since FS2020.
I’m sure the texture popping issues that have existed since the beginning of FS2020 are still there, so I acknowledge THAT issue hasn’t been fixed. But the issue I saw with textures popping around photogrammetry airports was specifically introduced in an earlier SU3 beta release, and it has been fixed. Don’t want to split hairs, just trying to be accurate and give credit where it is due. Asobo fixed the specific issue I was seeing pretty quickly, and I appreciate that!
The issue is not fixed entirely I fear. See the area around the huge houses at the beach near Alicante airport LEAL. Tiles of beach and water and dunes will switch depending on camera angle and proximity.
This is precisely what I’ve been talking about. It hasn’t been addressed in FS2020, and FS2024 sadly carries the same unresolved baggage. The issue hasn’t been “fixed”; it’s merely shifted. The rendering of ground textures continues to change based on proximity, and while it may appear resolved in some areas, the underlying problem is very much alive. It’s just showing up in different locations now. so NOT FIXED.
The root seems to lie in mismatched datasets or imagery versions, much like what happens with regular Bing Maps. Instead of using high-resolution aerial photography as the base from which lower-resolution versions are derived, an entirely different set of satellite imagery is used for the low-res layers. That, combined with aggressive LOD thresholds and the lack of proper fade logic, is likely the core of the issue.
I’m seeing this issue in MSFS 2020. The terrain LOD system is entirely borked for both sims. What a disaster.
Can someone please remove the ‘Solution’ / ‘It’s fixed’ tag on this thread?
This is not fixed, still occuring
The OP has marked this as solved, and I’m not sure if anybody else can change or update that. Maybe a moderator can, but they may not want to do this either. From OP’s perspective, the original issue is now fixed. If similar things are still happening in other areas or under other conditions, you may need to open a new report in this beta forum. Then you can decide when to mark it as “solved” or not.
@ShakyBug6501
As @CaphollandX mentions, the OP has marked this as solved, as from their perspective, the original issue is now fixed.
However, this has no bearing on the bug-logged status of this topic. This is managed by CMs, and will change based on feedback from the test & dev teams - for example, to fixed-on-live if the bug has been fixed & the code change is included in a released build.
Hello. The same thing is happening to me. I am on the latest stable release and have 2000MB (2GB) broadband speeds. Speed test checked. Also deleted rolling Cache. MSFS2024 scenery looks just like Flight Sim X steam edition with moving scenery changing as I fly over. Also buildings in New York were missing from a short distance away before loading.
Never had this issue on MSFS2020
What you are describing in that image is PG at range, not ground imagery being blurry or changing drastically as your distance changes. There are other threads for that particular issue.