Page MenuHome

Color picker samples merged (display output) colors on a certain object regardless of "Sample Merged" setting
Needs Information from Developers, NormalPublic


System Information
Operating system: Windows 10 v1909
Graphics card: NVIDIA GeForce GTX 1660 super

Blender Version
The bug occured on the latest Steam release of Blender (2.90.1). I also tried to open the project file with the said bug in 2.83 LTS steam beta branch but it happened there too.

Short description of error
When trying to texture paint a certain project it ignores the "Sample Merged" setting and always picks the display output color, while other objects don't share this problem.
It happens regardless of the material or texture I'm editing, it seems to be tied to a single object. For example, If I create a cube and assign the material which the bugged object uses color picking works fine with it, and if I assign any other material to the bugged object it still samples display output color regardless of the settings.

Exact steps for others to reproduce the error
I'm sadly not sure how to reproduce it. Though I appended the bugged object to a fresh file:

It's system info:

I separated it so you wouldn't have to dig through the mess that is my main project file :D. It retained it's weird inabillity to pick colors though.

I couldn't find a solution to this when I tried to google for it, so my only assumption left here is it being a bug. I'm sorry in advance if something I said isn't clear. If needed, I can provide a whole project or try and provide more specific information if what I wrote here isn't enough as soon as possible.

Event Timeline

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Nov 2 2020, 1:14 PM

Can confirm there is something weird with that object, but I havent been able to reproduce this issue.

You can "fix" it by enabling/disabling Paint Mask once. Color Picker then samples "unmerged" again.

Maybe this rings a bell on your side? Do you have an idea how to reproduce?

No, unfortunately not. Constantly switching between modes and enabling\disabling things is a big part of my "workflow" (more like an annoying habit honestly), so it's hard for me to keep track of that, sorry. I tried to reproduce it and had no luck too.
Many thanks for the workaround though

Pretty sure T81775: Crash on Exiting Texture Paint With Multiresolution (Image Editor involved) / rB1ceb91d1b394: Fix T81167: Texture Painting with Paint mask enabled, (de)selecting faces… are related.

But since we dont have a way to reproduce this, I think there is not much we can do.
Would assume that once T81775: Crash on Exiting Texture Paint With Multiresolution (Image Editor involved) is resolved, this report should also be no problem anymore.
Will merge these reports now, if you ever find a reliable way to reproduce, please leave a comment in T81775.

@Philipp Oeser (lichtwerk) T81775 seems to be a 2.91 only issue. People aren't able to reproduce the crash, and the cause of the disappearing object has been found in 2.91 where the draw command isn't send to the GPU. Not sure if this is related.

Philipp Oeser (lichtwerk) reopened this task as Needs Information from Developers.Nov 2 2020, 6:26 PM

@Philipp Oeser (lichtwerk) T81775 seems to be a 2.91 only issue.

Not sure what you mean. As in not in 2.92? Not in 2.90.1? It was reported for 2.90.1 and is present in 2.92 as well (you can easily reproduce it with the file from this report as well in master).
But of course, this could be different.