Terrain deserialization errors spamming in the console (but terrain is working correctly)

[K3rhos]

Branch

release

Describe the bug

So I have recently reworked my terrain in my game, previously I was using a 200000 x 200000 terrain, with an 8bit 512x512 heightmap, I recently remade my heightmap to be 16bit 4096x4096, to get a way better looking terrain. EDIT: After more testing heightmaps has nothing to do with that

The size is the same and the settings are the same as I was using before but with a new heightmap, so now I'm getting these errors when playing my game:

Here is the settings of my terrain:

I tried a TONS of values for both "ClipMapLodLevels" and "ClipMapLodExtentTexels", I always get the same 2 errors on play mode, the only thing I found that was removing one of the error was to put ClipMapLodLevels to 6, the only value where it doesn't throw an error for some reasons.

To Reproduce

So this is probably not exactly clear, but since this issue didn't existed when I was using a 512x512 heightmap I'm pretty sure there is some sort of issue with the LOD system when using a high quality heightmap like I'm using now (4096x4096).

Expected behavior

Not throw these annoying errors on play (especially since they appear to be only visual, the terrain works great, and the Lod system too, so idk why it keep throwing this)

Media/Files

No response

Additional context

No response

[DevulTj]

could you provide the project?

[K3rhos]

Well, first of all this has become even weirder, I disabled the terrain entirely (+ the gameobject) and now it throwing a different deserialization error:

Idk wtf is wrong with my terrain lol

[K3rhos]

Apparently deleting (cuting it) the terrain component entirely, no errors thrown, which makes sense, but once I paste the terrain component again, it throw back errors in the console (terrainwidth and terrainheight) in this case (no need to enter playmode for them to show this time)

[K3rhos]

Okay so after more testing, it appears that the "deserialization errors" still come with my old terrain (and with the repro example I'm sending you below), so I wonder if this has something to do with a recent S&box update ?!

First of all, when creating a fresh project, creating an empty terrain throw this error: (Which is unrelated with the deserialization errors, but still a problem)

Once I have linked a terrain, I have changed the settings to match my terrain I was using in my project:

And what a surprise:

Exact same errors !

So this has nothing to do with heightmaps or anything, the terrain component on itself (with some specific size/height/cliplod etc... seems to throw these errors)

Here is the reproduction repo: https://github.com/K3rhos/terraindeserializationerrors