Animation: 'TEMP folder is full' -->crash

[kwistenbiebel1]

Hi all,

I try to render an animation using Irrmap/LC.
However, Su crashes just after the incremental LC iteration is done.
Following error message occurs: "Not enough space in your TEMP folder".
It must be that in some way, Vray is flooding the folder with (too) much or too large files...

I don't have this when trying brute force (LC-QMC)but that method takes to long to render out animations.

Any solutions to this?

I am on vista 64 Business and already tried to lower polycount and the res of texture images.

Should I try to render the LC pass and the IRRmap pass seperately and load both solutions for a final rendering, after I manually cleaned the Temp folder?


Thanks in advance,

Biebel

[Jorgensen_cg]

Re: Animation: 'TEMP folder is full' -->crash

Had that error - first got rid of it when I delete some trees witch had alot of faces.

Jorgensen

[kwistenbiebel1]

Re: Animation: 'TEMP folder is full' -->crash

I had the feeling also it had to do with polycount so I got rid of some trees and people as well. But at a certain point, there's a limit to deleting stuff as it makes the scene less credible.
There is no way to make proxies of components and instance them, so I hoped there was another way to overcome the issue of the 'temp' folder.

[Jorgensen_cg]

Re: Animation: 'TEMP folder is full' -->crash

I saw your thread on Sketchucation about using proxy - it is a nice feature - some great scenes

[kwistenbiebel1]

Re: Animation: 'TEMP folder is full' -->crash

Thanks ,
It's my believe that instancing and proxies are a much wanted feauture for Vray.
In (Sk)Indigo it is as simple as making a second component (with just a few polygons) and name it the same as the high poly component you want to see instanced/ proxied, but with the addition of '_dummy' as suffix to that component name.
Skindigo will automatically replace the dummies by the high poly components towards the render engine (64 bit!) at export.
This happens all by just a ruby script.

I hoped to have something similar and easy for Vray.

Until such an option arrives, I am really struggling to avoid crashes in Vray when rendering animations or stills that are medium complex.

I hope there is a solution.



Regards,
Kwistenbiebel

[dalomar_cg]

Re: Animation: 'TEMP folder is full' -->crash

I'll check and see what information I can find about what tempfiles are used/needed. My intuition at the moment is that for some reason we are grabbing files/data on a per frame basis, where they can simply be loaded once and not have to worry about loading/unloading (ie we aren't adding files twice).

In the meantime I would suggest that you render out any prepass light info (LC, IR) separately before hand, save them, and load them directly from the file. For animations, take a look at the tutorial that we have. The concepts are all the same, although you'll have to adjust the FPS via the Output rollout.

[kwistenbiebel1]

Re: Animation: 'TEMP folder is full' -->crash

Thanks Dalomar,
I am already using that method.

First I render the Light cache solution to disk (LC/LC settings) at full framerate.
Then the IRR pass (IRR/none settings)to disk but only for every 10 frames.
Finally I load both solutions and try to render it.
This method works quite well for simple SU files.
For rather complex files the issue stated above is the consequence...


By the way,
instead of changing the framerate for the Irrmap pass, I divide the 'scene transition time' of the SU animation by 10. Same effect.

[joe_b]

Re: Animation: 'TEMP folder is full' -->crash

We place textures that are extracted from Sketchup a folder. I am not sure what version you are running - but I think our official 1.0 release did place them in the temp folder. Our more recent builds place them in Documents and Settings/Application Data/ ASGVIS/VRayForSketchUp/Textures on XP, or c:\ProgramData\ASGVIS\VRayForSketchUp\Textures on Vista.

I am not aware of any other temp file usage

[Jorgensen_cg]

Re: Animation: 'TEMP folder is full' -->crash

Just for information, I have had this error when rendering a still image.