Hey,
Some objects in my scene spend ages “compiling geometry” at render times, others go straight through. Their poly counts are similar though, so i’m wondering what slows this down, and is there any way to optermize it?
Cheers!
Nick D
Hi,
Can you send us the slow scene?
/Teodor
This project is under NDA, so sadly i can’t 
Hm, this will make it harder to debug
Have you tried to isolate the slow objects in the scene?
Do you have some animations, expressions or some history in the slow objects?
And what kind of objects do you have? Meshes, subdivs, NURBS, particles?
most of the case i had here was the number of poly, or subd models, like T. said u need to give us some details about the scene…
p.s. if u want to speed up ur scene, u can convert some of ur models in the scene into vrproxy → that will speed up more than 90% of converting time
cheers
p.s. if u want to speed up ur scene, u can convert some of ur models in the scene into vrproxy → that will speed up more than 90% of converting time
If they supported displacment, I would.
U can always bake the displacement (just subdivide in viewporf if u can go high enought) and export that heavy mode.
i think that vlado is working on that solution, so u can apply disp on a proxy…
Perhaps there are a lot of calculations involved in computing the final mesh for those slow objects. If the objects have any history, you could try to collapse it; if the mesh is deforming you could try to cache it.
Best regards,
Vlado
What would be ideal in the future is to use vrProxis as a geo cache format, eg just take our animation and spit out vrProxies. It would make lighting super fast. Displacment is the only thing holding us back from doing this (we really need to displace at render time).
The vray proxy as a cache would be really nice. And it would be top notch if those could be transferrable to and from other packages. So maybe we could shuffle the cinema4d mograph stuff to maya one day 
But yes, displacement is important.
We could to that, but there are already a number of similar initiatives (Alembic, XMesh) dedicated to this task and already being implemented across various 3d packages. I’m not sure we have the resources for such a thing.
Best regards,
Vlado
Then maybe the other way around and support alembic as a proxy format?
+1 for an alembic procedural!!!
This is doable certainly and is somewhere on the “to do” list But in the meantime, the Alembic implementation in Maya should do the job just fine.
Best regards,
Vlado
Alembic as proxy format will be a great feature !
It will support displacement ?
This is the goal, yes.
Best regards,
Vlado
This is a very very good news for vfx houses ! Direct rendering of Alembic file format will be a very a great feature!
I am not sure that there is any voxel support with alembic, dont you need this ?
Anyway if you can find a way to render zillons of polys with alembic instead of proxies, it will be a big news… + displace this will be great !
z
No, there isn’t. Strictly speaking we don’t need this - we’ll just use whatever we have. Of course, it won’t be the same as .vrmesh files, but it is what it is…
Best regards,
Vlado