- Fri Nov 26, 2010 1:17 pm
#333524
Hi,
Just recently I've noticed that the Maxwell render processing isn't technically quitting when the render stops when launched via the opening of a .mxs file. It looks like it's closing because the Maxwell render app itself has quit. What happens is some process is transferred to the kernel_task which then utilises 150-200% of the CPU usage on a quad core Mac Pro.
If I subsequently launch another render via Maxwell render 8 out of 10 times my machine kernel panics at some stage during the render. I have to hard reset the Mac Pro.
However, if I launch a render via a host application such as C4D I have no such issues. The problems only occur when starting or resuming renders via Maxwell render itself. I've not tried this via the Studio app as I never have the need to use it.
Matt
Just recently I've noticed that the Maxwell render processing isn't technically quitting when the render stops when launched via the opening of a .mxs file. It looks like it's closing because the Maxwell render app itself has quit. What happens is some process is transferred to the kernel_task which then utilises 150-200% of the CPU usage on a quad core Mac Pro.
If I subsequently launch another render via Maxwell render 8 out of 10 times my machine kernel panics at some stage during the render. I have to hard reset the Mac Pro.
However, if I launch a render via a host application such as C4D I have no such issues. The problems only occur when starting or resuming renders via Maxwell render itself. I've not tried this via the Studio app as I never have the need to use it.
Matt
- By Edward Leibnitz
- By Forum Moderator