Terrain texture issue

[SamuelDugger]

Terrain3D version

v1.0.1

System information

Godot v4.5.stable.mono - Windows 10 (build 19045) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 32.0.15.8180) - Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz (20 threads) - 31.85 GiB memory

Is the issue reproducable in the demo?

Yes

Issue description

To me it looks like there is some flickering or z-fighting going on with my textures. I've tried adjusting the camera near and far values and that hasn't affected it. I've also tried disabling temporal effects. I'm fairly new to game dev so please excuse my ignorance on the subject.

2025-12-13.17-15-01.mp4

Logs

godot.log
godot2025-12-13T16.42.58.log
godot2025-12-13T16.51.48.log
godot2025-12-13T16.51.58.log
godot2025-12-13T17.08.53.log

[TokisanGames]

What specifically is the problem? I don't see any issue except a dark, under exposed terrain.
Textures don't have z-ordering, so can't z-fight.

Since you say it's reproducible in our demo, please describe the specific steps needed to reproduce it and show video of it.

[SamuelDugger]

If you look at the path, there's some kind of weird visual line that appears as I move toward it. I recreated it in the demo with a brighter texture so its easier to see. You can see it very noticeably in the left path. Sorry about the first video, I was experimenting with the different albedo colors. To recreate this, I just setup two new textures painted them down, then used the spray brush on the edges of the path texture with the grass texture to smooth out the edges. I could just be creating the texture wrong, importing it wrong, or missing a step somewhere. Once again I'm not super familiar with this yet as its my first time using it and I'm still fairly new to game dev.

2025-12-13.23-01-04.mp4

[TokisanGames]

That's a Level Of Detail(LOD) transition point. Every production game uses LODs. Look at the wireframe mode. If you don't want to see them, expand mesh_size at a performance cost, or better, fill your game with content. Later versions geomorph between the LODs.

[SamuelDugger]

I understand that most games have them, I just don't think they are normally this drastic up close. I played around with changing the mesh_size and I personally didn't see any meaningful difference. I tried an example in the demo where I expand the mesh_size to the max it will let me (64) and also adding in some meshes to try and help and in my opinion it still just seems too harsh for a LOD visual being that drastic and noticeable that close to the player. If it was only happening far enough away that no one would really notice I wouldn't mind. But this is happening right in front of the player. I'm attaching a clip of the demo with your recommendations on how to help. If you have any other tips or practices so that I could at least avoid seeing these until the later versions that fix this come out I would greatly appreciate it.

[SamuelDugger]

2025-12-14.01-42-22.mp4

Here is that video trying the recommended changes. Sorry its so short, GitHub loves to have really strict size limits with videos.

[TokisanGames]

I understand that most games have them, I just don't think they are normally this drastic up close.

Most games are full of content and sound which distract you from the flaws. You're comparing an unfinished, brand new project with default settings against commercial, polished games. I gave you the setting to change what you want.

I personally didn't see any meaningful difference.

Mesh_size changes the size of lod0, and all lods. Later versions geomorph and go up to 256. But it would be unwise to go that high unless you really know what you're doing.

As I said, look at the wire frame.

You can also set the clipmap target in later versions which is recommended for third person games.

later versions that fix this come out I would greatly appreciate it.

Use a nightly build, see the docs.

[SamuelDugger]

I understand what you're saying and I have somewhat of an understanding of how it works, and I tried your settings and you can still see the issue in the video. I've looked at the wire frame and so I can visually see how the changes effects it, but as far as the painted textures go, it seems to have little to no effect. I understand this is a new game so there aren't as many things going on, but slapping on more content is not going to get rid of the very apparent jarring line constantly in front of the player no matter how good the content is. In my opinion that is a band-aid fix and is not fixing the problem. But I'm not here to argue with you and I'm not mad or upset about anything, I'm just looking for a good plugin that could help me make my game. I'm not dead set on using Terrain3D or any plugin for my project and was just testing the waters because a few people seem to like it. But if it can't handle paths without LODs transition point lines in close view then it is probably not going to work for me ,and that's alright man. I appreciate your help with all this. Once the updated version comes out I'll try it again.

[TokisanGames]

In the material, enable the shader override. Then edit this line.
Change bool bilerp = region_mip < 0.0 && region_uv.z > -1.; to region_mip < 1.0 or 2-4 and see if that helps.

However, you need to smooth your path for good results.

[SamuelDugger]

That worked perfectly. I tried both 1 and 2 but I still was seeing the issue, but raising it to 4 seems to have helped resolve that issue. I appreciate your help with all of this and the quick responses. Sorry for being impertinent. Was just bashing my head trying to resolve these issues for multiple days and nothing seemed to work. Once again, thank you!

[TokisanGames]

This is improved in #899. The < 4.0 bilerp condition is built in, and adjusting this number doesn't have as much of impact on quality or performance as it did before.