out of mem solution?

[STRAT]

whilst running out of RAM on a large render, someone suggested to up the dynamic memory value in vray's system tab. Spot3d's official explanation is -

 

"Dynamic memory limit - the total RAM limit for the dynamic raycasters. Note that the memory pool is shared between the different rendering threads. Therefore, if geometry needs to be unloaded and loaded too often, the threads must wait for each other and the rendering performance will suffer."

 

What does this mean? and how/when do i use it? (the default setting is 400mb)

[BrianKitts]

I've had a couple of scenes where vrayProxy's weren't an option for memory managament, so I changed the memory to dynamic and bumped the max up to 2000mb. It does slow your overall render time a bit and you will see the rendering dialog jump back and forth between "rendering image" and "loading/unloading geometry"..... but it keeps you from crashing and allows you to get a final image rendered out.

 

I have 4G of ram, so I've never had a problem with taking the dynamic max up to 2000mb, I'm not sure what happens when you take it over the amount of ram in your machine....

 

I normally resort to rendering to a .vrimg file and turning off the frame buffers though before I switch from static (or auto) to dynamic geomtery if I am having issues with running out of ram

 

So to answer your "when" question, I would say when all other tricks have failed (proxy's and vrimg) to conserve enough ram to complete an image.

[STRAT]

 

I normally resort to rendering to a .vrimg file and turning off the frame buffers though before I switch from static (or auto) to dynamic geomtery if I am having issues with running out of ram

 

So to answer your "when" question, I would say when all other tricks have failed (proxy's and vrimg) to conserve enough ram to complete an image.

 

thanks man

 

in vrayforc4d i dont have proxys yet. what is vrimg?

 

looks like i'll bump up the value a couple of gig next time i'm struggling then

[rivoli]

a low memory limit it's a problem when rendering displacement, proxies, fur or any other object which require dynamic memory. vray always uses dynamic memory for such objects, it doesn't matter which type you set (auto, static..).

but this have nothing to do with a rendering that crashes because it runs out of memory.

a good thing to do in those cases it's rendering directly to vray image format unchecking render to memory frame buffer. vray will write the buckets directly on the drive, saving all the memory needed to store the rgba channels and any other element in the vfb (which can be quite a bit with high res images).

there are other things one can do to save memory, like using instances, proxies, precalculated maps and so on. but of course it depends on your specific scene.

 

edit:

looks like I'm very slow typing, I'd do exactly what Brian said.

[gfa2]

thanks man

 

in vrayforc4d i dont have proxys yet. what is vrimg?

 

looks like i'll bump up the value a couple of gig next time i'm struggling then

 

You guys are missing out by not having proxy and vrimg, hopefully they'll implement that for C4D soon. vrimg is an image file format that Vray writes too that is useful for large scenes because it writes to disk as it renders...very helpful for memory issues.

[Lebjos]

I have a question regarding this issue, but not directly to the memory rollout in vray. I have a machine with 4 gigs of ram, but due to my operating system being 32 bit only about 3.5 or 3.12 gigs are visible to windows. When I start to render does max and vray actually utilize the missing percentage of ram?

 

The thing that confuses me about this is my laptop has only 2 gigs of ram and sometimes crashes on renders, but the same renders on my 4 gig machine seem to finish just fine. Would bumping up the memory to 2000mb and changing it to dynamic fix the crashing problem on my laptop?

 

thanks