Displacement issue 3.07 skewed steps on smooth gradients Tweet

[Chromfell]

Hi.
I make building displacement maps.

Yeah, might be unconventional - but listen, I feel like 3.07 has a problem with displacement. Let me show you.

What are those steps? My first thought was not enough bit depth (had that before), but they also don't make any sense visually...
To me at least. You're looking at a pure, lossless linear 16-bit PNG gradient being displaced, but with weird skewed lines throughout.
I've had other octane users replicate the issue on their end (presumably also on 3.07) and they experienced the same.

I reproduced the effect with other displacement examples aswell:

You're looking at a 32-bit tiff baked sphere and a cube. And those ridges are NOT supposed to be there.

Just hope it's fixed by the time stable 3.08 rolls out cuz I really wanna get my hands on that sweet OSL in OctaneC4D... but my building maps are my everything, ya feel?

Anyway, what the hecc happen otoy???

.ORBX PROJECT FILE:

displacement_issue_3_07_skewed_steps_on_smooth_gradients.orbx

(4.2 MiB) Downloaded 66 times

[bepeg4d]

Hi Chromfell,
wow, congrats, great displacement work
About 3.07/3.08, now you need to click the tool icon of the Displacement texture and change the depth from default 16bit to 32bit:

ciao beppe

[Chromfell]

hi beppe,

Thanks, but I have to ask, why the change? How does this affect the workflow?
Did it previously always interpret as 32bit and this is the new default to save VRAM?
Seems like a bad idea to have the "worse" option as a default :/

I also have no option to enable this in cinema4d plugin which is what I mainly work with...
so I can't use smooth displacement there at the moment?
Interesting choices.

ciao chromfell

[aoktar]

I also have no option to enable this in cinema4d plugin which is what I mainly work with...
so I can't use smooth displacement there at the moment?
Interesting choices.

It's for saving memory and good for most of situations i suppose. Also I don't know how to change this parameter from sdk but i'll talk to team.

[bepeg4d]

Hi Chromfell,
in Standalone you can specify in Preferences/Import what to do with HDR texture bit depth while importing :

ciao beppe

[abstrax]

hi beppe,

Thanks, but I have to ask, why the change? How does this affect the workflow?
Did it previously always interpret as 32bit and this is the new default to save VRAM?
Seems like a bad idea to have the "worse" option as a default :/

I also have no option to enable this in cinema4d plugin which is what I mainly work with...
so I can't use smooth displacement there at the moment?
Interesting choices.

ciao chromfell

HDR images that are used as textures are converted to half float anyway, which is why we made it the default. Displacement mapping is actually the exception here, but of course you can change the defaults in the preferences to what you think makes most sense for you. And of course you can also change it for a particular node, too (using the wrench icon).

[julienplastic]

Hello,
I have a similar problem with Octane Render for C4d 3.06.2.
How I can resolve this problem?
(The displacment use a 32bit ImageTexture, levels of details in displacment channel is 4096x4096.)
All the best

[julienplastic]

Hello,
No solutions for this?

[bepeg4d]

Hi julienplastic,
sorry, difficult to say without the scene.
Please, try with 3.08test 6, the displacement feature has been revisited.
ciao beppe