Your Model May Be Outdated
Using Bonsai v0.8.4, it seems that I can restructure the Outliner at will, save both .blend and .ifc (using Ctrl-S), and reopen with the saved structure of the Outliner intact. I know the Spacial Decomposition tool is now the go-to as far as the structuring of the IFC elements is concerned.
If I KNOW that the .ifc has not been edited prior to reopening the .blend, is it safe to ignore the "Your Model May Be Outdated" warning? Is the "RuntimeError: Instance #XXXX not found" error still able to rear its head?
Essentially, I guess my question is: "Just how de-coupled is the Outliner?" Is there code under the BB hood that still relies on the structure of the Outliner?
Comments
AFAIK completely.
Means everything you restructure in Outliner inside the IFC Collection will be basically lost when you reopen the IFC. And if I got that right that, if you force that by saving the Blend file and opening the IFC inside that Blend, you will get even that warning.
In the past you manually controlled the Spatial Structure through Outliner manually. There are threads that deeper structures caused lags and that the sync with Blender was unreliably. To avoid these problems IFC Collection got decoupled and as you said "Spacial Decomposition tool is now the go-to as far as the structuring of the IFC elements is concerned".
I do not touch or change the IFC my IFC Collections for those reasons.
But I would really love to get one extra IFC Hierarchy Level under Stories - for the Element Classes.
(Not sure if deeper Collection hierarchies, after decoupling, would still be problematic for Bonsai on Blender)
I'ld like to know that too.
I often see tutorial videos while such out of date warnings are active and ignored, but I think they will be there for a reason ....
I can use Spacial Decomp to create spaces and they ALL show up under the SAME "IfcSpace" collection. And, they'll still show up in that collection AFTER that collection is (manually) nested under, for example, "IfcBuildingStorey/My Storey".
My takeaway is that collections can be created and nested at will and IFC element Blender objects can be placed in your collection of choice, and those collections and object placement lives through the subsequent loading of the .blend, PROVIDED the .ifc is not changed outside of the .blend in which it is loaded.
Unfortunately, it seems that errors down the road while using this sort of workflow have the potential to be hazardous to your health!
UNLESS - "refreshing" the loaded .ifc is possible?
Note that I am thinking/speaking of potentially using this as my workflow, and thus leaving it on myself to ensure I don't edit the .ifc elsewhere.
The warning displays whenever it detects both a Blend and an IFC simultaneously. If you know what you're doing, ignore it :)