Support for DarkRadiant layers about io_export_qmap HOT 3 CLOSED

DR layer information is stored externally in .darkradiant file and depends on the order of brushes & entities. So this can't be generalized for other editors and even if it could be, it could interfere with pasting from clipboard. I'm also already using collections for entity (bmodel) grouping in brush mode. Since in DR a brush can belong to multiple layers independently of its parent entity, Blender's view layers could be used instead of collections.

I don't think something this specific belongs in the main addon. Seems simple enough to implement, so I can make a separate unmaintained branch with the feature. Probably not until Sunday though. I'm fine with suggestions/reports, but I'll tell you right away that DR's xml clipboard is out of the question, unless someone comes by with a pull request.

from io_export_qmap.

Oh, I was thinking about organizing scene in Blender using collections and then when I export it to DR, each Collection with its meshes will become a layer. So when I load .map into DR, I won't have a mess.
Since .map can't be loaded back to Blender, I don't think it's relevant how each brush can be in every layer.

Blender's layers could be used, but aren't they are limited to only so many?

from io_export_qmap.

Added in 7e62fc7 as a branch

The terminology is a bit weird, what's now called "collections" used to be "layers" in pre-2.8 Blender. And what's now called "view layers" used to be "render layers" (I think). Both used to be limited in number, but not anymore. Anyway, like I said, I'm already using collections for grouping (such as grouping the house and chimney brushes into one entity in the video above).

from io_export_qmap.