Outline color for collection instances is different (dimming, also no indication for "Active") #81010

Closed
opened 2020-09-20 23:58:22 +02:00 by Russell · 19 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-20 17:34, hash: 0d5aa352d3
Worked: (newest version of Blender that worked as expected)

Short description of error
If the Outline overlay is selected then the color is either desaturated or semi-transparent for collection instances. I treat them like every other object in a scene and this change of color is very jarring. I can't find any setting that would control this. I understand that the empty is the real active object but since those are often hidden or turned off the outline color really should pass down to the instance itself. In fact it already does, but it's modified for some reason.

Screenshot (157).jpg

Exact steps for others to reproduce the error

  1. Enable Outline Selected in the Overlay dropdown.
  2. Create a collection containing at least one object.
  3. Add an instance of that collection to the scene
  4. Select the instance object and notice that the outline doesn't match the Object Selected and Active Object colors in the Theme settings.
**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-20 17:34, hash: `0d5aa352d3` Worked: (newest version of Blender that worked as expected) **Short description of error** If the Outline overlay is selected then the color is either desaturated or semi-transparent for collection instances. I treat them like every other object in a scene and this change of color is very jarring. I can't find any setting that would control this. I understand that the empty is the real active object but since those are often hidden or turned off the outline color really should pass down to the instance itself. In fact it already does, but it's modified for some reason. ![Screenshot (157).jpg](https://archive.blender.org/developer/F8904159/Screenshot__157_.jpg) **Exact steps for others to reproduce the error** 1. Enable Outline Selected in the Overlay dropdown. 2. Create a collection containing at least one object. 3. Add an instance of that collection to the scene 3. Select the instance object and notice that the outline doesn't match the **Object Selected** and **Active Object** colors in the Theme settings.
Author

Added subscriber: @Russ1642

Added subscriber: @Russ1642

#88134 was marked as duplicate of this issue

#88134 was marked as duplicate of this issue
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Philipp Oeser self-assigned this 2020-09-21 15:29:04 +02:00
Member

This is done on purpose, see https://developer.blender.org/diffusion/B/browse/master/source/blender/draw/intern/draw_common.c$104

So it blends the color for Object Selected with the background color.
In my opinion it makes sense, no? It serves the purpose of communicating that this is an instance that some actions cannot be done on (why would you think this is a bug?)

Will close for now (feel free though to comment again why this makes you feel like having found a bug...)

This is done on purpose, see https://developer.blender.org/diffusion/B/browse/master/source/blender/draw/intern/draw_common.c$104 So it blends the color for Object Selected with the background color. In my opinion it makes sense, no? It serves the purpose of communicating that this is an instance that some actions cannot be done on (why would you think this is a bug?) Will close for now (feel free though to comment again why this makes you feel like having found a bug...)
Author

I feel this is a bug because I want to see the object outline highlighted amongst a bunch of other objects. That's its purpose. Not to communicate something I already know, which is that I'm using collection instances. Knowing what objects are selected and which is the active seleected object is far more important than than being reminded yet again that my object is a lesser object citizen - the collection instance.

I feel this is a bug because I want to see the object outline highlighted amongst a bunch of other objects. That's its purpose. Not to communicate something I already know, which is that I'm using collection instances. Knowing what objects are selected and which is the active seleected object is far more important than than being reminded yet again that my object is a lesser object citizen - the collection instance.
Member

Ah, it is selected vs. active.
In its current state, you can only tell apart active vs. selected instances by looking at their origin point [which still draws differently], not by the outline, that is true.

In contrast to objects [which have a separation between colorActive and colorSelect], for instances there is only colorDupliSelect.

This would be a nice addition in fact (and could be added of course), I agree 100%, but this sounds more like a feature request?
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Ah, it is `selected` vs. `active`. In its current state, you can only tell apart active vs. selected instances by looking at their origin point [which still draws differently], not by the outline, that is true. In contrast to objects [which have a separation between `colorActive` and `colorSelect`], for instances there is only `colorDupliSelect`. This would be a nice addition in fact (and could be added of course), I agree 100%, but this sounds more like a feature request? For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Author

This is NOT a feature request. I only would like a feature that exists, outline highlighting, to work properly. I need to SEE the objects that I have selected. I have a scene filled almost entirely with collection instances. If you want to use outline highlighting for some other purpose such as communicating object type then do it through another colour in the themes panel, not by DIMMING the HIGHLIGHTING. I hope I haven't come across as rude

This is NOT a feature request. I only would like a feature that exists, outline highlighting, to work properly. I need to SEE the objects that I have selected. I have a scene filled almost entirely with collection instances. If you want to use outline highlighting for some other purpose such as communicating object type then do it through another colour in the themes panel, not by DIMMING the HIGHLIGHTING. I hope I haven't come across as rude
Member

Changed status from 'Archived' to: 'Needs Developer To Reproduce'

Changed status from 'Archived' to: 'Needs Developer To Reproduce'
Member

I hope I haven't come across as rude

I hear many things every day, so no worries :)

Not sure if the original decision was made to save some uniform in the globals block [but it looks like 2.79 already behaved the same].
I would still see this implemented as dimmed, but with the color for selected being dimmed and the color for active being dimmed (but making a distinction between active vs. selected).

I can only raise awareness to the appropriate module to make a decision then.
Dont get me wrong either, that link https://wiki.blender.org/wiki/Reference/Not_a_bug also explains why it is not possible to to implement every inconsistency we might come across.

> I hope I haven't come across as rude I hear many things every day, so no worries :) Not sure if the original decision was made to save some uniform in the globals block [but it looks like 2.79 already behaved the same]. I would still see this implemented as dimmed, but with the color for selected being dimmed and the color for active being dimmed (but making a distinction between active vs. selected). I can only raise awareness to the appropriate module to make a decision then. Dont get me wrong either, that link https://wiki.blender.org/wiki/Reference/Not_a_bug also explains why it is not possible to to implement every inconsistency we might come across.
Author

The collection instances only highlight with the dimmed 'active' colour, whether or not they're just selected or active. Also, please run this past someone who uses collection instances a lot. As I said I have scenes entirely filled with these objects and outline highlighting is nearly useless. I set the highlight colour to bright yellow and I can't see it most of the time because it blends right into the background. This is making it hard to work in my scene. I've even considered not using collection instances until this is fixed.

The collection instances only highlight with the dimmed 'active' colour, whether or not they're just selected or active. Also, please run this past someone who uses collection instances a lot. As I said I have scenes entirely filled with these objects and outline highlighting is nearly useless. I set the highlight colour to bright yellow and I can't see it most of the time because it blends right into the background. This is making it hard to work in my scene. I've even considered not using collection instances until this is fixed.
Author

Dont get me wrong either, that link https://wiki.blender.org/wiki/Reference/Not_a_bug also explains why it is not possible to to implement every inconsistency we might come across.

I wanted to address this specifically. The code for highlighting the entire object is already there, ready to go. Just remove the part where it's dimming the colour from the themes panel for no good reason. The purpose of outlining selected and active objects is to see what we have selected, not to identify object types. Dimming a highlight color goes against that in every way. So please bring up this point. It's an outline highlight to help us old farts see. I'd go so far as to call it an accessibility issue as well.

> Dont get me wrong either, that link https://wiki.blender.org/wiki/Reference/Not_a_bug also explains why it is not possible to to implement every inconsistency we might come across. I wanted to address this specifically. **The code for highlighting the entire object is already there**, ready to go. Just remove the part where it's dimming the colour from the themes panel for no good reason. The purpose of outlining selected and active objects is to see what we have selected, not to identify object types. Dimming a highlight color goes against that in every way. So please bring up this point. It's an outline highlight to help us old farts **see**. I'd go so far as to call it an accessibility issue as well.
Member

In #81010#1020422, @Russ1642 wrote:

Dont get me wrong either, that link https://wiki.blender.org/wiki/Reference/Not_a_bug also explains why it is not possible to to implement every inconsistency we might come across.

I wanted to address this specifically. The code for highlighting the entire object is already there, ready to go. Just remove the part where it's dimming the colour from the themes panel for no good reason. The purpose of outlining selected and active objects is to see what we have selected, not to identify object types. Dimming a highlight color goes against that in every way. So please bring up this point. It's an outline highlight to help us old farts see. I'd go so far as to call it an accessibility issue as well.

But there is specific code that separates instances from regular objects reg. outline color, so there is clearly an intention to differentiate these (and I do think this is helpful -- there is just some stuff for instances that makes them "less editable" which I think is communicated by this) That dimming could be made more subtle?
And of course, it would be good to have selected vs. active for instances, too.

> In #81010#1020422, @Russ1642 wrote: >> Dont get me wrong either, that link https://wiki.blender.org/wiki/Reference/Not_a_bug also explains why it is not possible to to implement every inconsistency we might come across. > > I wanted to address this specifically. **The code for highlighting the entire object is already there**, ready to go. Just remove the part where it's dimming the colour from the themes panel for no good reason. The purpose of outlining selected and active objects is to see what we have selected, not to identify object types. Dimming a highlight color goes against that in every way. So please bring up this point. It's an outline highlight to help us old farts **see**. I'd go so far as to call it an accessibility issue as well. But there is specific code that separates instances from regular objects reg. outline color, so there is clearly an intention to differentiate these (and I do think this is helpful -- there is just some stuff for instances that makes them "less editable" which I think is communicated by this) That dimming could be made more subtle? And of course, it would be good to have selected vs. active for instances, too.
Author

They're certainly less editable, but the outline color is there so I can see the objects to transform them and do stuff with them. Dimming a highlight colour negates the entire purpose of highlighting. When you have a scene with a hundred or more collection instances this is a big deal. I want the objects I've selected to be visible. That the code for dimming is already there is unfortunate but it's doing something completely counterproductive. Use it to put in another color. Make it a dashed outline. Just do something that makes it so I can still see what I've selected.

They're certainly less editable, but the outline color is there so I can see the objects to transform them and do stuff with them. Dimming a highlight colour negates the entire purpose of highlighting. When you have a scene with a hundred or more collection instances this is a big deal. I want the objects I've selected to be visible. That the code for dimming is already there is unfortunate but it's doing something completely counterproductive. Use it to put in another color. Make it a dashed outline. Just do something that makes it so I can still see what I've selected.
Philipp Oeser removed their assignment 2020-09-22 09:09:49 +02:00
Member

Added subscriber: @Imaginer

Added subscriber: @Imaginer
Philipp Oeser changed title from Outline color for collection instances is different to Outline color for collection instances is different (dimming, also no indication for "Active") 2021-05-10 14:43:06 +02:00
Member

Added subscribers: @Vyach, @finirpar

Added subscribers: @Vyach, @finirpar

This problem cannot be depicted with cubes - it appears on massive scenes with lots of collection instances.
It is important to detect active collection instance properly there (at least because it is possible to use the active one as transformation pivot so it is important to detect which one from selected is active).

This problem cannot be depicted with cubes - it appears on massive scenes with lots of collection instances. It is important to detect active collection instance properly there (at least because it is possible to use the active one as transformation pivot so it is important to detect which one from selected is active).

This issue was referenced by aa13c4b386

This issue was referenced by aa13c4b386b1311162e74378ad864a51b2f1b7af
Member

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Hans Goudey self-assigned this 2021-11-09 17:15:12 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#81010
No description provided.