Page 1 of 1

Bug - Material Editor and 2nd instance of max/octane

Posted: Sun Aug 24, 2014 9:18 am
by WhaleHunter
Hi,

Open any scene, start rendering.

Open 2nd instance of max (with octane set as the renderer and materials are in the material editor)
open material editor in 2nd instance of max.

Result: Often the material editor / max goes "not responding" in 2nd instance / file=comatose. This can sometimes resolve if you close the render in the other max instance. Not always possible to close down the render window as it is doing important things like below.

Other case:
Network rendering to your workstation while still working in copy of max. Open material editor, same not responding result.

Please consider a fix for this if you can reproduce.
Thanks in advance.

Regards,
N.

Re: Bug - Material Editor and 2nd instance of max/octane

Posted: Sun Aug 24, 2014 9:05 pm
by Karba
WhaleHunter wrote:Hi,

Open any scene, start rendering.

Open 2nd instance of max (with octane set as the renderer and materials are in the material editor)
open material editor in 2nd instance of max.

Result: Often the material editor / max goes "not responding" in 2nd instance / file=comatose. This can sometimes resolve if you close the render in the other max instance. Not always possible to close down the render window as it is doing important things like below.

Other case:
Network rendering to your workstation while still working in copy of max. Open material editor, same not responding result.

Please consider a fix for this if you can reproduce.
Thanks in advance.

Regards,
N.
This is not a good idea to render things in parallel.
main render and material preview use GPU, which can't split tasks properly.