Keyframes from the old file are not working correctly unless new keyframe is added #140
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/test#140
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Original bug report: https://projects.blender.org/blender/blender/issues/157234
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.57 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked:
Short description of error
Keyframes from the old file are not working correctly unless new keyframe is added. Can't test 5.2 alpha or 5.1.1 rc due to network issues
Exact steps for others to reproduce the error
Report is clear
LLM Reasoning
Got it, let's see. The bug report has a clear title, a short description of the error, and exact steps to reproduce. The steps are numbered and explain what to do. Even though there's system info, we ignore that. The description is concise and tells what the problem is: old keyframes don't work unless new ones are added. So the clarity is good. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 6.21941
}
Report is specific
LLM Reasoning
Got it, let's analyze this bug report. The title is "Keyframes from the old file are not working correctly unless new keyframe is added". The body describes a specific scenario: opening an attached file, noticing F-curve issues, then adding a new keyframe fixes it. So it's about a specific issue with keyframes in an old file that requires a new keyframe to work. That's a specific problem because it's tied to a particular action (adding a new keyframe) and a specific context (old file's keyframes). So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 7.820939999999999
}
Report flagged as NOT a duplicate by LLM
Blender 5 Keyframe Problem in Grease Pencil
https://projects.blender.org/blender/blender/issues/140576
System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 576.02 Opengl Backend
Blender Version
Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-06-10 23:34, hash:
c463860a828bWorked: (newest version of Blender that worked as expected)
Short description of error
When I created a new Grease Pencil layer, keyframes automatically appeared in previous blender versions, but in blender 5 keyframes are not showing up.
Exact steps for others to reproduce the error
I created a new file in 2D animation, added new layer to work on, now, I cant see any keyframes in the timeline but if I just go ahead and change it's position the animation works, but there are no keyframes visible.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1 is about keyframes from an old file not working unless a new one is added. The steps involve opening a file where F-curve doesn't follow keyframes, then adding a new keyframe fixes it.
Bug report 2 is about Grease Pencil in Blender 5: when creating a new layer, keyframes don't show up (but animation works if you change position). Steps are creating a new file, adding a layer, no visible keyframes but animation works after changing position.
The issues seem different. Report 1 is about existing keyframes from an old file not working, needing a new keyframe to fix. Report 2 is about new Grease Pencil layers in Blender 5 not showing keyframes (but animation still works when modified). The contexts are different: one is old file keyframes, the other is new layer keyframes in Grease Pencil. So they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 14.277334000000002,
"duplicate_report_number": "140576"
}
Report flagged as NOT a duplicate by LLM
this file's keyframe values don't update in the property editors, but display correctly in the viewport
https://projects.blender.org/blender/blender/issues/156105
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 591.44 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash:
a37564c4df7aShort description of error
Something strange is going on with the readout of keyframe values, although the viewport updates correctly both the transform properties and graph editor are wrong. Reverting the file temporarily makes the values display correctly, and closing the viewed sequence or removing and purging the compositing network seems to stop the error occurring. See video
Exact steps for others to reproduce the error
any ideas? the file may be in quite an unusual state, it's from a large complex project which has had multiple scripts run on it, plus at one point the current frame of the scene with the sequencer was used as a driver, I think that should have been removed now though.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug Report 1: The issue is keyframes from an old file not working correctly unless a new keyframe is added. Steps involve opening a file, noticing F-curve in Graph Editor doesn't follow keyframes, then adding a new keyframe fixes it.
Bug Report 2: Keyframe values don't update in property editors but display correctly in viewport. Steps include observing location values in graph editor/properties, advancing and rewinding frames changes the keyframed status/value, reverting fixes temporarily, and certain actions (clearing sequence, compositing network) stop it.
The core issues seem different: Report 1 is about old keyframes not working until a new one is added. Report 2 is about values not updating correctly in editors vs viewport, with specific steps involving frame changes and reverting. The symptoms are distinct—Report 1's fix is adding a new keyframe, Report 2's involves reverting or clearing sequences. So they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 15.511598,
"duplicate_report_number": "156105"
}
Report flagged as NOT a duplicate by LLM
Grease Pencil: New keyframes are not automatically selected
https://projects.blender.org/blender/blender/issues/148937
System Information
Operating system: Linux MInt
Graphics card: N/A
Blender Version
Broken: 5.1 alpha - 3.0
Worked: never
Short description of error
When creating new keyframes for Grease Pencil the new keyframes are not selected.
This is inconsistent with normal animation where the latest inserted key is always selected.
Note: Split off from #138877: insert keyframe behavior not consistent between all animation editors
This may work as intended since GP has different workflow requirements, in that case it would either be a ToDo or closed
Exact steps for others to reproduce the error
Create a grease pencil object
ensure auto-keying is enabled
Go into draw mode
draw a line, go to a different frame, draw another line
Notice none of the new keys are selected
Compare that to object animation
On the default cube press
Ito create keyframesgo to a different frame and press
Inotice only the last inserted key is selected
Related for VFX masks: #148938: VFX: Mask keyframes are not automatically selected
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about keyframes from an old file not working correctly unless a new keyframe is added. The steps involve opening a file, noticing F-curve issues, then adding a new keyframe to fix it.
Bug report 2 is about Grease Pencil new keyframes not being automatically selected, comparing to object animation where the latest key is selected. Steps are creating a grease pencil object, drawing lines on different frames, and checking selection.
The core issues are different: one is about old file keyframes not working (needing a new keyframe to fix), the other is about Grease Pencil keyframe selection behavior. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.195986000000001,
"duplicate_report_number": "148937"
}
Report flagged as NOT a duplicate by LLM
GP Gradient Tool Will not automatically create new keyframes
https://projects.blender.org/blender/blender/issues/153061
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.57 Opengl Backend
Blender Version
Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash:
a37564c4df7aWorked: (newest version of Blender that worked as expected)
Short description of error
Using GP Gradient Tool in editing mode will not automatically create new keyframes
Exact steps for others to reproduce the error
1.Creat GP
2.Open Auto Keying
3.In GP editing mode,Use Gradient Tool
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about keyframes from an old file not working unless a new one is added. The steps involve opening a file and adding a new keyframe to fix the curve.
Bug report 2 is about the GP Gradient Tool not automatically creating new keyframes when used in editing mode, with steps involving creating a GP, enabling auto-keying, and using the gradient tool.
The issues are different: one is about existing keyframes from an old file not working (needing a new keyframe to fix), the other is about the gradient tool not creating keyframes automatically. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 10.966636999999999,
"duplicate_report_number": "153061"
}
Report flagged as NOT a duplicate by LLM
Baking Overwrite action, adding keyframes without removing the old ones (double keyframe, at the same frame)
https://projects.blender.org/blender/blender/issues/109079
System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.36
Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash:
e1ccd9d4a1d3Worked: 3.4
Short description of error
Baking doesn't remove old keyframes, when using Overwrite current action. the result is curves with two values at the same frame.
Keyframes are also changing to Linear interpolation for no reason. This was working fine in 3.4
Exact steps for others to reproduce the error
open the attached file.
Select the object named 'Armature'
Bake the action of the Armature. Use the settings: Overwrite action and visual keying.
After the bake select the bones and check them in the graph editor, in the top bones such 'Bone.003' you can see the result better.
Now try it on 3.4 and see what would be the expected result
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about keyframes from an old file not working correctly unless a new keyframe is added. The steps involve opening a file, noticing F-curve issues, then adding a new keyframe to fix it.
Bug report 2 is about baking actions with Overwrite option leading to double keyframes (same frame) and linear interpolation. Steps are baking an action on an armature, checking the graph editor for duplicate keyframes.
The core issues seem different: one is about old file keyframes not working without new ones, the other is about baking creating duplicate keyframes. The descriptions don't match. So they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 11.824021,
"duplicate_report_number": "109079"
}