- Mon Sep 14, 2015 8:57 pm
#388227
Hi Jeremy,
there are a few things about the rhino-FIRE interaction that I am not quite sure about, right now I am seeing some strange updates with subD options so I'll start with this:
1- subdivison: when it is unchecked Fire does restart but still shows subdivided mesh. same goes for crease/interpolation setting; FIRE restarts on a change but actually nothing changes until a full reload.
another strange thing with subD: if I assign a material to an object, start fire, assign a new material to it, and then change any subD setting of the object, FIRE will restart showing the previous material assigned.
a little workflow wish: when FIRE is running and subD is enabled on an object it is automatically set to Catmull. However this is often not the desired option, and may produce errors/stop fire. It would be helpful if we could access the options without the check set.
2- subdivison errors: is there a way to select the meshes/objects that cause subD to fail when FIRE starts? right now I only see the warning but finding the questionable objects is often difficult once subD is turned on for many objects. External maxwell will render anyway, but I have had situations where FIRE would get stuck, in fact I think inside Studio FIRE will not work when there are subD errors detected in comparison to FIRE in Rhino.
3- pretesselated displacement: when there is an object with pre tesselated displacement assigned rendering in FIRE, the change of any other scene material's parameter triggers a full FIRE restart. (displacement precalculated again)
so basically FIRE can't be used with that type of displacement, everything gets really slow.
Checking inside Studio with the same scene, this problem does not show itself.
there are a few things about the rhino-FIRE interaction that I am not quite sure about, right now I am seeing some strange updates with subD options so I'll start with this:
1- subdivison: when it is unchecked Fire does restart but still shows subdivided mesh. same goes for crease/interpolation setting; FIRE restarts on a change but actually nothing changes until a full reload.
another strange thing with subD: if I assign a material to an object, start fire, assign a new material to it, and then change any subD setting of the object, FIRE will restart showing the previous material assigned.
a little workflow wish: when FIRE is running and subD is enabled on an object it is automatically set to Catmull. However this is often not the desired option, and may produce errors/stop fire. It would be helpful if we could access the options without the check set.
2- subdivison errors: is there a way to select the meshes/objects that cause subD to fail when FIRE starts? right now I only see the warning but finding the questionable objects is often difficult once subD is turned on for many objects. External maxwell will render anyway, but I have had situations where FIRE would get stuck, in fact I think inside Studio FIRE will not work when there are subD errors detected in comparison to FIRE in Rhino.
3- pretesselated displacement: when there is an object with pre tesselated displacement assigned rendering in FIRE, the change of any other scene material's parameter triggers a full FIRE restart. (displacement precalculated again)
so basically FIRE can't be used with that type of displacement, everything gets really slow.
Checking inside Studio with the same scene, this problem does not show itself.
Last edited by dk2079 on Fri Sep 18, 2015 6:21 pm, edited 2 times in total.