Add FilterNode to AnimationTree to isolate bone animations without any other operations

[TheConceptBoy]

Describe the project you are working on

A game that has a single armature with multiple animations that should simply play besides each other without affecting each other.

Describe the problem or limitation you are having in your project

None of these nodes offer allow you to exclude or filter out certain bones from an animation as a sole operation. Blend and Add have a filter feature but I don't want to blend or add anything. One Shot has a filter operation but again, I don't want to add any single shot animations either. I just want to take the supplied animation and get bypass certain bones , no adding / blending involved.

Feature issue showcase. https://youtu.be/t7XuSW_GXbk

Describe the feature / enhancement and how it helps to overcome the problem or limitation

A Filter Node who's sole purpose is to accept an animation as an input and allow you to select certain bones to be filtered (Just like the filter feature on Blend, Add and One Shot but without any extra operations done by those nodes)

Right now I can use the One Shot bone to achieve this but this use case was neither described in the docs, not does it feel like that's the intended use case of the node. A dedicated node would be much more clear.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

If this enhancement will not be used often, can it be worked around with a few lines of script?

Oh, it'll be used often, I'm certain. Nothing else besides of the One Shot node workaround can allow you to do this.

Is there a reason why this should be core and not an add-on in the asset library?

Doesn't make sense to not make it core- seems like something that should have already been a part of animation tree. Who doesn't need to do a simple operation like filtering out certain nodes without introducing other operations like blend, add or One Shot?

[Daylily-Zeleen]

I think it is meanningful that only using multiple inputs.

Here is another proposal about filter node.

[Radivarig]

I think it would be useful to allow more granular filtering, like ignore position/rotation or even per axis.