User avatar
By JamesColeman
#349377
Sorry to be annoying Jeremy but I've found this bug again. It's not seriously interrupting my workflow but I thought you should know.

When I create a new Maxwell emitter material in Cinema (Maxwell material editor > create > standard > emitter) and then remove the emitter layer, I get this:

Image

and

If I create a Maxwell emitter material in the same way, then from that new emitter material create a new Maxwell material (Maxwell material editor > create > new material) I get this:

Image

Sometimes it's serious enough to crash Cinema altogether and it wont force quit, a computer restart is required.

Thanks
James

Cinema 13.029
Maxwell 2.6
Maxwell for Cinema 4D 2.6
OSX 10.6.8 64-bit
By JDHill
#349379
Thanks James, so apparently, this has resurfaced. I observe it here (on OSX only), but not to the degree that you describe -- less crazy noise, no crashing, but apparently the same thing. Would you mind confirming for me that after removing the emitter, if you switch to another preview scene, it then renders as expected (i.e. the preview object renders as pure black).
By JDHill
#349380
I have another repro, but not involving the plugin:
  1. open Studio
  2. add a camera
  3. disable environment
  4. import a plane and a sphere
  5. add an emitter to 'Default'
  6. assign 'Default' to the sphere
  7. start rendering in Maxwell Fire
  8. remove the emitter from 'Default'
If there is no BSDF in the material, then when you remove the emitter, Studio will remove both the emitter and its parent layer. In that case, nothing will happen until you then add a new layer (it will come with a new BSDF); doing so will trigger the bug. On the other hand, if in either case, you disable the emitter, rather than removing it, you should get a message from Studio saying that there are no light sources in the scene.
User avatar
By JamesColeman
#349387
JDHill wrote:Thanks James, so apparently, this has resurfaced. I observe it here (on OSX only), but not to the degree that you describe -- less crazy noise, no crashing, but apparently the same thing. Would you mind confirming for me that after removing the emitter, if you switch to another preview scene, it then renders as expected (i.e. the preview object renders as pure black).
Confirmed that changing the preview scene renders as expected.
JDHill wrote:I have another repro, but not involving the plugin:
  1. open Studio
  2. add a camera
  3. disable environment
  4. import a plane and a sphere
  5. add an emitter to 'Default'
  6. assign 'Default' to the sphere
  7. start rendering in Maxwell Fire
  8. remove the emitter from 'Default'
If there is no BSDF in the material, then when you remove the emitter, Studio will remove both the emitter and its parent layer. In that case, nothing will happen until you then add a new layer (it will come with a new BSDF); doing so will trigger the bug. On the other hand, if in either case, you disable the emitter, rather than removing it, you should get a message from Studio saying that there are no light sources in the scene.
Confirmed again.

Something I noted: Cinema only crashes with the bug when CPU usage is high. Can you try recreating the bug with Maxwell rendering (anything) in the background? (Production engine, not Fire).
By JDHill
#349389
No, it doesn't seem to make any difference here having Maxwell running. Regardless, I've reported this to the core guys, so they'll be checking it out -- thanks for the precise reporting.
render engines and Maxwell

well I don't think AI will remain like it is now. […]

Help with swimming pool water

Hi Andreas " I would say the above "fake[…]