High memory usage Vray 1.5f 500k polys

[Paul Oblomov]

1.5 final max9 x64 4gb of ram
Working on project right now. 500k polys and max eats 6gb+ on it. Nothing big just a small cell phone. But everytime I start rendering (preview only) max eats more and more. Transforming verticies takes nearly 15min and then I make 3dsmax reset. This is first time I experience this kind of problem. As I remember RC4-5 didn't suffer from this.

Maybe problem is in npower powernurbs. Working on it...

[instinct]

I'd suggest converting powernurbs to editable meshes prior to final rendering. As the tesselator as almost all tesselators is single threaded it's a major performance hook. And vray does extremly well with a lot of Geometry (rendering a 7k pic of an 8mio poly scene as i type :P ), but it cant help PNurbs tesselating. To do so you can use the Viewport tesselation settings to find a good tesselation and then simply convert it to editable mesh (use "Show mesh" instead of "both" to see what kinda mesh you're creating).

If you need any assistance with the settings lemme know.

Regards,
Thorsten

[Paul Oblomov]

Using npower for a year Never had this problem before. I can't convert to polys on some object parts.

Still looking

[instinct]

Did you upgrade PNurbs recently ? As it really sounds rather like a PNurbs problem then like a vray problem

Regards,
Thorsten

[Olli96]

well, i had something similar some days ago (RAM usage problem), and couldnt really fix it. i wasnt using pnurbs, everything was fairly basic, shaders, geometry nothing fancy at all but the ram usage went up the roof. the only way to fix was to render it on a machine with lots of ram...

Olli

[Paul Oblomov]

Upgrades - no. I can't afford to do this, as deadline - monday.
Build 280.
Now it makes me mad - render, render, render..... hehe reset. Restart max. Will try RCx later this day.

P.S. Multithreaded tesselation - this is da npower feature (as I remember).

[Paul Oblomov]

well, i had something similar some days ago (RAM usage problem), and couldnt really fix it. i wasnt using pnurbs, everything was fairly basic, shaders, geometry nothing fancy at all but the ram usage went up the roof. the only way to fix was to render it on a machine with lots of ram...

Olli

Did max take more and more of RAM ?

My record was 9.342.1 mb It went from 1.5gb to 9+ Not sure is this a npower issue nor Vray, but there's smth strange. RC won't be used in our pipeline for this project.
Just can't. Asked already

There's lots of multisub mats, two vrayblend mats and lots of glossiness. Every object is mat id wise. Some smooth issues etc.

[instinct]

Well in theory yes. The Tesselator itself is partially multithreaded. The preparing for rendering by max isnt tho! If you import cad files and monitor the performance meter in the taskmanager you can clearly see when max is working and when PowerNurbs is working :P

AND in addition not all Bundles have multithreaded tesselation. Only PTrans Advanced and Pro do, the smaller packages dont (at least PTrans Standard does not for sure)

Regards,
Thorsten