Weight paint mode and vertex paint mode share the same brushes #62225

Open
opened 2019-03-05 19:11:29 +01:00 by Julien Kaspar · 4 comments
Member

Blender Version
Broken: b8bb2bb960

Short description of error
Pretty much what the title says. When you adjust the settings of the Draw brush in the vertex paint mode the same changes apply to the weight paint mode. These are 2 separate modes with their own use cases and settings. They should not share their brushes.

**Blender Version** Broken: b8bb2bb960ac **Short description of error** Pretty much what the title says. When you adjust the settings of the Draw brush in the vertex paint mode the same changes apply to the weight paint mode. These are 2 separate modes with their own use cases and settings. They should not share their brushes.
Author
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

Why not simply use different brushes if you don't want to use the same one? You aren't forced to use the same brush.

If users have spent a real long time setting up some nice brushes, I can't see why we should not let them use these in the other modes?

Why not simply use different brushes if you don't want to use the same one? You aren't forced to use the same brush. If users have spent a real long time setting up some nice brushes, I can't see why we should not let them use these in the other modes?
Author
Member

@WilliamReynish
But ... most tools/brushes are not really compatible either in the settings or in how they are used. And these differences make sense.
You can't use textures or colors for weight painting since these are useless for that mode. You can't define options like weights, auto-normalize and multi-paint for vertex painting for the same reason. Some settings are not available for the brush in one mode or another which makes any brush setup in most cases useless and unnecessary to share between modes (especially vertex paint & weight paint).

From a user perspective, changing for example the spacing & jitter settings on a quick vertex paint and then having to change this again or create a new brush for a different mode that is used for different tasks is tedious.

You aren't forced to use the same brush.

That may be true but the user is recommended to do so by making it the default that the brushes are shared and set to be the same between modes.

If users have spent a real long time setting up some nice brushes, I can't see why we should not let them use these in the other modes?

While using Blender I would never think that using a brush from vertex paint for my weight painting would save me time, just like I wouldn't want to use a draw brush from weight paint in sculpt mode.
You also wouldn't want to share brushes between different tools within for example sculpt mode because most are incompatible for the same reasons.

In theory this feature kinda makes sense and maybe it can be useful in some way, like copying brush settings between vertex paint and texture paint mode.
Or sharing brushes between specific compatible tools in the same mode similar to how it works in Photoshop.
But Blender is not Photoshop and most tools are not compatible and sharing brushes by default is not useful and instead just tedious.

@WilliamReynish But ... most tools/brushes are not really compatible either in the settings or in how they are used. And these differences make sense. You can't use textures or colors for weight painting since these are useless for that mode. You can't define options like weights, auto-normalize and multi-paint for vertex painting for the same reason. Some settings are not available for the brush in one mode or another which makes any brush setup in most cases useless and unnecessary to share between modes (especially vertex paint & weight paint). From a user perspective, changing for example the spacing & jitter settings on a quick vertex paint and then having to change this again or create a new brush for a different mode that is used for different tasks is tedious. > You aren't forced to use the same brush. That may be true but the user is recommended to do so by making it the default that the brushes are shared and set to be the same between modes. > If users have spent a real long time setting up some nice brushes, I can't see why we should not let them use these in the other modes? While using Blender I would never think that using a brush from vertex paint for my weight painting would save me time, just like I wouldn't want to use a draw brush from weight paint in sculpt mode. You also wouldn't want to share brushes between different tools within for example sculpt mode because most are incompatible for the same reasons. In theory this feature kinda makes sense and maybe it can be useful in some way, like copying brush settings between vertex paint and texture paint mode. Or sharing brushes between specific compatible tools in the same mode similar to how it works in Photoshop. But Blender is not Photoshop and most tools are not compatible and sharing brushes by default is not useful and instead just tedious.
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
2 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#62225
No description provided.