OTOY Forums

Is there any explanation for why this is suddenly happening on all my displacements? I've been getting this for the last few months, and I thought I'd open up a previously fine model that never had this effect before, and its also present here.
The last time I was advised on this, it was suggested I switch to Vertex Displacement, but honestly, that's a completely unworkable idea, because doing so means I have to switch the subdivisions to the point that the model goes from 600k to 2.2m pixels.

I'm getting to the point where I have to not use displacements, and I don't understand why it's not working. Vertex displacements are never, ever, a solution, because they either don't work, or they make the whole scene completely unworkable due to the performance hit.

Forgive me for seeming frustrated, but Octane is the only software I use that doesn't seem to get incrementally better.

The problem is that even if I reduce the file down to its barest components, the error still exists. Plus the error only presents at certain angles in the scene, which leads me to believe it's not something on my end, since, as I already stated, this didn't happen at all on anything I did until a few months ago.

The topology on this object is literally just a flat cube. The displacement is a 32bit EXR file of some text. Again, the most basic possible displacement. I've experimented with LNG and JPG to the same result.

It's terms of correctly setting up, I've tried every possible setting I can think of. I'm by no means an expert, but if I create a displacement node, plug in an image, and then set my distance, it should work, right?

I'm not saying it's definitely not me, but if it worked previously, and now EVERY displacement does this, even ones that previously worked? I can't simplify the steps I'm taking because the simplest step, which is just creating the nose and plugging the texture in has the same effect.

I've emailed the scene to you and would be interested to see what the problem actually is

It looks like a scaling error issue. "Ray epsilon" is a threshold value to adjust math errors, similar to OpenGL scene scaling factors.

See "Ray epsilon" here:
https://docs.otoy.com/cinema4d/DirectLighting.html

I noticed the most recent version of Octane completely broke all previous versions of displacement on my old scenes too. Maybe switching into a different compatibility mode would fix it?