Displacement

[glorybound]

My understanding is 2D and 3D should render just as fast in the later releases if V-Ray. Is this correct? I have a scene that renders nice at a high resolution using 2D, but with 3D it will not fit into the RAM I have. With 3D I can have the edges joined, so 3D is a must. Any tips?

[glorybound]

3D gets caught up in the Uploading Geometry, which takes 3-4 hours.

[glorybound]

using the VRayBmpFilter and dropping the blur seems to help.

[Macker]

http://macviz.blogspot.co.uk/2013/08/bitmap-tip.html

[vlado]

My understanding is 2D and 3D should render just as fast in the later releases if V-Ray. Is this correct?

Only if you have enough RAM unfortunately. Increasing the dynamic memory limit and perhaps the edge length may help.

Best regards,
Vlado

[glorybound]

I did turn off filtering, but this script sure looks helpful.

http://macviz.blogspot.co.uk/2013/08/bitmap-tip.html

[glorybound]

I have my dynamic memory to 12GB and the edge length is 6, but I am literally seeing 12 hr pre-cal and 12 hour render times.

Only if you have enough RAM unfortunately. Increasing the dynamic memory limit and perhaps the edge length may help.

Best regards,
Vlado

[glorybound]

Do you see anything that I can change to speed up my render times? It is stone, which is a good distance from the camera.

[Seraph135]

Do you need 512 subdivs? I usually lower this value a lot. Between 8 and 24 depending on how dense the geometry I'm displacing already is. I also factor in the final output resolution too.

Tim J

[glorybound]

Well, I thought 512 was already the bare minimum and I never thought of lowering it more. I'll stop the rendering, lower it, and see what happens.

Do you need 512 subdivs? I usually lower this value a lot. Between 8 and 24 depending on how dense the geometry I'm displacing already is. I also factor in the final output resolution too.

Tim J

[glorybound]

is your site down, or is it me? http://www.seraph3d.com/

Do you need 512 subdivs? I usually lower this value a lot. Between 8 and 24 depending on how dense the geometry I'm displacing already is. I also factor in the final output resolution too.

Tim J

[glorybound]

with 24 subdivs, by edges don't meet up nice. I'll bump it up until I get a good balance.

[Neilg]

Add a few iterations of meshsmooth (or whatever you need to do if it goes around a corner) to your model and subdivide it in advance before lowering the subdivisions to 8-32. throwing subdivisions that high on a large flat plane is messy & inefficient.

If you control the density of the mesh so it drops off further from the camera you can drop this really low and get super optimised displacement.

[Seraph135]

is your site down, or is it me? http://www.seraph3d.com/

Yes its down right now. I'm hoping to have it back up and running in a few weeks.

Add a few iterations of meshsmooth (or whatever you need to do if it goes around a corner) to your model and subdivide it in advance before lowering the subdivisions to 8-32. throwing subdivisions that high on a large flat plane is messy & inefficient.

If you control the density of the mesh so it drops off further from the camera you can drop this really low and get super optimised displacement.

totally agree with this.

[glorybound]

I am dealing with Revit geometry here, so it ain't pretty! I would have to slice every corner, and the arches would be difficult. If I put a meshsmooth on it, it turns into a blog. Is there a script for this kind of geometry like Populate:Terrain for sites?