Proxy = faster rendering?

[Exon]

I have a project coming up that I know will be a killer for rendering..

If I make a vray proxy of each object, will it render faster?

This will be a complex particle system made up of fairly high-res objects, apx 2 min animation..

[Deflaminis]

As long as those proxies are instances of one another, yes it will render faster. I just did a test last night on this actually to see how much faster. With proxies, I rendered 12 billion polys (yes, billion) in 1.5 minutes with GI. It works great...

[zeronove]

just remeber that main scope of proxy is going beyond traditional memory limits not speed; but, yes, in some cases (a lot of proxy instanced) it could be faster

[bardo]

when you reach the memory limit, 3dsmax starts to use the swap file and rendering slow down.

with proxies you save memory so rendering go straight at full computational speed (CPU & memory speed).

Teorically, if you stay inbetween the memory limit, with o without proxies shouldn't do difference.

[Exon]

I exported several objects to seperate vraymesh..

I load one of these into a new scene with Vrayproxy.. It renders fine..

But if I use the imported proxy as an instanced shape for a particle flow source, it only renders the preview faces like I see in the viewport.. How do I get it do render the object solid?

[plastic_]

When the memory limit isn't reached, proxies render slower.

[simmsimaging]

I exported several objects to seperate vraymesh..I load one of these into a new scene with Vrayproxy.. It renders fine..But if I use the imported proxy as an instanced shape for a particle flow source, it only renders the preview faces like I see in the viewport.. How do I get it do render the object solid?

I don't think proxies work with Pflow

[Undersky]

Or, rather, Pflow doesn't work with proxies. Or dummies. Or lights. Or anything that isn't a mesh. And even if it would, you wouldn't benefit from it, since Pflow attaches all the particle shapes to one mesh when rendering. In early versions of max, it was faster and more efficient to render it as one mesh. That's why we can't use Pflow to render vast forests even with "instances" since the memory gets eaten anyway.

There are however scripts that let you bake proxies onto the particle's positions. It will also take into account the scale and rotation of the particles. The problem is that you have to re-bake everytime you change something in the PFlow. And you have to view all of the proxies in the viewport (unless you right-click and hides them, or puts them in a hidden layer).

In the end, multiscatter or something similar is a way better option.

[joconnell]

Particle flow effectively makes a big mesh for the object that gets passed to vray so it'll break the link with your proxies. If you want movement in your objects then bake the particles movement out to nulls and then parent a proxy to each, if you want the objects to be static then either try multi scatter or a script that'll swap your particles for another scene object.

Proxies never render anything faster, if you have the ram to do it your scene will always be faster with just instances since it doesn't keep loading and unloading things from disk. Proxies are a last resort so that you can render massive scenes and take advantage of objects being loaded and unloaded from ram so you can render far more than your computer could normally handle.