Inconsistent Grease Pencil auto-keying behavior #93248
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93248
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: Linux 64-bit
Graphics card: GTX 1080
Blender Version
3.1 and prior
Short description of error
When auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe.
Also, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.
GP_autokey_bug.blend
Exact steps for others to reproduce the error
Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!
Added subscriber: @rocketman
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @lichtwerk
Can confirm, will check.
Added subscribers: @filedescriptor, @antoniov
Turns out this (canceling out of transform) is a bit hairy for greasepencil:
Opposed to other transform operations (which insert their auto-keyframes as part of
special_aftertrans_update__XXX
[and only do so if transform was not cancelled], greasepencil does this early on [and it probably needs to] as part ofcreateTransGPencil_curves
/createTransGPencil_strokes
.So we could introduce a
special_aftertrans_update__gpencil
and remove the frame again (but then again, dont think there is an easy way to figure out if the frame might have existed beforehand?)Have not looked into the auto-key for deleting, but since this might involve a rethinking of design, would prefer if @antoniov or @filedescriptor have a look...
Added subscriber: @capnm