Python - in an operator, setting scene frame after undo causes playback cursor to get 'stuck' #55807
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#55807
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
Windows 8.1
Blender Version
Broken: 2.79b
Short description of error
Ok, this is kinda hard to describe, so here goes -
If a scene's sync mode is "AV-sync",
If an operator is called from a panel,
The operator runs an undo operation (bpy.ops.ed.undo()),
Then setting bpy.context.scene.frame_current will cause the playback cursor to get stuck rapidly iterating between 2 frames.
This seems to only happen if it is done in an operator, and only if the operator is called from a panel or shortcut (not just directly in the script run), and only if the av-sync is set
Exact steps for others to reproduce the error
Set a new scene's sync mode to "AV-sync"
Load the following script into a text area
Run the script
Click the new "Test" button in the "Test Panel" panel in the 3d view properties panel.
Added subscriber: @snuq
As a side note, I have seen this happen before from some other cause, but it was one of those unreproducable 'what the heck just happened??' moments...
So, it is entirely possible that other combinations of commands may cause this, but Blender was most definitely set to av-sync mode in that situation.
Added subscriber: @mont29
Changed status from 'Open' to: 'Resolved'
Fwiw, on 2.8 it seems to work OK, so will consider that issue as fixed. Thanks for the report!