Maxwell Render | Official public forum

When using fire on a Mac pro 12 core (24 threads) fire does not use all of the available power. All 24 threads appear to cap at around 80%
When rendering in Maxwell render however. All 24 threads are fully saturated.
Is this intentional?

Thanks.

In order to be interactive, Fire must have update points which are much more densely-timed than those used in Maxwell Render. At each update, the render has reached a stopped state, in order that UI code can (a) read & update the image, and (b) have a chance to indicate whether whether it wants to change something in the scene and restart, or just to continue rendering the scene as-is. During this time, render threads are sleeping, and this is why you see lower CPU saturation with Fire.

Thanks for the info.