Grease pencil weight paint select > color attribute does not work on materials that use a texture #107925

Closed
opened 2023-05-14 16:47:11 +02:00 by Jan-Willem van Dronkelaar · 7 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: (newest version of Blender that worked as expected)

Short description of error
In grease pencil in vertex paint mode, trying to select strokes with the same vertex color through "select > color attribute" does not work for strokes made with a brush that use a texture. That is despite these strokes being successfully colored by assigning them a vertex color.

Exact steps for others to reproduce the error

  1. Open the supplied blend file.
  2. Go into vertex paint mode for the GP object
  3. Set selection mask to stroke so you can select strokes
  4. Select one of the green strokes on the left (use lasso select)
  5. Go into the "Select" menu and choose "Color Attribute"
  6. In the redo panel change the Threshold from 0 to 1
  7. All green strokes will now be selected (this is the desired result)

Repeat these exact steps for a red stroke on the right. You will see that no additional red strokes will be selected.

Additional notes
I want to emphasize that the vertex colors have been correctly assigned. I don't know why I need to bump the threshold up to 1 for "select by color attribute" to work, that seems to be a bug in itself but is not the focus of this report.

You can verify that the red strokes have a vertex color assigned to them by going into the "Paint" menu and choosing "Reset vertex color". The stroke will turn black which is the color without any vertex color assigned. So the vertex color is there, assigned and coloring the stroke.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: (newest version of Blender that worked as expected) **Short description of error** In grease pencil in vertex paint mode, trying to select strokes with the same vertex color through "select > color attribute" does not work for strokes made with a brush that use a texture. That is despite these strokes being successfully colored by assigning them a vertex color. **Exact steps for others to reproduce the error** 1) Open the supplied blend file. 2) Go into vertex paint mode for the GP object 3) Set selection mask to stroke so you can select strokes 4) Select one of the green strokes on the left (use lasso select) 5) Go into the "Select" menu and choose "Color Attribute" 6) In the redo panel change the Threshold from 0 to 1 7) All green strokes will now be selected (this is the desired result) Repeat these exact steps for a red stroke on the right. You will see that no additional red strokes will be selected. Additional notes I want to emphasize that the vertex colors have been correctly assigned. I don't know why I need to bump the threshold up to 1 for "select by color attribute" to work, that seems to be a bug in itself but is not the focus of this report. You can verify that the red strokes have a vertex color assigned to them by going into the "Paint" menu and choosing "Reset vertex color". The stroke will turn black which is the color without any vertex color assigned. So the vertex color is there, assigned and coloring the stroke.
Jan-Willem van Dronkelaar added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-05-14 16:47:11 +02:00
Iliya Katushenock added the
Interest
Grease Pencil
label 2023-05-14 16:49:55 +02:00
Member

@jwvdronkelaar I could not reproduce the problem either with 3.5 or latest compiled 3.6, both green and red strokes can be selected by color attributes (although have to bump the threshold to 1).

I'll take a look at the code to see if the 1 is necessary.

@jwvdronkelaar I could not reproduce the problem either with 3.5 or latest compiled 3.6, both green and red strokes can be selected by color attributes (although have to bump the threshold to `1`). I'll take a look at the code to see if the `1` is necessary.

Turns out there has been a point release that I've missed. While I could not see where this was fixed exactly in the patch notes this does work properly in 3.5.1 now. I thought I was on the latest version when checking the website, only realized there was a point release when I scrolled down.

Sorry for wasting your time, this indeed works fine.

In regards to the threshold, it would be nice if this gets "fixed", thank you for looking into it. If it always fails at a value of 0 then why does that exist to begin with? All it does is that it guarantees the user is forced to do the extra step of manually bumping up the threshold to one for the tool to work, even with perfectly matching vertex colors.

Turns out there has been a point release that I've missed. While I could not see where this was fixed exactly in the patch notes this does work properly in 3.5.1 now. I thought I was on the latest version when checking the website, only realized there was a point release when I scrolled down. Sorry for wasting your time, this indeed works fine. In regards to the threshold, it would be nice if this gets "fixed", thank you for looking into it. If it always fails at a value of 0 then why does that exist to begin with? All it does is that it guarantees the user is forced to do the extra step of manually bumping up the threshold to one for the tool to work, even with perfectly matching vertex colors.
Member

@jwvdronkelaar thanks for testing again. I just tested 3.3 since it's LTS, doesn't seem to have any problem. So I guess let's just investigate the 1 issue, otherwise it's good.

@jwvdronkelaar thanks for testing again. I just tested 3.3 since it's LTS, doesn't seem to have any problem. So I guess let's just investigate the `1` issue, otherwise it's good.

So I guess let's just investigate the 1 issue, otherwise it's good.

Doesn't seem to be the problem reported.
Maybe it's worth editing or creating another report about this (if it really is a bug).

> So I guess let's just investigate the 1 issue, otherwise it's good. Doesn't seem to be the problem reported. Maybe it's worth editing or creating another report about this (if it really is a bug).
Germano Cavalcante added
Status
Needs Info from Developers
and removed
Status
Needs Triage
labels 2023-05-15 22:58:11 +02:00

@mano-wii As a user I'd be happy to turn this into a separate report if that is required or desired? From my perspective it is a bug, however it was not the focus of this report. If you'd like me to take this action let me know.

@mano-wii As a user I'd be happy to turn this into a separate report if that is required or desired? From my perspective it is a bug, however it was not the focus of this report. If you'd like me to take this action let me know.

@jwvdronkelaar, as I see it, this isn't really a bug. Therefore, the report would be a feature request.

@jwvdronkelaar, as I see it, this isn't really a bug. Therefore, the report would be a feature request.
Member

@mano-wii Will close the report since this is more of a feature request.

@mano-wii Will close the report since this is more of a feature request.
Blender Bot added
Status
Archived
and removed
Status
Needs Info from Developers
labels 2023-07-05 06:31:43 +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#107925
No description provided.