Future of displacement.

[BbB]

Hi Ono. Can we expect further developments of this feature in the foreseeable future? I'm thinking more of memory consumption, on-the-fly subdivision, etc. than new functionalities here.

[Zom-B]

the possibility to transform a mesh multiple times via displacement to get a more 3D displaced mesh would be awesome too (also capable of using different maps for this)...

[BbB]

You can do that to an extent by using your app's internal displacement modifier and then apply an Indigo displacement to the displaced mesh. I think that's how the Doc did his rock formations.

[Zom-B]

yes I know, but if I actually subdivide the mesh heavily in my 3D app, do there some displacement, why shouldn't i do a second (and third...) displacement pass in my 3D app too??!

The Point is to get subdivision and displacement in Indigo done, so your 3D mesh data stays small and portable...

[crojack]

and not all 3d apps support displacement, cough cough sketchup cough.

I too am interested if there is going to be more development of this.

I would jsut like to see a solid implementation of this.

[OnoSendai]

Well one thing I think i'll add is a 'min-num-subdivisions' parameter.
This will allow subdivision + displacement of flat planes to occur when the subdivision cuvature threshold is > 0.

As far as dynamic subdivision + displacement go, I'm not planning to add that immediately.
I think that generally it will be more efficient to precompute the subdivided triangles.