GPencil: Strokes cannot be erased, sculpted or painted #76950
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#76950
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.23 355.11.10.50.10.103
Blender Version
Broken: version: 2.90 (sub 2), branch: master, commit date: 2020-05-18 23:33, hash:
7bd07c9f5a
Worked: (newest version of Blender that worked as expected)
Short description of error
At some point during the drawing process in a GP object, the eraser can't erase the lines anymore. All layers and colors are unlocked and there is only one keyframe.
But after switching to edit mode and moving some points manually, these points are erasable again.
Exact steps for others to reproduce the error
Added subscriber: @Dedouze
Added subscriber: @ronsn
@Dedouze Can you reattach your .blend file? It seems to be broken in the wysiwyg editor.
greasepencil eraser bug.blend
Ah yeah. Good luck !
Changed status from 'Needs Triage' to: 'Confirmed'
@Dedouze Do you remember what you were doing when the problem started?
Greasepencil strokes not erasable until moved in edit modeto GPencil: Strokes cannot be erased, sculpted or paintedThe problem is related to the internal stroke bounding box used to determine if the brush collides with the stroke. As the bounding box is outdated, the brush cannot determine if the brush collides with stroke and any brush related operation does not work.
As a quick fix, just enter in Edit mode, select all, move the strokes and cancel and return to Draw mode. This operation will update the bounding box.
The point here is try to find what operation produced the outdate of the bounding box.
@Dedouze Could you try to reproduce the problem and determine the steps? Fix the issue is very simple if we know where.
@Dedouze Did you find a way to reproduce it? have you found again the bug?
@Dedouze And: I remember you did a live stream some time ago, but I didn't watch it. Maybe you did some more and maybe the issue occurred in one of the streams? Then we could watch it and see what causes the issue.
I think i reproduced it once by using the symmetry modifier to create a drawing and then clock on apply for the modifier, but i couldn’t reproduce it another time, so maybe there is something else. I have some live recordings also but i don’t remember the occurence on the bug on it. Let me check again today, i will tell you if i find a recording.
Thanks for your help!
Closed as duplicate of #79651