I have seen similar places.
Usually I stop my drone cam … and wait in place to watch if something will change if I allow time to make progress on some static data (texture) downloads.
My feeling is, that FS2024 might have similar caching bugs like FS2020. In FS2020 it could be triggered by a very rapid movement of a (drone) camera.
I suspect what happened in FS2020 and might exist in a similar form in FS2024 is something like this:
- Camera moves to a position
- 3D rendering needs to define a 3D mesh and texture for that place
- A low res texture was just downloaded … because the cam was approaching that place
- Now a high res texture is requested from the server
- … but in the meantime an extrapolation of the low res is used … until the better res arrives
- and somehow … that better res never replaces the low res for that location
- … because the system now remembers the extrapolated “low res” as the cached “high res”
In FS2020 no amount of waiting could heal that display bug. The only solution was to move far away … get the 3D data purged from the GPU … and then come back to that location.
Perhaps the more “aggressive” caching in FS2024 adds a new flavour to this kind of bug.
A “bad cache” overrides “the truth”.
I could clean my cache to test this idea … but so far I was too lazy.
PS: I have a number of places on Maui and Lana’i where I can clearly see a “line” where low res ground meets high res ground. And that clearly is not FPS etc. related. All data by now comes from the Rolling Cache. Here is one location … and on the very right, if you look closely, you can see a sharp line where the level of details changes:



















