I’m having some real major issues with displacement - not just with SP3, it happened with SP2 as well.
Basically I’m applying displacement to a large area of carpet. Maybe a bit ambitious to start with (?), and I’m leaving all the settings as default. Both computers I’m rendering on have 16gb of ram.
Test renders at 1k go without a hitch.
So I then up the resolution to 3k.
I set the dynamic memory limit to 4000 and things start off ok. I get several rounds of ‘unloading geometry’ during lightcache with my ram usage at 6.85gb. Then about three quarters of the way through the IR map calc, with the ram usage still at 6.85gb I get ‘unloading geometry’ and then it crashes.
So I then admit defeat and delete all the displacement from all the objects in the scene and also remove all traces of it from the materials.
When I do another render I still get ‘unloading geometry’ as if the displacement is still there. It also ends up crashing at the same place again.
I’ve even tried merging the old file into a new one to see if it will leave the ‘phantom’ displacement behind, but it doesn’t.
So I uncheck displacement in the Vray global switches menu, in hope of switching off all traces of displacement. But I get exacly the same thing happening - unloading geometry and crash.
Is there a bug that doesn’t allow you to remove displacement once a scene has crashed?
Not sure if this is the problem, but if you have 16 gb of ram you can set the dynamic limit alot higher than 4000… try 12000, then vray shouldnt have to load/unload geometry all the time.
Also, if youre using 3d displacement, try 2d instead. It uses alot less memory.
/k
untrue, Dmitry.
I myself set it to 16gb to avoid another issue happening with very dense geometry as base, and it always worked.
64bit though.
You can check the wiki of where you are now for infos
don t take me wrong, i must have misunderstood ur previous post, nonetheless i am pretty sure the ram usage goes above 3000, maybe i can slip in some image…again
Well, as ene pointed out, it does go above 3gb.
The 32bit does not, of course.
The only thing i can think of is that you’re using that one, but then, i know you know what you’re doing, so it’s unlikely
What version (exact build number) does that?
LMAO XD
I have to say i didn’t realise it was a lose-lose situation i was putting him into
Let’s say i could also think about overwork, stress, morning blues that could have him getting that one wrong.
Or, it goes without saying, me never realising it’s actually as Dmitry says it is.
And ene is photoshopping screenshots like mad, ofc