[polynurb]

as the title says, i experience some resets when autosave kicks in while fire is running.
also some other things like unlocking objects restarts it sometimes.

for the type of work i do right now (very heavy scene) i would really like a button to reduce all fire-updates to the maxwell side of things (material-environment-scene edits).

atm using fire on big scenes still feels a bit like juggling eggs

thnx,
daniel

[JDHill]

I don't see that happening here with those particular actions, but it is possible. The thing is, there is no way to do what you ask -- there is no bright line separating Maxwell-related changes from non-Maxwell-related changes. For example, you may have noticed that material assignments work with Rhino's Undo/Redo system; this happens in response to change notifications from Rhino, and the plugin needs to react in order to keep all the necessary data synchronized. Such changes may be initiated by Rhino, or by any other plugin. When that happens, the rendering has to be stopped, then restarted, after data has been synchronized.

As much as possible, the plugin filters out changes which it believes cannot affect the rendering, but this is not an exact science; obviously, there are factors in play in your situation where the plugin is not able to prove that a change can be ignored. I would need to be able to identify what that is before I can do anything about it though, so if you have any clues, that would be good. One thing you might try using is the Lock to current camera button in the Fire window. There is no guarantee that changes won't be made to the current view during a save or other operation, necessitating a restart, but it might narrow things down.

[polynurb]

thanks Jeremy, for the immediate&detailed explanation.

in this scene here whenever i unlock something fire restarts.
I'll try things out an let you know.