Hi I remember reading somthing about dual 265 that don’t use 100% of cpu usage when rendering, I have this problem with my 3 new machines.
Anyone got this problem?
or somone know where the thread that had somthing about it?
Try up’ing your dynamic memory limit.
Are you using vray displacements?
yes i’m using vray displacment.
and up’ing your dynamic memory limit to what value? riht now it on default 400…
its the displacement causing this
I’d try doubling it to start off. Keep inreasing the dynamic memory limit until it renders with all cores @ 100%. Max/Viz will start to crash if you run out of memory though.
so you’re saying no displacment with dual duals?
I have dual dual 280’s with 4 gb ram (w/xp64) and I render displacement all the time… 2d displacement even. The trick is to crank up the dynamic memory as has been suggested. If your CPU is not at 100% then you are having memory problems and rendering is most likely “stuck”.
With displacement scenes I usually turn the dynamic memory up to about 3000 mb, though Vray doesn’t usually need to go that high. But it does keep it from getting stuck.
Also, try smaller render buckets in frame buffer, and smaller strips (like 10px or less) in backburner.
I have a dual 265 with only 2 g ram , on win xp.
I’ve tried turning into dynamic memory with 1000 mb , and the cpu did came to 100% and then max crashed , if i set it tp 800mb it use around 80% and still crash …
It only happanes in this specific scene …
can’t get it over 50% without crashing.
well … Here are my findings.
I’ve used 3d displacment and the cpu didn’t go over 50 % , turn it into 2d displacment and cpu is back to 100%.
can chaos give us an explanation whats going on with that?
Valdo explained this in the past for the xeon thread of this nature.
Displacement and Vray Fur are not multi-threaded processes.
From my experience, a render with displacement will run multithreaded no problem unless you have the sampling set too high on the discplacement, or the resolution too high. As said by others, the solution to this is to up the dynamic memory. Another fix to try would be to make sure your mesh that you are displacing has a good topology, ie all quads.
Try increasing the edge lenght under 3d vray displacement to 8 or higher and then render.
While rendering the displacement is a multithreaded process, generating the displaced geometry is not. If V-Ray needs to constantly destroy and re-create displacement geometry because it runs out of RAM, then most of the time only 1 thread will be used and it will be busy to generate/destroy displaced triangles.
Best regards,
Vlado