Reply To: Understanding the scene collections and heirarcy

Can I first say how blown away I am by the level of support and help shown here – I’m really grateful. So many places say they have a community but very few actually do. I’m still very new here but the courses & support are incredible value for money. 
I tried to have a play following those instructions and immediately hit a wall of confusion.

My end goal here is to be able to easily show/hide the head and body while I’m working on the other pieces.

Shift+H is good but then Alt+H turns on everything even if it had previously been hidden ie Shift /Alt H is a toggle that applies to all objects regardless of their starting (viewable/hidden) state. Is there no way to toggle between one collective state and the previous state?

So… looking at the advice above I added the Pot and Body to a new collection. However only the parent was clickable in the new collection and all the children were instanced. I think this might be cos I only clicked the parent and dragged it to a new collection? The upshot was if I turned off visibility of the new collection only the parents were hidden and not the children.

So I tried to delete the collection and start again but all that did was delete the container and left the objects! 

Now I had 2 copies of body and pot objects. This separated the parent from my hi res collection but the children stayed in the hi res collection and were instanced(I think?) as children of the parent outside of the collection.

So then experimented in how to delete the 2nd copy and instanced children without deleting the original parent & children. 

Finally seemed to manage this by unlinking the original (if I try and unlink the parent copy it deletes everything!)

And then the really weird thing is that after unlinking the original parent / child object is removed from the collection and it’s the copy that remains. So I then have to move them back into the original collection!

I’m sure all this makes sense eventually and there are good reasons for it working the way it does but from a UX point of view it’s super confusing