Stroke overlay when erasing #66479

Open
opened 2019-07-05 19:14:44 +02:00 by xanadou · 18 comments

System Information
Operating system: Win 10
Graphics card: NVIDIA GeForce GTX 1070 Ti

Blender Version
Broken: (example: 2.80, 66684bdff3, master, 2019-07-05)

Short description of error

The new alpha overlap stops working, when you erase somethin of that stroke.

Exact steps for others to reproduce the error

Open a new project create a blank stroke object draw something try to erase it

**System Information** Operating system: Win 10 Graphics card: NVIDIA GeForce GTX 1070 Ti **Blender Version** Broken: (example: 2.80, 66684bdff30f, master, 2019-07-05) **Short description of error** The new alpha overlap stops working, when you erase somethin of that stroke. **Exact steps for others to reproduce the error** Open a new project create a blank stroke object draw something try to erase it
Author

Added subscriber: @xanadou

Added subscriber: @xanadou

Added subscriber: @Lattapotta

Added subscriber: @Lattapotta

image.png
Yea, this is what happens when I test it.

![image.png](https://archive.blender.org/developer/F7577332/image.png) Yea, this is what happens when I test it.

Added subscribers: @antoniov, @ZedDB

Added subscribers: @antoniov, @ZedDB
Antonio Vazquez was assigned by Sebastian Parborg 2019-07-09 18:00:11 +02:00

@antoniov is this something fixable?

@antoniov is this something fixable?

Not now.... because there are more implications.... hide points needs more things that a simple change and hide strokes need to change in the draw manager also and maybe in a lot of places, so it's something cannot be changed easily..it's possible, but need a redesign of several areas.

Not now.... because there are more implications.... hide points needs more things that a simple change and hide strokes need to change in the draw manager also and maybe in a lot of places, so it's something cannot be changed easily..it's possible, but need a redesign of several areas.
Antonio Vazquez was unassigned by Dalai Felinto 2019-12-23 16:33:55 +01:00

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

I have re-triaged this report and can not reproduce it.
Can you please check if this is still an issue in latest build?
https://builder.blender.org/download/

I have re-triaged this report and can not reproduce it. Can you please check if this is still an issue in latest build? https://builder.blender.org/download/
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'
Member

I can still reproduce:

before Eraser:
image.png
after Eraser:
image.png

@antoniov: is this something that also goes away in the greasepencil-refactor branch?
(confirming for now, since it is still an issue in master...)

I can still reproduce: before Eraser: ![image.png](https://archive.blender.org/developer/F8323521/image.png) after Eraser: ![image.png](https://archive.blender.org/developer/F8323523/image.png) @antoniov: is this something that also goes away in the greasepencil-refactor branch? (confirming for now, since it is still an issue in master...)

Added subscribers: @fclem, @mendio, @pepe-school-land

Added subscribers: @fclem, @mendio, @pepe-school-land

I have tested and this is something we cannot fix, because is not a "real" error. We could change how works the eraser, but it's something we need to think before the pros and cons.

The reason for the change is how the strokes are overlapped by stencil. When you start to draw, you draw only one stroke, so the stencil is applied (always works by stoke), so any overlapping is removed.

image.png

When you start to erase, first the strength of the stroke is reduced, but when you get a threshold, the point is removed and the stroke is cut in pieces, In this moment, you have more than one stroke and the effect is as if you had several strokes one on top of others. As the opacity is not 1.0, you get the overlapping effect, and this is normal.

image.png

To fix this, we would have to add an option in the eraser to keep the "invisible" points, but then the eraser could never remove points and will produce "invisible strokes", so if we fix this, we break other areas.

@mendio @pepe-school-land @fclem Any idea here?

I have tested and this is something we cannot fix, because is not a "real" error. We could change how works the eraser, but it's something we need to think before the pros and cons. The reason for the change is how the strokes are overlapped by stencil. When you start to draw, you draw only one stroke, so the stencil is applied (always works by stoke), so any overlapping is removed. ![image.png](https://archive.blender.org/developer/F8323569/image.png) When you start to erase, first the strength of the stroke is reduced, but when you get a threshold, the point is removed and the stroke is cut in pieces, In this moment, you have more than one stroke and the effect is as if you had several strokes one on top of others. As the opacity is not 1.0, you get the overlapping effect, and this is normal. ![image.png](https://archive.blender.org/developer/F8323571/image.png) To fix this, we would have to add an option in the eraser to keep the "invisible" points, but then the eraser could never remove points and will produce "invisible strokes", so if we fix this, we break other areas. @mendio @pepe-school-land @fclem Any idea here?

@lichtwerk As this report is something that cannot be fixed without breaking other things... is it good to keep as know issue or just close it?

@lichtwerk As this report is something that cannot be fixed without breaking other things... is it good to keep as know issue or just close it?
Member

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Member

A Known Issue can be closed if this is a Architecture/Design limitation that wont be fixed.
https://code.blender.org/wp-content/uploads/2019/12/flow-chart-ish-6-months.png

However, if this is something that might be worked on [just not in the forseeable future of lets say two releases], than I guess it should stay open?

Tbh, I would like the opinion of @dfelinto here (since it was never 100% clear to me as well)

A Known Issue can be closed if this is a Architecture/Design limitation that wont be fixed. https://code.blender.org/wp-content/uploads/2019/12/flow-chart-ish-6-months.png However, if this is something that might be worked on [just not in the forseeable future of lets say two releases], than I guess it should stay open? Tbh, I would like the opinion of @dfelinto here (since it was never 100% clear to me as well)

As this is a design limitation, we are going to add an explanation of the limitation in the manual.

@mendio when you can , please add a cooment in the manual. Contact with me if you need a detailed explanation of the problem and why cannot be fixed with the current design without breaking more things.

As this is a design limitation, we are going to add an explanation of the limitation in the manual. @mendio when you can , please add a cooment in the manual. Contact with me if you need a detailed explanation of the problem and why cannot be fixed with the current design without breaking more things.
Philipp Oeser removed the
Interest
Grease Pencil
label 2023-02-09 15:19:59 +01: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
6 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#66479
No description provided.