Vray Proxy

I hope this will help all of you guys. Any problem encounter with nevermodeledtrees just pm me. Thanks guys for viewing.
Special thanks to Ichiban Sensei v_wrangler and Sensei Torvicz.

Nice new avatar sir cloud.

very nice sir salamat sa pagbahagi

May I ask please, what Max version is this?...

galing mo talaga sir Galaites! para sayo! sir baka pag ganito post mo, bukod sa pics, lagay ka din downloadable pdf. thanks po. more power!

If you'd just check "Automatically create proxy" (Assuming you saved the original max file prior to proxi'ing), yo ucan do away with the extra reloading of the file and the mapping part.

yup as what master v had said just check the automatic create proxy and the materials will come along with it no need to reinstate the materials.

cloud20 wrote:May I ask please, what Max version is this?...

max 9 bro.

Unfortunately much of the parameters in this tutorial ay panahon pa ni kopong kopong. It is always best to consult the current manuals at:

http://www.spot3d.com/vray/help/150SP1/vrayproxy_params.htm

Much of the problems encountered might have been fixed in the current releases.

Thanks for sharing bro.

To add, this technique is only good if you are using a single mesh with multi-sub material.

bokkins wrote:

cloud20 wrote:May I ask please, what Max version is this?...

max 9 bro.

Ah. That explains the "0" poly & vert count. Try that on higher versions & you won't get a zero count. AFAIK. I've come across that blasted zero count here on CGP once. Gave me a headache.

Misleading nanaman ito. Its not funny anymore...

So much for the proxy-master...

for more info regarding this topic ..

http://www.cgpinoy.org/vray-for-3d-studio-max-tutorials-f35/vray-proxy-made-easy-t4436.htm

cloud20 wrote:

bokkins wrote:

cloud20 wrote:May I ask please, what Max version is this?...

max 9 bro.

Ah. That explains the "0" poly & vert count. Try that on higher versions & you won't get a zero count. AFAIK. I've come across that blasted zero count here on CGP once. Gave me a headache.

Misleading nanaman ito. Its not funny anymore...

So much for the proxy-master...

AFAIK, the reason it's zero dude cloud is because all the objects in the scene are vray proxy.
Although di ko pa na-try yung higher versions...I dunno kung anu naka-display dun...

To add, I always use automatically create proxies.

torvicz wrote:

cloud20 wrote:

bokkins wrote:

cloud20 wrote:May I ask please, what Max version is this?...

max 9 bro.

Ah. That explains the "0" poly & vert count. Try that on higher versions & you won't get a zero count. AFAIK. I've come across that blasted zero count here on CGP once. Gave me a headache.

Misleading nanaman ito. Its not funny anymore...

So much for the proxy-master...

AFAIK, the reason it's zero dude cloud is because all the objects in the scene are vray proxy.
Although di ko pa na-try yung higher versions...I dunno kung anu naka-display dun...

To add, I always use automatically create proxies.

it will automatically create 10k poly sir any object you have proxy on higher version of max.. in this reason i used xref instead of proxy to get a zero poly but my big problem in xref hindi ko na cia maimove i need to merge it before ko maimove yung object into different location...

@dude andro: I see...But I don't see why you use xref over vray proxy.
that doesn't make sense(in a way...) I'm talking about rendering...

I only use xref so I could manage the scene easily(option of turning it on and off in the scene is very handy.) But when rendering, I go for proxies...


Yung pag move ng object, no choice but either merge it or open the xref file.
I normally open the xref file than merging it.

torvicz wrote:@dude cloud: I see...But I don't see why you use xref over vray proxy.
that doesn't make sense(in a way...) I'm talking about rendering...

I only use xref so I could manage the scene easily(option of turning it on and off in the scene is very handy.) But when rendering, I go for proxies...


Yung pag move ng object, no choice but either merge it or open the xref file.
I normally open the xref file than merging it.

you mean sir mas mabilis po irender yung proxy kaysa a xref? ganun po b yun sir?

there's a setting in the proxy conversion parameters where you can set how many polygons you'd want displayed. This is a one time setting, though.

The number of polygons displayed in the statistics is dependent on the display parameters in the modify panel. If it's a bounding box, then you'd get 6. If its preview from file - you get what you set during conversion. If its set to display a point - then you get none.

The number of polygons here has no effect really in rendering as the proxy works during rendering. The object is precalculated anyways. The only thing to worry about is the limit of your graphics board. So if you don't want your million proxy instances hogging display, set it to box or point.

andro111985 wrote:

torvicz wrote:@dude andro: I see...But I don't see why you use xref over vray proxy.
that doesn't make sense(in a way...) I'm talking about rendering...

I only use xref so I could manage the scene easily(option of turning it on and off in the scene is very handy.) But when rendering, I go for proxies...


Yung pag move ng object, no choice but either merge it or open the xref file.
I normally open the xref file than merging it.

you mean sir mas mabilis po irender yung proxy kaysa a xref? ganun po b yun sir?

di naman dude sa bilis, pero alam ko mas madaling nagca-crash ang file pag di naka proxy.
(something to do with memory...)

dude verts, please clarify....ty

torvicz wrote:

dude verts, please clarify....ty

Thats the setting below. (Faces in Preview)



There goes the display setting which is common I guess even in the older versions.

dude verts, I'm talking about the speed of proxy in rendering compare to xref. mas mabilis ba? yan din tanong ni dude andro....

TIA

bokkins wrote:Thanks for sharing bro.

no worries.

bokkins wrote:To add, this technique is only good if you are using a single mesh with multi-sub material.

thats right.

My apologies, I got confused.
I won't have the figures now because I have no time to test but base on experience it's faster than if you have the objects raw in the scene.

The greatest benefit in speed you can find when you are rendering lots of polys, It will take a hit in preprocessing, tesselation if you have nono-proxy scenes and the tendencies are max will crash when it loses ram. It is the exact opposite when you have proxies.

Xref's are of course a good way to minimize your viewport resource because they allow you to bring in otehr objects at render time. the problem with xrefs is that they bring in the objects as a separate max file and you will be limited in terms of the amount of geometry max will allow. Vray proxies goes around this limitation because the object is recalled in the rendering process (VRAY) and they aren't in the scene - you just see their display. So basically allowing you to render more geometry than max would allow.

Xref'n a vrayproxy is like making another highway when there's already one in the same location. The only way I'd see one using xrefng a vrayproxy over directly calling the proxy in the scene is when you don't want to tinker with the node inside the scene.

FYI, there's a lot of other ways to proxy an object, XREF is one, MR has one and the versatile Substitude Modifier.

v_wrangler wrote:My apologies, I got confused.
I won't have the figures now because I have no time to test but base on experience it's faster than if you have the objects raw in the scene.

The greatest benefit in speed you can find when you are rendering lots of polys, It will take a hit in preprocessing, tesselation if you have nono-proxy scenes and the tendencies are max will crash when it loses ram. It is the exact opposite when you have proxies.

Xref's are of course a good way to minimize your viewport resource because they allow you to bring in otehr objects at render time. the problem with xrefs is that they bring in the objects as a separate max file and you will be limited in terms of the amount of geometry max will allow. Vray proxies goes around this limitation because the object is recalled in the rendering process (VRAY) and they aren't in the scene - you just see their display. So basically allowing you to render more geometry than max would allow.

Xref'n a vrayproxy is like making another highway when there's already one in the same location. The only way I'd see one using xrefng a vrayproxy over directly calling the proxy in the scene is when you don't want to tinker with the node inside the scene.

FYI, there's a lot of other ways to proxy an object, XREF is one, MR has one and the versatile Substitude Modifier.

thank you very much for your explanation sir...

there you have it dude andro....malamang talagang magcrash ang max pag xref lang compare to vray proxy....thanks dude verts!

torvicz wrote:there you have it dude andro....malamang talagang magcrash ang max pag xref lang compare to vray proxy....thanks dude verts!

oo nga sir.. from now on i will change my method.. thanks for helping me to clarify this one sir..

v_wrangler wrote:My apologies, I got confused.
I won't have the figures now because I have no time to test but base on experience it's faster than if you have the objects raw in the scene.

The greatest benefit in speed you can find when you are rendering lots of polys, It will take a hit in preprocessing, tesselation if you have nono-proxy scenes and the tendencies are max will crash when it loses ram. It is the exact opposite when you have proxies.

Xref's are of course a good way to minimize your viewport resource because they allow you to bring in otehr objects at render time. the problem with xrefs is that they bring in the objects as a separate max file and you will be limited in terms of the amount of geometry max will allow. Vray proxies goes around this limitation because the object is recalled in the rendering process (VRAY) and they aren't in the scene - you just see their display. So basically allowing you to render more geometry than max would allow.

Xref'n a vrayproxy is like making another highway when there's already one in the same location. The only way I'd see one using xrefng a vrayproxy over directly calling the proxy in the scene is when you don't want to tinker with the node inside the scene.

FYI, there's a lot of other ways to proxy an object, XREF is one, MR has one and the versatile Substitude Modifier.

Sensei V...thanks for sharing (sa wakas sinagot nyo na po yung imi ga nai.