Is it real to make displacement in Cycles like in octane or corona render for less memory usage?
There are a lot of cases I can do in Octane with displacement, and can’t do the same with Cycles, because - out of memory. But I like Cycles, i want to do all in it.
Is 2.5d displacement for cycles in development? In plans? Is it real for cycles?
Displaced meshes are not watertight, although this is not considered unsolvable. From what I seem to understand, discontinuities only appear at UV seams and whenever the displacement map is rather coarse, so it’s invisible most of the time.
edit : apparently I was wrong on that second point, see Brecht’s reply below
The technique is incompatible with GPU acceleration, because it doesn’t tesselate and build a BVH beforehand, which is what GPUs expect to be fed. Instead it creates a “displaced-BVH” on-the-fly for each ray. This sounds like kind of a dealbreaker…
A future extension would be to extend modern hardware to directly support displacement mapping
doesn’t seem absurd to me but then again what do I know
I think the main downside of this method is the performance, which from the papers seems to be about 20-50x slower than pre-tessellated meshes after preprocessing is done. Still would be great to have as an option.
So it would be compatible with GPU acceleration after all ? have I read this wrong ? or would it be considered as a CPU-only method ? I’m thinking if it’s limited to CPU and it’s 50 times slower, well, wow, that seems like a pretty steep price to pay for lower memory footprint