OTOY Forums

Hi,

I'm having a serious distortion problem with displacement in octane, both modo and standalone.

It's a strange distortion, different from the "ridged steps" that others on the forum have posted.

The examples above are from a simple 512m by 512m "plane" displaced with a 8K 32 bit TIF heightmap (i can send it, but it's 120MB if i compress it with .7z ).

Tried a lot of combination:
Tried with heightmaps generated from landscape software, with ones created by me on photoshop, with ones acquired as stock image.
Tried with 8,16,32 bit depths.
Tried wit 1k, 2k, 4k, 8k resolution.
Tried with different "plane" sizes. .

The problem allways exist.

It happens inside modo AND on "standalone".

My specs:
Modo 12.1v1
Octane for modo 3.08.1
Octane standalone 3.08.2
2x GTX 780 compute model 3.5 with Driver 388.71
AMD Ryzen 3 1200
8GB DDR4 Ram
Windows 10 Home 64 Version 1803

For the past three days i'm trying to find the cause, but i'm running out of ideas.

I would appreciate some help

Thanks in advance

Here's another example

This time:
Displaced a 1mx1m plane using modo procedural texture.
Then baked it into a 8k 32bit float .exr heightmap
Then used that .exr heightmap in octane to displace the same 1mx1m plane

result: insane distortion


The wireframe kernel. Look at the "insane" wireframe!


and a second wireframe kernel rendered from a closer camera:


...

Just an update:

All the displacements above were made inside "octane schematic" through octane override and using the "displacement node"

If the displacement is made using on the fly material conversion from modo's shader tree, it's worst. The examples are with cathmull-clark: level 5

OCTANE
And the wireframe kernel
MODO

And the wireframe:

Your files are missing Teste.tif.

Paul

Hi Paul

Here it is. I compacted with 7zip.

I was unable to upload to the forum. Had to use "wetransfer".

Here's the link.

https://nam02.safelinks.protection.outl ... reserved=0

Thanks

Any ideas why this distortion is happening?

Thanks for providing this file. It appears to be an Octane issue - potentially due to the scale of the scene. May I suggest you open a ticket with OTOY via the Support menu above and send the Standalone OCS and Teste image files.

Thanks

Paul

Just sent it.

Thanks