Only Selected display option in animation editors keeps displaying unused fcurves #75476

Open
opened 2020-04-07 11:38:38 +02:00 by Daniel Salazar · 19 comments
Member

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75

Blender Version
Broken: version: 2.83 (sub 12), branch: master, commit date: 2020-04-06 21:23, hash: 10f0e003a9

Short description of error
Unused fcurves within an action (result from deleted bones) are not filtered out by the Only Selected option in "animation editors". They keep being displayed even when their parent bones are obviously not selected (since they do not exist)

Exact steps for others to reproduce the error
What you see in both animation editors are unused fcurves, even when both have the Only Selected option on.

I assume it is just failing to filter that case.

OnlySelected.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75 **Blender Version** Broken: version: 2.83 (sub 12), branch: master, commit date: 2020-04-06 21:23, hash: `10f0e003a9` **Short description of error** Unused fcurves within an action (result from deleted bones) are not filtered out by the Only Selected option in "animation editors". They keep being displayed even when their parent bones are obviously not selected (since they do not exist) **Exact steps for others to reproduce the error** What you see in both animation editors are unused fcurves, even when both have the Only Selected option on. I assume it is just failing to filter that case. [OnlySelected.blend](https://archive.blender.org/developer/F8454388/OnlySelected.blend)
Author
Member

Added subscriber: @zanqdo

Added subscriber: @zanqdo
Author
Member

This comment was removed by @zanqdo

*This comment was removed by @zanqdo*

Added subscribers: @dr.sybren, @mano-wii

Added subscribers: @dr.sybren, @mano-wii

I'm not sure what I should see this file, it might be a good idea to simplify the file to show what the problem is even for those who don't work much with animation.

I'm not sure what I should see this file, it might be a good idea to simplify the file to show what the problem is even for those who don't work much with animation.

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

This example file is too complex to analyze. Please create a minimal example, and include steps to reproduce (so for example "Channel A is shown, but does not belong to selected object B even though 'Only Selected' is enabled").

This example file is too complex to analyze. Please create a minimal example, and include steps to reproduce (so for example "Channel A is shown, but does not belong to selected object B even though 'Only Selected' is enabled").
Author
Member

Sure thing. Here´s a step by step.
OnlySelected.blend
We have this scene which contains an armature with only 2 bones which named ONE and TWO. Both are selected.
image.png
The Action however contains fcurves for 4 Bones. Why? Because 2 bones have been deleted, leaving those fcurves behind and unused.
image.png
Now we have actually 2 problems with the animation editor´s filtering options which I explain in the following video.

Disabled FCurves.mp4

Sure thing. Here´s a step by step. [OnlySelected.blend](https://archive.blender.org/developer/F8480271/OnlySelected.blend) We have this scene which contains an armature with only **2 bones** which named **ONE** and **TWO**. Both are selected. ![image.png](https://archive.blender.org/developer/F8480280/image.png) The Action however contains fcurves for **4 Bones**. Why? Because 2 bones have been deleted, leaving those fcurves behind and unused. ![image.png](https://archive.blender.org/developer/F8480309/image.png) Now we have actually 2 problems with the animation editor´s filtering options which I explain in the following video. [Disabled FCurves.mp4](https://archive.blender.org/developer/F8480351/Disabled_FCurves.mp4)

Now we have actually 2 problems with the animation editor´s filtering options which I explain in the following video.

Don't mix up reports, each task should be about one thing only. And please don't require developers to watch a 3+ minute video for something that could be explained in a few lines of text. Videos can be very helpful when used in addition to a description, but shouldn't replace one.

> Now we have actually 2 problems with the animation editor´s filtering options which I explain in the following video. Don't mix up reports, each task should be about one thing only. And please don't require developers to watch a 3+ minute video for something that could be explained in a few lines of text. Videos can be very helpful when used in addition to a description, but shouldn't replace one.

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Sybren A. Stüvel self-assigned this 2020-04-20 10:41:22 +02:00

The Action however contains fcurves for 4 Bones. Why? Because 2 bones have been deleted, leaving those fcurves behind and unused.

Blender shows the curves related to the selected object. In the case of armatures, this means for selected bones and errors. If you add another object to the scene and select that, all the 4 FCurves for the bones are hidden because they're no longer related to the selected object. As it's working as designed, I don't consider this a bug.

> The Action however contains fcurves for 4 Bones. Why? Because 2 bones have been deleted, leaving those fcurves behind and unused. Blender shows the curves related to the selected object. In the case of armatures, this means for selected bones and errors. If you add another object to the scene and select that, all the 4 FCurves for the bones are hidden because they're no longer related to the selected object. As it's working as designed, I don't consider this a bug.
Author
Member

The Only Selected feature works on a channel level as you can read in the tooltip

image.png

So when in Pose Mode, it will show you the channels related to whatever bones are selected.

You can prove this by selecting only one of the two bones in the provided simplified blend file.

So why would channels unrelated to the current selection be shown at all?

image.png

The *Only Selected* feature works on a **channel level** as you can read in the tooltip ![image.png](https://archive.blender.org/developer/F8484869/image.png) So when in *Pose Mode*, it will show you the channels related to whatever bones are **selected**. You can prove this by selecting only one of the two bones in the provided simplified blend file. So why would channels unrelated to the current selection be shown at all? ![image.png](https://archive.blender.org/developer/F8484878/image.png)

It says "related to selected objects and data". It doesn't say "only selected bones". While you're in pose mode, the armature object itself is still selected too.

It looks like it's implemented as "hide channels of not-selected bones"; you can also see this in skip_fcurve_selected_data() in anim_filter.c. A pose channel without a bone is never hidden.

Of course you can say that this is an annoying implementation, but from the looks of it it was a deliberate design choice, and thus not a bug.

It says "related to selected objects and data". It doesn't say "only selected bones". While you're in pose mode, the armature object itself is still selected too. It looks like it's implemented as "hide channels of not-selected bones"; you can also see this in `skip_fcurve_selected_data()` in [anim_filter.c](https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/animation/anim_filter.c). A pose channel without a bone is never hidden. Of course you can say that this is an annoying implementation, but from the looks of it it was a deliberate design choice, and thus not a bug.
Author
Member

In #75476#913925, @dr.sybren wrote:
It says "related to selected objects and data". It doesn't say "only selected bones". While you're in pose mode, the armature object itself is still selected too.

OK, I understand, but then if that is the case, how do we explain this behavior?

Here, bone ONE is selected. Channels related to bone TWO are hidden
image.png

Here, bone TWO is selected. Channels related to bone ONE are hidden.
image.png

So it kinda shows that the feature is supposed to work on selected bones?

> In #75476#913925, @dr.sybren wrote: > It says "related to selected objects and data". It doesn't say "only selected bones". While you're in pose mode, the armature object itself is still selected too. OK, I understand, but then if that is the case, how do we explain this behavior? Here, bone ONE is selected. Channels related to bone TWO are hidden ![image.png](https://archive.blender.org/developer/F8484902/image.png) Here, bone TWO is selected. Channels related to bone ONE are hidden. ![image.png](https://archive.blender.org/developer/F8484904/image.png) So it kinda shows that the feature is supposed to work on selected bones?
Author
Member

In other words, if the feature was not designed to filter selected bones, why is it hiding the unselected bones?

Then aren't orphan bones unselected?

In other words, if the feature was not designed to filter selected bones, why is it hiding the unselected bones? Then aren't orphan bones unselected?

There are three types of channels right now:

  • Belonging to bones that are selected
  • Belonging to bones that are not selected
  • Not belonging to any bones, so its "selected" state is undefined.

Any filter that masks based on the selected state of the bones is free to do with that third category, because it cannot be reasoned about in terms of selectedness.

There are three types of channels right now: - Belonging to bones that are selected - Belonging to bones that are not selected - Not belonging to any bones, so its "selected" state is undefined. Any filter that masks based on the selected state of the bones is free to do with that third category, because it cannot be reasoned about in terms of selectedness.

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'

This behaviour can be changed, so that "Selected Only" means really only "belonging to bones that are selected", after #75926 (FCurves are only marked invalid after they have been shown in the UI) has been implemented.

This behaviour can be changed, so that "Selected Only" means really only "belonging to bones that are selected", after #75926 (FCurves are only marked invalid after they have been shown in the UI) has been implemented.
Member

Added subscriber: @BassamKurdali

Added subscriber: @BassamKurdali
Member

whether this is a bug or not, it's not desirable behavior, as the animator has no way to hide the unwanted channels; and there could be good reasons (not too lazy to delete error channels) for instance, if the action is intended for multiple armatures with extra bones. Maybe the only show error channels could be used to filter this behavior?
[edit] Aah, I see, fixing it involves fixing the other bug first.

whether this is a bug or not, it's not desirable behavior, as the animator has no way to hide the unwanted channels; and there could be good reasons (not too lazy to delete error channels) for instance, if the action is intended for multiple armatures with extra bones. Maybe the only show error channels could be used to filter this behavior? [edit] Aah, I see, fixing it involves fixing the other bug first.
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:36:14 +01:00
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#75476
No description provided.