Any news about this environment variable?
24 gb ram to fill… easy… if u render output is at 15-10k pixels.. Im running to shop tomorrow to get extra ram to soften my workflow argh !
But yea the would be great to have that option tbh. It might make it easier for me too..
Thanks, ciao.
Yes, would love to know if Vlado has an update on this. Working on a scene right now that is topping 10GB to render and is only about 1/3 finished - and slowly running out of optimisation options…
I will be able to get you an updated build sometime next week… if you are interested, please email me to vlado@chaosgroup.com
Best regards,
Vlado
Great to hear that. Email is on the way.
thanks Vlado!!! email on its way
Hi Vlado, I’m running out of memory:
I work all the day on a scene, the lightcache was working. I reboot, now the lightcache start, say 91hours and freeze.
I already send you an email, can I have the fix also please?
Hello, sorry we are a bit stressed here (animation deadline on monday), we finally reduce all the textures and desactivated the displacement, it’s working now.
I’m not sure I’m running into the same problem. My problem is that VRay seems to be using up the “Cache” as listed in the Task Manager.
The system has 8GB of RAM.
Max is taking 3.1GB
But the Physical Memory section is as follows:
Total - 8186
Cached - 4051
Free - 0
As far I can tell I have another 3.1 GB free
As a result it’s rendering about 8x slower than on my desktop with 16GB of RAM.
Hi Gavin,
As a matter of fact it looks like you actually don’t have any memory available.
The “Free” memory entry is not the same as available memory, which is an entry you seem to be missing in the Task Manager dialog. Are you using Vista?
If you take a look at the Windows 7 Task Manager screenshot below (taken from a random desktop at my company) you can see how that works in reality. The Free memory is not equal to the Available memory. The way this works is that Vista / Windows 7 reserve memory for running processes in a way they can quickly make it available to the application that needs it (SuperFetch is involved here). Basically this Cached memory will automatically return to the pool of free memory if another application requires more memory.
Memory management in Vista and Windows 7 is a really complex subject! And for that reason it is very hard to grab in a graph or single small management dialog. Memory management is much better than what it was in previous Operating Systems though. Memory is truly dynamic in the latest OSes. Win7 is much better at that than Vista though. Vista seemed to lock a lot of memory unnecessarily which is probably why it seems like you are missing 3.1GB of free mem. That is, if you are actually using Vista.
In your case there is also 4707MB committed to the page file, meaning there is most definitely swapping going on because the physical memory is exhausted. The cached memory seems to actually be in use by 3ds Max or any of your other running processes (including the OS itself). As a result the processor is unable to perform optimally because there’s probably a lot of disk swapping going on which of course is much slower than processor speed.
I think your computer and overall performance would greatly benefit from a memory upgrade 
Anyway, I hope this helps you to understand what is going on and why 
Kind regards
John
does that happen with any scene? or with scenes which heavily rely on dynamic memory? proxies, displacement and so on? if so, have you tried raising the dynamic limit up to something closer to your 8 gigs of memory?
Any news about the patch?
We finish our job, so at the end, I had to shut down the displacement, and lowered the size of the textures.
We notice that the big problem was for the lightcache, we have 12 gigas of memory on each workstation and we are used to put the memry limit to 10, so after a restart of the computer, first lightcache go to 596h, after 2 min stop it, relaunch wait 2 min (it says 5 or 6 hours) stop it, relaunch and it says 30 min. Look like a car engine.
you should email vlado about the patch.
Bertrand, did you receive the patch? I still didnt.
same problem here.
we use distributed render to render the finale Images.
every time a computer runs out of memory we clear the memory by restarting the vrayspanner… it is dirty but it helps.
Hello,
Vlado, I send you an email for the patch, you might be busy right now, but is it posible to have it please?
When did you send it?
Best regards,
Vlado
13/06, 27/06 :), I read somewhere that the next build were for autonm, so if it’s possible to have a new build before, it’s nice.
Thanks
You should have mail now.
Best regards,
Vlado
Thanks!
I’m downloading it, good we
We are running into the same problem with the same settings. Render farm all with 24GB ram. Their page files maintain at 24GB at first, but after they render 8 frames the page file starts to grow eventually hitting the ceiling of 75GB, then they all freeze up and have to be completely restarted. Some become completely unresponsive and have to be shut off via power button.
Any chance there’s an update to this? I saw in the changelog for 2.20.10 that there were memory/multithreading bug fixes and I’m not sure if this was added. We can essentially only render 15-20 frames per node before they reach their pagefile limit. We could raise the pagefile limit but some of of the machines crash before that because their drives only have 40GB of free space. This is on 2.20.10 and it starts adding to the pagefile after 8 frames and during the Building Static Raycast Accelerator phase. The previous frames before that are no problem. Even if we render different sections of the animation, it takes 8 frames, then the pagefile starts filling up. At least with 2.20.10, it’s releasing the pagefile ram after we suspend the backburner job.
Vlado, can I email you and get the fix or has this been implemented in 2.20.10 and something else may be wrong?
EDIT!: Sorry, I meant 2.20.03, NOT 2.20.10.