
0
Not a bug
Double sided shader error
Hi Joachim, i have a odd artifact, if i go up the grass pass from bad to good, and when i'm on the top of the mountain i can see all the grass good, but if i'm on the bottom of the mountain there is like a invisible line which "split" the colors.
The shader is very simple as you can see
The shader is very simple as you can see
Answer

0
Answer
Not a bug
Freya Holmér (Developer) 10 years ago
Ah, hehe, I missed that too :)

Under review
Are you using Unity's terrain object? If yes, does it happen if you place grass quads manually?

No, it's a voxel terrain, and yes i think they are quads, they are also merged in groups

Do you get the same issue if they are not marked as static?
Also, are you running deferred or forward rendering, and does switching it make it better/worse?
Also, are you running deferred or forward rendering, and does switching it make it better/worse?

Okey my bad i put the node connected to a normal and i don't know why, now it works perfect, apologies, you can close it and mark it as no error.

Okey sorry for reopen this but the issue is still there, i got confuse because i change the material.
The shader is now without the normal input and i still have that error i attach a screenshot for a better view of the issue.
With other shader it works perfect, it's very weird.
![]()
Additional info: It only happens in double sided mode.
The shader is now without the normal input and i still have that error i attach a screenshot for a better view of the issue.
With other shader it works perfect, it's very weird.
Additional info: It only happens in double sided mode.
Customer support service by UserEcho