Transform gizmos having low opacity behind meshes. #74905

Closed
opened 2020-03-19 02:44:24 +01:00 by Zino Guerr · 15 comments

System Information
Operating system: Windows-10-10.0.14393-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59

Blender Version
Broken: version: 2.83 (sub 10), branch: master, commit date: 2020-03-19 01:09, hash: b62e1146e1
Worked: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7

Short description of error
If the transform gizmos have meshes behind them they get dimmed for some reason.
G.jpg

Exact steps for others to reproduce the error

  • Reset to factory settings.
  • Open the test file or with the default scene, zoom in until the gizmos encompass the cube.
  • notice that the opacity is very low before hovering over the gizmos.
    G.blend
**System Information** Operating system: Windows-10-10.0.14393-SP0 64 Bits Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59 **Blender Version** Broken: version: 2.83 (sub 10), branch: master, commit date: 2020-03-19 01:09, hash: `b62e1146e1` Worked: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7 **Short description of error** If the transform gizmos have meshes behind them they get dimmed for some reason. ![G.jpg](https://archive.blender.org/developer/F8414887/G.jpg) **Exact steps for others to reproduce the error** * Reset to factory settings. * Open the test file or with the default scene, zoom in until the gizmos encompass the cube. * notice that the opacity is very low before hovering over the gizmos. [G.blend](https://archive.blender.org/developer/F8414894/G.blend)
Author

Added subscriber: @Znio.G

Added subscriber: @Znio.G
Zino Guerr changed title from 3 to Transform gizmos having low opacity behind mehes. 2020-03-19 02:49:25 +01:00
Zino Guerr changed title from Transform gizmos having low opacity behind mehes. to Transform gizmos having low opacity behind meshes. 2020-03-19 02:49:57 +01:00
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

will bisect if the said working build shows thicker lines

will bisect if the said working build shows thicker lines
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Added subscriber: @fclem

Added subscriber: @fclem
Member

804e90b42d is the first bad commit
cc @fclem

804e90b42d is the first bad commit cc @fclem

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

This is not a bug AFAIK. The code explicitly sets the opacity to factor 0.6 and then to 1.0 on rollover.

IMO, I do find this to be too much - the gizmos become too unclear in many cases. However, it doesn't appear to be a bug.

This is not a bug AFAIK. The code explicitly sets the opacity to factor 0.6 and then to 1.0 on rollover. IMO, I do find this to be too much - the gizmos become too unclear in many cases. However, it doesn't appear to be a bug.

If we use 0.8 instead of 0.6, it looks clearer:

0.6:
Screenshot 2020-03-19 at 14.46.46.png

0.8:
Screenshot 2020-03-19 at 14.46.50.png

patch:

patch.diff

If we use 0.8 instead of 0.6, it looks clearer: 0.6: ![Screenshot 2020-03-19 at 14.46.46.png](https://archive.blender.org/developer/F8415816/Screenshot_2020-03-19_at_14.46.46.png) 0.8: ![Screenshot 2020-03-19 at 14.46.50.png](https://archive.blender.org/developer/F8415818/Screenshot_2020-03-19_at_14.46.50.png) patch: [patch.diff](https://archive.blender.org/developer/F8415821/patch.diff)
Member

William, it got a bit worse without explicitly changing those two lines in the said commit. So a regression ?

William, it got a bit worse without explicitly changing those two lines in the said commit. So a regression ?

Added subscriber: @ideasman42

Added subscriber: @ideasman42

@ankitm or maybe it just makes the value more correctly reflect the result? Not sure, but 0.6 is almost only 50% opacity.

I even tested with 1.0, which is the clearest, and there is still highlighting on top:

Screenshot 2020-03-19 at 14.53.25.png

I am not even sure why we explicitly dim the gizmos so much in the code. It seems to serve no obvious purpose. @ideasman42 Do you know why we set the gizmo opacity to be so low?

@ankitm or maybe it just makes the value more correctly reflect the result? Not sure, but 0.6 is almost only 50% opacity. I even tested with 1.0, which is the clearest, and there is still highlighting on top: ![Screenshot 2020-03-19 at 14.53.25.png](https://archive.blender.org/developer/F8415824/Screenshot_2020-03-19_at_14.53.25.png) I am not even sure why we explicitly dim the gizmos so much in the code. It seems to serve no obvious purpose. @ideasman42 Do you know why we set the gizmo opacity to be so low?
Author

In #74905#894487, @WilliamReynish wrote:
This is not a bug AFAIK. The code explicitly sets the opacity to factor 0.6 and then to 1.0 on rollover.

IMO, I do find this to be too much - the gizmos become too unclear in many cases. However, it doesn't appear to be a bug.

I tried with the previous versions of Blender that i got 2.81 and 2.82 to check and it's only in 2.83 that the opacity is low with this case, they should be the benchmark since they feel correct &maybe it's what @ankitm have said, it's the new changes to the color management affecting parts where it's not supposed to.

> In #74905#894487, @WilliamReynish wrote: > This is not a bug AFAIK. The code explicitly sets the opacity to factor 0.6 and then to 1.0 on rollover. > > IMO, I do find this to be too much - the gizmos become too unclear in many cases. However, it doesn't appear to be a bug. I tried with the previous versions of Blender that i got 2.81 and 2.82 to check and it's only in 2.83 that the opacity is low with this case, they should be the benchmark since they feel correct &maybe it's what @ankitm have said, it's the new changes to the color management affecting parts where it's not supposed to.
Author

This can be closed i think.
It seems to be fixed on the latest version at least for my setup, so thank you.

This can be closed i think. It seems to be fixed on the latest version at least for my setup, so thank you.
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Ankit Meel self-assigned this 2020-04-19 08:09:07 +02: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
3 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#74905
No description provided.