Wireframe color per collection
Now that we finally have lovely wireframe colors, let's extend them by adding a color-per-collection option. For those of us familiar with Architectural design, this will be a further blessing.
Now that we finally have lovely wireframe colors, let's extend them by adding a color-per-collection option. For those of us familiar with Architectural design, this will be a further blessing.
11 Comments
Its already planned as part of overrides.
* @Pawel Piotrowski * cool, good to know!
How would you handle the situation where an object is in multiple collections?
* @Jason van Gumster * Jason, we have been telling this the whole time, the fact that you can have one object in multiple groups / collections makes more problems than it has advantages. Serious graphic apps recognized this long time ago and simplified the rules. This current 'flexible feature' will hamper a lot of possible future upgrades too.
One collection per object, simple yet powerful and believe or not, enables more flexibility down the road. Proven through my work, many times.
* @Jason van Gumster *
Instanced objects should adapt the color of the collection.
For example, from the workflow that I use daily with Rhino, each layer has a different color. Blocks (aka instanced objects) have the ability to either keep their own colors no matter which layer they are on, or they can be set up to to accept the layer's color in the viewport.
* @dimi.des * OK, so this only affects instances? I can get behind that.
* @Okavango * The ability to have objects in multiple collections/layers/groups is a critical component in my workflow (and that of many other users). Taking that away is a non-starter as far as I'm concerned.
* @ Okavango * I totally agree with that
I feel that using collections to structure the models (as a tree) is much more useful. You can then implements cascades features for properties, modifiers, ... This is currently not possible with objects in several collections.
* @Jason van Gumster * What do you think about mixing between multipile colors if an object is in multiple collectios?
* @ Okavango * Collections are good at least as sources for instancing. Also as small workspaces. Anyway you can use em only as layers. But even 2.79 layers and groups can contain same objects.
And you didn`t answer. What color is more important? Last added? First? First in the outliner stack?
* @dimi.des * with single instances all is clear. But any object can be connected to few collections. Collections are not objects and they do not have rule lilke «another collection = new instances». Collections have advantages of layers and groups + can be instanced.
For example I always have at least two collections: modeling and rendering. Modeling excluded from render, and contain only geometry. Rendering contain same geometry, instances of geometry, camera, ligths.
Idea is interesting for instances. They can have their own colors. But for collections we should decide, how priority of color will work.
Why we should just copy, if Blender can be Better?!
* @aryeramaty * Mixing colors might make sense for simple scenarios with 2 or maybe 3 collections involved, but I think it would quickly spiral out of control.