Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
Hey!
So I think I understand what you mean based off the image and the explanation of it, and you are correct.
If you are working on something and then save out an object from that element or scene as a new creation because maybe you want to have it as an external element to work on, or for others to use that is then tied to the scene/element you were working in.
So if you then want to publish your collection that contains that new creation, it needs to publish that scene/element because they are now a part of the scene/element in your collection and for it to have the correct genealogy and the instance of that creation within it, it needs to be online too.
So it's not really a bug, as it allows you to keep references between your things your creating, while also maintaining the credit chain.
So it’s totally correct that you’re seeing these elements/scenes when you publish your collection, if you don’t want others to be able to see those creations then keep the private save selected on them.
The only thing I would be careful about is make sure it’s not then going to save a local save you might have of older assets over newer versions as if it’s saying all those things need publishing it’s because there’s a local save you have of them that isn’t saved online.
And if you then went in to edit your collection and selected update, it will only then show you the elements/scenes that are in your collection, not these ones that you just published :)
So your collection isn’t having items in it that it shouldn’t it’s just to keep the chain of references with them all :) If that all makes sense!
Thanks,
Catherine