Material Displacement Issue for Terrain Height Maps

[Bowser16NB]

Hello,

I have consistently had problems with getting terrain height maps to work properly in Octane.

Whenever I map a terrain heightmap into a material displacement it will leave strange artifacts in a couple ways.

1.) These artifacts are mainly on the outer edge of the plane that has the matieral displacement applied. Thin stripes layer on boarder.

2.) I encounter artifacting/pixelization within the area of the terrain as well. Some areas seem to have polys missing and show as black.

I've double checked quality settings both within the displacement channel of the material and in render settings>c4d shaders>render size

Neither seems to do the trick.

Has anyone else been encountering this or found a solution?

Thanks
NB

[bepeg4d]

Hi NB,
are you working with 16/32bit images for displacement?
You can verify/correct the image in PS/Gimp, or enable the Filter to reduce the differences. and add an UV transform node with slightly bigger scale in x-y to correct the borders.
ciao beppe

[Jolbertoquini]

Two problems there.

1. You need crop you texture displacement.
2.make sure you are using a map with 16bit or 32bit should be large enough.

Also the scale of your plane may be to small for Octane. Please check this post viewtopic.php?f=24&t=61634

[abstrax]

Hello,

I have consistently had problems with getting terrain height maps to work properly in Octane.

Whenever I map a terrain heightmap into a material displacement it will leave strange artifacts in a couple ways.

1.) These artifacts are mainly on the outer edge of the plane that has the matieral displacement applied. Thin stripes layer on boarder.

2.) I encounter artifacting/pixelization within the area of the terrain as well. Some areas seem to have polys missing and show as black.

I've double checked quality settings both within the displacement channel of the material and in render settings>c4d shaders>render size

Neither seems to do the trick.

Has anyone else been encountering this or found a solution?

Thanks
NB

Please send us the scene and we will have a look at it. The blockiness is an artifact of the current algorithm that is being used. The stripes shouldn't be there and if you send us the scene, we will check what is going on there.

[Jolbertoquini]

Hello,

I have consistently had problems with getting terrain height maps to work properly in Octane.

Whenever I map a terrain heightmap into a material displacement it will leave strange artifacts in a couple ways.

1.) These artifacts are mainly on the outer edge of the plane that has the matieral displacement applied. Thin stripes layer on boarder.

2.) I encounter artifacting/pixelization within the area of the terrain as well. Some areas seem to have polys missing and show as black.

I've double checked quality settings both within the displacement channel of the material and in render settings>c4d shaders>render size

Neither seems to do the trick.

Has anyone else been encountering this or found a solution?

Thanks
NB

Please send us the scene and we will have a look at it. The blockiness is an artifact of the current algorithm that is being used. The stripes shouldn't be there and if you send us the scene, we will check what is going on there.

Hi Abstrax,

Spend nearly a 16 days I posted a issue about displacement also I update the scenes for check and I've got any answer? Please could you check this if you don't mind. Is really frustrate when we have issues with Octane and take ages to have any fix or answer.

here the post with the scene:

viewtopic.php?f=110&t=61819&p=316181#p316181


cheers,
JO

[abstrax]

Hi Abstrax,

Spend nearly a 16 days I posted a issue about displacement also I update the scenes for check and I've got any answer? Please could you check this if you don't mind. Is really frustrate when we have issues with Octane and take ages to have any fix or answer.

here the post with the scene:

viewtopic.php?f=110&t=61819&p=316181#p316181


cheers,
JO

You reported this problem to our support and they should have gotten back to you. Looks like a bug, but I'm not sure yet what the problem is and how to fix it. We will investigate it and fix it as soon as possible.