Animation should be seperate for groups or at least not be affected by node deletion in new groups.
When swapping duplicated compositor groups, if I remove the key frames for animation for a node in one group like glare sunbeams it reflects the original group that I duplicated. I can't even delete it from the duplicated group as doing that still removes the animation from the original. I should be able to duplicate a group I like and delete nodes from it without deleting animations from the original by removing a node from the new group.
Ideally when a new group is formed it wouldn't have the animation or at least deleting it from the new group wouldn't also delete the keyframes from the original.
In the images deleting the glare sunbeams node from the bazzite compositing node group, which is a new group based off the steamos compositing group, removes the animation from the orginal steamos group.
The only workaround is muting the nodes but keeping them in the setup. (they can be off to the side disconnected)
9 Comments
Someone seems to have fixed it, reported it better the second time lol
Can't tell if it's a bug or on purpose.
It definitely looks like a bug to me. The nodes of one group should not affect the animation of another. You should report it.
"Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors."
got this reply when I reported it as a bug
Bit frustrating they acted like it isn't a bug since it definitely seems like a bug, but I guess I'll just make new files for now, kinda makes the compositor having groups useless...
Copying and pasting the nodes into a new group instead of making a new group based off an existing one might work actually, will try that.
To clarify, what you're experiencing is when you duplicate a node group and press the "Make Single User" button, then delete a node with animation in the duplicated group, the original node group loses it's animation? You should at least ask for clarification on why it was closed, in case this is intended for some odd reason, but I think this behavior makes no sense.
Yeah no other node group works like this and the point of giving compositor groups was to have parity, I'm bad at explaining bugs, I'm sure someone else will experience this issue soon enough and report it with more clarity than I did.