We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

BUG REPORT: collections within collections dissapear

Home Forums Graphics / Blender BUG REPORT: collections within collections dissapear

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #42150

    I noticed some time ago, that nested collections cause issues in Verge3D blender files. I have seen almost the entire outliner “disappear” after I save a file with collections nested inside other collections. I don’t feel like this behavior is the way it should be. I was under the impression that collections were not that restricted in how they could be structured . . .


    I should also say, that I do not experience this same behavior in blender files which are not being used as a Verge3D project or application.


    I found this bug report on developer.blender.org:


    It seems to be related, but in releases before 2.93, I only noticed this behavior once I started working and test a scene/file in Verge3D.

    • This reply was modified 1 month, 2 weeks ago by mcolinp. Reason: wrong link posted initially

    What’s your purpose in nesting them?
    For parenting purposes?
    Adds groups to objects.
    In that if an object belongs to a certain group (collection) then it will be listed in the object’s groupNames property.

    I would suggest NOT nesting them.
    And if you’re trying to parent objects, do just that.

    …if I’m understanding correctly.


    It provides a much better way of managing large assemblies. So if I make something like a bicycle, I would have a frame with components. So lets say the brakes, have many individual components such as cables, caliper, disc, lever etc. I want to be able to manage/link or import collections at different levels. I might also have several options within the upper collection containers. A good example of this was a watch I designed, which had multiple options for Hands, Markers/Numbers, and Bezels. So I have a Top Container that is Called “Bezel”, and then inside I have several distinctly unique bezels, but only one is present in any configuration. So I turn off (untick) the collections not in use for the given configuration. I also can tick on a different set of components using multiple “scenes” in blender.

    I have been a little unsure how to best structure files for use in Verge3D. Up till recently, I painstakingly structured files with collections, and made liked proxies of each individual mesh object. It made it so all the materials can be applied in the main file to the proxy objects.

    In my most recent file, I decided to use linked collections instead of linking individual proxy objects. The trade off, is that I have to apply materials in the linked files, as you cannot apply materials to collections. So I link all the files to the same material blend file, to ensure materials are not accidentally duplicated.

    With blender, there is so much flexibility, that it can be difficult to grasp the best file structure workflow pipeline; especially with specific parameters needed for Verge3D output.


    Make sure you do not have your camera icon un-ticked for certain elements,or they will not export with the verge gltf exporter. :good:

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.