Library Override Included obstacle causes bpy error about blender-flip-fluids HOT 5 CLOSED

Thanks for the report! I am able to reproduce the error with the supplied Blend files.

It looks like this issue is caused by a change between the previous FLIP Fluids 1.6.1 and the latest version 1.6.2 and is a side effect of a bug fix. The bug fix involved making a change that requires data of the FLIP Obstacle/Inflow/Outflow/Fluid/ForceField type objects to be modified before baking a simulation. Linked objects are not allowed to have their data modified, and this is what is triggering errors.

I think we may be able to add a workaround to fix this type of issue. We'll see what we can do and try to have this fixed for the next FLIP Fluids 1.6.3 version, which is planned for release in about two weeks.

Note: Linking FLIP Domain type objects will not be supported, as this type of object requires modifying its data in order for the addon to function.

from blender-flip-fluids.

Sounds good, glad I was able to help reproduce it quickly! I don't ever link in domain objects, mostly just Obstacle, Inflow, and Outflows.

I have a work-around for right now (making objects local), so it's not holding anything up.

Thanks very much for your work on the add-on and looking at this so quick!

from blender-flip-fluids.

Perhaps an idea. For an addon i did some work on, i made a small edition for when linked armatures are used. It's makes a copy of the linked armatures and puts it a new collection, only then could it be used for actions needed.

I know it's not the same object type as this addon uses, but i think the principle idea is the same. Unless you cn do library overrides on this type. I do not know if that is possible

from blender-flip-fluids.

Thanks for the suggestion! That's a solution that I had not thought about. In our longer-term development plans we had wanted to be able to improve support for linked objects and I think this solution could work well with this idea.

from blender-flip-fluids.

Just had a chance to add a fix for this issue. This fix will be included in the next stable release, FLIP Fluids 1.6.3 which is planned for release in about one week.

from blender-flip-fluids.