Paint Mode: Brush Radius VS Brush Size #98676

Open
opened 2022-06-08 17:22:50 +02:00 by Juanfran Matheu · 11 comments

This is a brief task design to explain why Blender should switch brush radius to brush size and how this change will benefit artists.

I will start introducing the issues that texture paint mode have currently by using brush radius:

1. Makes impossible to paint single pixels.

  • As minimum brush radius is 1px (integer values), minimum brush size is 2px, so it's impossible to use current brushes to paint single pixels as for pixel art styles.

2. Spectrum of brush size values cut by half.

  • Current brush radius makes it impossible for artist to paint with an odd number brush size/diameter.
  • This likely cut the values by half as artists can't paint with a brush with sizes of 1, 3, 5, 7, 9, 11, and so on...
    That's a silly limitation for artists when we have an easy solution of moving to brush size/diameter.

3. Contra-intuitive.

  • Brush size/diameter gives artists better feedback on the real size of the brush over the texture space while they don't have to think in brush radius * 2.

Brush size is a standard over brush radius but not because it is driven by big companies but because it is the most intuitive for artists while radius may be more intuitive for mathematicians and programmers, so I think we should invest into improving UX for the end-user, specially in texture paint mode that lacks a lot of it.

This is a brief task design to explain **why Blender should switch brush radius to brush size** and how this change will benefit artists. I will start introducing the **issues that texture paint mode have currently by using brush radius:** **1. Makes impossible to paint single pixels.** - As minimum brush radius is 1px (integer values), **minimum brush size is 2px**, so it's **impossible** to use current brushes **to paint single pixels as for pixel art** styles. **2. Spectrum of brush size values cut by half.** - Current brush radius makes it **impossible** for artist **to paint with an odd number brush size**/diameter. - This likely **cut the values by half** as artists can't paint with a brush with sizes of 1, 3, 5, 7, 9, 11, and so on... That's a silly limitation for artists when we have an easy solution of moving to brush size/diameter. **3. Contra-intuitive.** - **Brush size**/diameter **gives artists better feedback on the real size of the brush** over the texture space while they don't have to think in brush radius * 2. Brush size is a standard over brush radius but not because it is driven by big companies but because it is the most intuitive for artists while radius may be more intuitive for mathematicians and programmers, so I think we should invest into improving UX for the end-user, specially in texture paint mode that lacks a lot of it.
Juanfran Matheu self-assigned this 2022-06-08 17:22:50 +02:00

Added subscribers: @jfmatheu, @JulienKaspar

Added subscribers: @jfmatheu, @JulienKaspar

Added subscriber: @iss

Added subscriber: @iss

Is this something that is agreed on along developers? If so then please confirm the task and add design / TODO subtype. I have almost closed this as feature request before checking author.

Is this something that is agreed on along developers? If so then please confirm the task and add design / TODO subtype. I have almost closed this as feature request before checking author.

Added subscriber: @AndyCuccaro

Added subscriber: @AndyCuccaro

Added subscriber: @Limarest

Added subscriber: @Limarest

I think it's a nice change. Only question I have is should we compensate for the changes in brush size with this patch by changing default settings? We did have a task to update those on the workboard

I think it's a nice change. Only question I have is should we compensate for the changes in brush size with this patch by changing default settings? We did have a task to update those on the workboard

Added subscriber: @AlexeyAdamitsky

Added subscriber: @AlexeyAdamitsky
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

To me this sounds reasonable. I agree that the brush defaults need to be adjusted to fit this change. But most users probably wouldn't even notice a difference, while pixel art can be better supported.

To me this sounds reasonable. I agree that the brush defaults need to be adjusted to fit this change. But most users probably wouldn't even notice a difference, while pixel art can be better supported.
Julien Kaspar added this to the Sculpt, Paint & Texture project 2023-02-08 10:20:48 +01:00
Philipp Oeser removed the
Interest
Sculpt, Paint & Texture
label 2023-02-10 09:11:18 +01:00

Was there ever a decision made on this vs. #98607? Or would both be able to coexist?

Was there ever a decision made on this vs. #98607? Or would both be able to coexist?

@recatek If this one is made (move from radius to diameter), it would be possible to have 1px brush size which is helpful for pixel art, BUT still would require an option to disable AA and an overlay to show some grid, for example based on ImageEditor view2d zoom level.
So the reality is that both can coexist. But if this one is done and what I've said before, we add a AA toggle and an automatic grid overlay, then we could potentially skip #98607, however #98607 has additional benefits that can't be ignored since is a new dedicated tool for pixel art, it has much more potential as the #98607 issue explains.

@recatek If this one is made (move from radius to diameter), it would be possible to have 1px brush size which is helpful for pixel art, BUT still would require an option to disable AA and an overlay to show some grid, for example based on ImageEditor view2d zoom level. So the reality is that both can coexist. But if this one is done and what I've said before, we add a AA toggle and an automatic grid overlay, then we could potentially skip #98607, however #98607 has additional benefits that can't be ignored since is a new dedicated tool for pixel art, it has much more potential as the #98607 issue explains.
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 Assignees
7 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#98676
No description provided.