Search
-
Problem with HLSL Terrain Shader(Texture 2D Array)
Hi, I use the HLSL function Texture2D.Load do retrieve texture information. These informations are 3 Texture Indicies, 3 Texture blend weights and 3 texture tiling vaulues. Now if 2 different texture indicies are blended which have different texture tiling values there are some kind of gridlines showing and i don´t know… -
Re: Problem with HLSL Terrain Shader(Texture 2D Array)
We were messing around with some materials that stepped the UVs to make blocky surfaces and saw the exact same thing. It's caused by the mipmap algorithm spotting that the UVs jump a long way at the border and using a lower mipmap level on it. I don't think there's a huge amount you can do other than hard splitting the… -
Re: Problem with HLSL Terrain Shader(Texture 2D Array)
I found another way to "fix" it, if i use texture2dlod instead of sample(meaning no mips) it won´t show these lines two. Limiting the mips doesn´t seem to help either. -
Re: Problem with HLSL Terrain Shader(Texture 2D Array)
Tried that already(on every frac) and it doesn´t help( int3 index = int3((int2)(frac(inputval.sTexCoords) * 256), 0); doesn´t have any frac anymore in a newer version) -
Re: Problem with HLSL Terrain Shader(Texture 2D Array)
Does it still happen if you take out the frac function? I've seen weird things like that happen right on the boundaries where the value hits a whole number and frac rolls it around again. -
Re: Problem with HLSL Terrain Shader(Texture 2D Array)
Thanks for mentioning that it´s a mipping issue, we got it to work ;) We just did this:float2 dx = ddx(uv);float2 dy = ddy(uv);if(blend.x)result = lerp(result, SplatTextureArray.SampleGrad(splattexturarraystate, float3(uv * blend.y, indices[0]), dx * blend.y, dy * blend.y), blend.x);
6 results