Any news on the "preview displacement in viewport"-frontier?

[Bigguns]

+ 1 here too!!

[FSGFX]

this should be handled by the dcc app... and it should not be that complicated... if im correct its part of openSubD...

[Midiaeffects]

+100

Would love to have it. Is it possible to use GPU tesselation for that, like Houdini?

https://www.youtube.com/watch?v=lDry8HoAjBY

[FSGFX]

maya does it now with openSubD... take a look at the viewport 2.0 vid...
http://help.autodesk.com/view/MAYAUL...4-597EE20E4826

i hope max will follow...

[fraggle]

+1
By the way, is there a way to convert vraydisplacement mod to edit poly?

[tashko.zashev]

+1
By the way, is there a way to convert vraydisplacement mod to edit poly?

Nope, sorry.

[Art48]

+1
By the way, is there a way to convert vraydisplacement mod to edit poly?

Just imagine the max crashes :P

[ben_hamburg]

+1 here aswell...Not a life saving option, since in most cases its ok to just put a standard displacement modifier below vraydisplacement and set it to only show in viewport, but thats still one more step I´d like to get rid off, since I´m doing it so often...

[Art48]

+1 here aswell...Not a life saving option, since in most cases its ok to just put a standard displacement modifier below vraydisplacement and set it to only show in viewport, but thats still one more step I´d like to get rid off, since I´m doing it so often...

What you seem to forget here is that for the max displacement modifier to show properly you need a good, dense mesh. Wasted viewport performance I think.

[fraggle]

+1 here aswell...Not a life saving option, since in most cases its ok to just put a standard displacement modifier below vraydisplacement and set it to only show in viewport, but thats still one more step I´d like to get rid off, since I´m doing it so often...

Good idea, thanks.

[ben_hamburg]

What you seem to forget here is that for the max displacement modifier to show properly you need a good, dense mesh. Wasted viewport performance I think.

I´m well aware of that. But often its not necessary to have a 100% accurate representation of the displaced mesh, for example if you need to place other objects on it or have animated objects react to it.
In those cases it would be usefull to have the vraydisplacement modifier to represent an approximation of the render time displacement.
Because if you´re using a standard displacement modifier to do that job, you might run into multiple issues: The displacement might not be quite identical, you have to take take care ,that the standard displacement modifiers luminance center and vraydisplacement modifiers shift values correspond, you have to make sure to use the same instanced map and update it on both modifiers, in case you switch it out etc etc...