Corrupt texture tiles (squares) at random locations only at specific distances

User Support Hub Install, Performance & Graphics
, , , , , , ,
1

I’d like to report the issue that I’m facing with clean install (reinstalled to see if it resolves this but it doesnt) of the MSFS2024;

  • Weird checkerboard-alike colorful square tiles appearing in weird missing-textures-alike shapes at random locations (mostly terrainy areas) only at specific distances (i.e. gettin furhter away they disappear and look normal, same as if going close enough). So to me it seems just like if texture at certain resoulution (i.e. certain distance from terrain) would be corrupt/missing/…

As said, no mods used, clean reinstall including packages folder reset, shaders/cache cleaned, all drivers up to date.

I can trigger it not only flying, but also slew-ing around randomly and it randomly appears.

Never had this in FS2020.

RTX4090, 13900k, 64GB ram.

When it appears, FPS are good and stable, and VRAM is nowhere near the limit.

See the picture of the issue below:

image
image1080×535 115 KB

Any help would be appreciated!

2

Is this your issue: https://forums.flightsimulator.com/t/ground-textures-are-blurry-lod-system-is-too-aggressive-and-loss-of-detail-in-2024-streamed-scenery-looks-worse-than-2020/676315

3

Not so sure because in my case it seems almost like a glitchy/missing texture rather than blurriness mostly reported in that one thread. But I can try my luck in that one too. What’s mostly interesting is that nobody reported same thing just yet, but it’s at least 2 of us (me and friend of mine) who are new to 2024 and both experience same issue. Both of us on decent RIGs and with fresh installs. SU2 BETA, I can try disabling it to see if it makes any difference but I doubt it’s related to that.

4

I think I found solution.
What I did is de-activated BETA SU2 and simultaneously also deleted the Streamed packages
(C:\Users\user\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\StreamedPackages)

One of the 2 things seems to resolve it, I guess it’s the packages “reset”.

Thanks anyways, will report if re-appears.

1 Like
5

Moved to User Support Hub since a solution has been marked.