Next/Previous Keyframe breaks when "Show Only Selected" is disabled #93944

New Issue

Sybren A. Stüvel · 2021-12-10T16:51:56+01:00

Sybren A. Stüvel commented

2021-12-10 16:51:56 +01:00

System Information
Operating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, hash: 60a9703de8
Worked: never, 2.79 also had this problem in a way (but slightly different due to limitations of its dope sheet). 2.83 has the exact same problem described here.

Short description of error
Next/Previous Keyframe ( {key up} and {key down} in the dope sheet) do not jump to the next/previous key shown, but to the next/previous key of the active object.

In other words, it sort of works as if "Show Only Selected" is always enabled, but then even more strict, only responding to the keys of the active object. This can probably be tracked down to the dope sheet only showing animation data of the active object back in the old ≤2.79 days.

Exact steps for others to reproduce the error

Open the attached blend file.
See that the current frame is set to frame 1.
While hovering with the mouse over the dope sheet, press the up arrow {key up}.
See the message "No more keyframes to jump to in this direction". Expected behaviour: it would jump to the next keyframe shown, which is at frame 5.
Click on the Cube to make it active + selected.
While hovering with the mouse over the dope sheet, press the up arrow {key up}.
See that it jumps to frame 10, which is the next keyframe in the Cube's animation. Expected behaviour: it would jump to the next keyframe shown, which is at frame 5.

next-prev-keyframe-selection-issue.blend

**System Information** Operating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, hash: `60a9703de8` Worked: never, 2.79 also had this problem in a way (but slightly different due to limitations of its dope sheet). 2.83 has the exact same problem described here. **Short description of error** Next/Previous Keyframe ( {key up} and {key down} in the dope sheet) do not jump to the next/previous key **shown**, but to the next/previous key of the **active object**. In other words, it sort of works as if "Show Only Selected" is always enabled, but then even more strict, only responding to the keys of the active object. This can probably be tracked down to the dope sheet only showing animation data of the active object back in the old ≤2.79 days. **Exact steps for others to reproduce the error** 1. Open the attached blend file. 2. See that the current frame is set to frame 1. 3. While hovering with the mouse over the dope sheet, press the up arrow {key up}. 4. See the message "No more keyframes to jump to in this direction". *Expected behaviour:* it would jump to the next keyframe shown, which is at frame 5. 5. Click on the Cube to make it active + selected. 6. While hovering with the mouse over the dope sheet, press the up arrow {key up}. 7. See that it jumps to frame 10, which is the next keyframe in the Cube's animation. *Expected behaviour:* it would jump to the next keyframe shown, which is at frame 5. ![image.png](https://archive.blender.org/developer/F12727458/image.png) [next-prev-keyframe-selection-issue.blend](https://archive.blender.org/developer/F12727463/next-prev-keyframe-selection-issue.blend)

Sybren A. Stüvel commented

2021-12-10 16:51:56 +01:00

Added subscriber: @dr.sybren

Dan McLaughlin was assigned by Sybren A. Stüvel

2021-12-10 16:57:00 +01:00

Sybren A. Stüvel commented

2021-12-10 16:57:00 +01:00

Added subscriber: @DrMc

Sybren A. Stüvel commented

2021-12-10 16:57:00 +01:00

Assigning to @DrMc as he's looking for a task to work on. I think this could be a nice one to look at. As a starting point, check the keyframe_jump_exec() function. It determines some filtering options (ads.filterflag), which are then used to find the keyframes to jump over. I'm guessing that these are set incorrectly.

Assigning to @DrMc as he's looking for a task to work on. I think this could be a nice one to look at. As a starting point, check the `keyframe_jump_exec()` function. It determines some filtering options (`ads.filterflag`), which are then used to find the keyframes to jump over. I'm guessing that these are set incorrectly.

Pratik Borhade commented

2021-12-11 04:47:18 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-12-14 06:53:03 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Sybren A. Stüvel commented

2022-03-18 12:48:27 +01:00

Hi @DrMc , how are things going?

Dan McLaughlin commented

2022-03-18 13:58:30 +01:00

Update over on the chat channel

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Next/Previous Keyframe breaks when "Show Only Selected" is disabled #93944