I’ve just watched this:
Interesting discussion about the ability to connect domains within a domain.
I think this is the way to go for many good reasons.
This could allow large worlds. It’s a good solution to allow many people to build in a same world with a lot of freedom, allowing people to exist between the linked domains, walking and taking in the parent domain.
This could give to HF a serious advantage over the other platforms that might not be able to follow us on that move.
But this won’t solve the problem that we have a limit on what we can render about the number of polygons. (and I won’t talk about the download time which is not really a technical limit but a limit in “human patience”.)
This limit will still be there even with those nested domains. That’s why I think we would need “visibility zones” before “hierarchic domains”.
I think we need to be able to have entities configurable to be “visible” or “not visible” from outside a specific zone.
This would allow seeing some structures from far away without having to load the secondary objects that are inside of it.
Considering that the sum of all the small objects of a living room can be as rich in polygons and textures than a whole island’s landscape, there is a serious benefit to not render those objects when you are outside of the house.
This kind of optimization could make a huge difference. I think this is needed for the single domain use case. (and certainly even more needed for the hierarchical domain use case.)