color picker broken #49090
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#49090
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
Win7 GTX 550ti
Blender Version
Broken: 2.77a and recent builds
the color picker widget shows a 'posterized' ramp / palette... this has happened from time to time, it works fine after I close and restart blender
guess it has to do with my system and drivers but thought of reporting anyway
http://www.pasteall.org/pic/105975
http://www.pasteall.org/pic/105976
http://www.pasteall.org/pic/105977
not easy to reproduce
Changed status to: 'Open'
Added subscriber: @lowercase
Added subscriber: @Sergey
Make sure you've got all updates and latest drivers installed.
If that doesn't help, we really have to know exact steps reproducing the issue, otherwise we can't troubleshoot the issue.
It might help if you'll try reproducing the issue on another computer you've got access to.
Added subscriber: @ThomasRadeke
Hey!
I'm experiencing this, too, but I was reliably able to reproduce it.
For me, it happens when I switch viewport rendering to "Material", then to "Rendered", then open up the color picker. Sometimes it will not happen right away, but changing perspective in the 3D view, then opening the color picker again will always result in the bug.
When first setting the viewport mode to "Solid", then to "Rendered", it does not happen.
I made a video to show the effect in action:
https://www.youtube.com/watch?v=WN7DTvlKuaI
I'm on Linux Mint 17.3 MATE (not using compositing), nVidia GTX1070 with proprietary drivers v367.27.
It happens on both builds 2.77.3-bac1279 and 2.77.3-f92a6b8.
Added subscribers: @GregZaal, @brecht
Likely it's an issue where the OpenGL state gets set to
glShadeModel(GL_FLAT)
, while the Blender drawing code assumes it'sglShadeModel(GL_SMOOTH)
, it should always be restored to the latter.I can't spot any place in the Blender drawing code with this issue, and I couldn't reproduce the problem with a default Blender configuration. The Node Wrangler and Cursor control addons do not properly set the state back to
GL_SMOOTH
though, are you using one of those by any chance?If I enable the Node Wrangler addon, I get the same artifacts in the color picker after using the Lazy Connect operator. @GregZaal, that should be easy to fix by removing both calls to
bgl.glShadeModel()
, they are unnecessary.yes, I have the Node Wrangler enabled by default... couldn't reproduce using Thomas instructions, it does show up with Lazy Connect -but I rarely use this exact operator anyway- have Animation Nodes enabled also
This issue was referenced by
f65ecafa4a
Changed status from 'Open' to: 'Resolved'
This issue was referenced by blender/blender@cf53389425
I checked the code again and found an issue with subsurf drawing in material draw mode, as in the video by @ThomasR. So with these two cases fixed, hopefully the bug is gone entirely.