Regression. Inconsistency of visual color and values #83974
Labels
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#83974
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71
Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-12-19 19:49, hash:
0144b70948Worked: blender-2.92.0-4797c13e8f3a-windows64
{F9518794 size=full}
Value is about half visually, about half on the stripe, but Blender shows 0.208.
Expected/worked
Added subscriber: @Vyach
#102957 was marked as duplicate of this issue
#85995 was marked as duplicate of this issue
#85982 was marked as duplicate of this issue
#84400 was marked as duplicate of this issue
Inconsistency of visual color and valueto Regression. Inconsistency of visual color and valuesAdded subscriber: @rjg
HSV now uses scene linear values for the slider:
f193b1afb3Added subscriber: @brecht
Changed status from 'Needs Triage' to: 'Archived'
Not a bug, but an intentional change.
@brecht
Okay. As i understand, now visually half gray is 0.5 value.
Sorry for disturbing
@brecht
¿Is it possible to make gradient that way?
{F9519727 size=full}
in the middle of stripe is RGB Value 0.74 and 0.5 linear
No, all the number values displayed are scene linear by design now, not perceptually/visually linear.
I don't think that would be better, the color gradient widgets are intended to be perceptually linear as they are now.
@brecht
hm… I don`t see the point but I hope «the point is out there»
Isn`t it good to follow WYSWYG principle?
Not always, there are trade-offs.
@brecht okay. Thanks for replies!
Added subscribers: @senteria, @lichtwerk
I think loud about changes in HSV color picker... I remember when I used Blender with Vray addition and there was linear and non linear workflow (little nightmare for me like whole papers explained how to use all color spaces). Than I switch to pure Blender Cycles and I was so satisfied with intuitive HSV color picker. For every user intuitive is put for example V=0,5 and achieve middle gray (like in photoshop, inkscape, krita etc.). For me this disconnection is confusing. Can you share with some lecture how to manage this new behavior in daily work when someone used HSV picker in old way?
Can someone help me with my previous message (I'm keeping in mind that you are very busy)?
Sorry, but this is strictly a bug tracker, not user support.
Added subscribers: @piar7777, @filedescriptor
Added subscriber: @yousef.jv
Removed subscriber: @Vyach
Because I noticed that someone is confuse as me -> Maybe better way is to give choice to user?
Added subscriber: @MrDixioner
I would also like to choose myself how the color value coincides with its location on the gray scale. Therefore, I demand that such an opportunity appear in the settings.
Added subscribers: @Rays-Lv, @scurest, @mod_moder
{F13999455}{F13999502}
I don't think it's reasonable. It'd become much more confusing than before. All other CG apps use the previous method on their color picker, like Photoshop, 3ds max, etc.
Also, in practice, if I need to get exact 50% gray, then what value am I supposed to set?
Look, I understand what you meant, but if new method introduced inconvenience, users wouldn't want it. And it will mess up all workflow with colors. I think color value should be read by human, not machine. Users are artists, not color scientists. If you really like to keep this, I think you should offer two options for users to switch around.