Has the problem with Vray crashing with large scenes been resolved yet? it was always the case that anything over about 4 million polys would crash Vray.
Is this problem still present in the newer beta builds?
What size scenes do people have experience rendering (non-instanced geometry!!!)
if forcing people to use vray proxy’s is the fix for the issue, then Im not sure how viable that is. Here at work, as scenes start to get large, the vray exceptions really start to kick in. Of course, we haven’t switched to the beta yet. When we switch, then sure vrayproxy’s all the way, it just seems like you shouldn’t have to do that for 4 mil polys. Or is that many polys really too much to ask for? At home I rarely get that high so Ive had little issues, but at work 4 mil polys rapidly becomes the norm.
Welll I think the deal is… and please someone correct me if I’m wrong. If the scene is big enough to make Vray crash, but you can still fine inside of MAX, then use the dynamic geometry option (not instanciate). If the scene is to big that you can’t enven really hold it in MAX, use Vray Proxy with the dynamic geometry option.
So no, AFAIK, Proxy is not the only option, but it is a pretty good one. Having use RibArchives in Prman, it is really useful. Also, Most of the process of making things a proxy can EASILY be made into a maxscript.
For example, one could select a bunch of objects, and the script does:
Combines them
extracts the material
write the vrmesh file
inserts the proxy object
attaches the mesh to it
assigns the material
done
Never done a maxscript myself… anyone up to the challenge?
When you export the mesh, select “Export as multiple meshes”. This will keep the pivot for the proxy to where it was originally in the exported object, rather than assuming the pivot to be (0,0,0).
Newer V-Ray builds will automatically render large and/or instanced meshes as dynamic meshes to save memory, so it is not quite so necessary to convert stuff to proxies.