You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, this does not appear to be as easy as I had hoped. Currently sorting is done based on an attribute of the object, either the 'Sort' property which the script adds (Sort Order) or the actual name of the object. You can then select how sorting works. I had hoped the collection an object belongs to could be treated the same, but that does not appear to be the case. Specifically, an object can belong to multiple collections, so treating the collection as a property of the object is not simple.
Another option I looked into was to output in the order that they appear in the outliner window. You still have the possibility of duplicates, but that could probably he handled. The bigger issue is that the outliner appears to be tied to the context. The script needs to be able to output all scenes regardless of the current context. I did not dig too deeply here, and I may come back to it, but depending on context becomes problematic.
So in short, this is not something that will happen soon. I am still personally interested in how collections can be used to make modelling for Orbiter cleaner, so I am not abandoning this. Just it won't be anything I implement in the near term.
Is it possible that the groups are sorted in the following order?
eg. I have 2 collections and want the groups of the 1st collection to be at the beginning and then the groups of the 2nd collection.
Scene Collection
____First Collection
________Mesh01
________Mesh02
____Second Collection
________Mesh01.001
________Mesh02.001
Currently the groups are sorted by their names
Mesh01
Mesh01.001
Mesh02
Mesh02.001
But I want them like this
Mesh01
Mesh02
Mesh01.001
Mesh02.001
Maybe this helps
https://blender.stackexchange.com/questions/144928/how-to-list-all-collections-and-their-objects
The text was updated successfully, but these errors were encountered: