[ishook]

Maybe not a bug with Fire so much, but the update in general. When I render with Multi-light + color, one of my lights goes nuclear bright. Another co-worker ran into a similar problem with one of his lights just blowing up when using multi-light. This didn't happen before the update.

Just an FYI. I'm trying to figure out EXACTLY what the bug is, lemmi know if you have similar issues.

(I'm rendering out of 3D Studio 2010, on a imac running win7)

[Half Life]

I've seen that problem if you try to use color multilight with an IES emitter (which is not supported).

Best,
Jason.

[Mihnea Balta]

Do you get the issue in the production render, or in the FIRE window? We know about a problem with FIRE and multilight which will be fixed in the next patch, but the production renderer isn't affected by it, so if you see the bug in Maxwell we have to investigate it as a separate issue.

[ishook]

The lights that were blowing up were instanced, so I un-instanced them (instancing in maxwell wasn't on, anyway). That didn't fix it. I also applied a new light material, thinking the material was corrupt. That didn't work.

Rendering without multi-light works fine
Rendering with multi-light works fine
Rendering with COLOR multi-light explodes with light on one of my light objects. (a bunch of thin light planes representing florescent lights.
I can't tell if my other lights are messed up by all of this, I really only noticed it on the lights I just mentioned.

Fire seems unaffected by all of this. Fire is great! I didn't even know multi-light for fire was in the works. It seems like the perfect bridge between standalone maxwell and the 3D software.

[Mihnea Balta]

ML for FIRE isn't in the works, since you can just edit the emitter and the change will show up in FIRE. However, having ML enabled can screw up FIRE under some circumstances. That's a bug we are going to fix in the next plug-in update.

I see now that the issue you are reporting is separate from this, so it will require a separate fix, inside the Maxwell core.

[ishook]

ML for fire WOULD be handy. A direct connection of sliders to the Maxwell materials is key. It's still a pain to go find all the lights in your scene and adjust them by hand, even if you can see live updates in Fire. Just sayin.

I wonder if user-submitted script with multi-sliders would be required to dock to the activeshade window though, you know?

Eitherway - nice work Maxwell team.

[ishook]

NEW fire bug I just noticed:

Fire updates correctly when I move a box, but not when I change the size of the box. I have a box blocking some light, when I make the height of the box different, it doesn't reflect my adjustments in the fire window. If I move it, it does. Basically, fire doesn't know when an object changes shape, just position.

[Tea_Bag]

I can confirm that adjusting object sizes works for me - I used the scale gizmo and it all updates fine! Fire voxelization's then updates the view!
Its not "instant" as the geometry needs to be updated (exported again) for the Interactive window - where everything else like light,materials,camera is
instant to the view

EDIT-This is ref to studio my bad should of seen it was from a plugin

[Mihnea Balta]

That's a max limitation. Max doesn't tell plug-ins what changes when an object is modified, so we cannot distinguish between object movement and mesh modifications. We had to pick between always exporting the mesh at every change, even when you just move it, or exporting just the position, missing geometry updates. We picked the second option, so that moving large objects around doesn't slow down Max. For the next update we will add an option which allows users to decide between the two modes. Until then, the only way to see mesh updates is to close the FIRE window and reopen it.