Blender 3.2.1 - Animation on nodes gets bugged out when dealing with Node Groups (duplicate node names) #101109

New Issue

Carlo Andreacchio · 2022-09-16T02:59:22+02:00

Carlo Andreacchio commented

2022-09-16 02:59:22 +02:00

System Information
Operating system: Ubuntu 21.04
Graphics card: GTX 1080

Blender Version
Broken: 3.2.1
Worked: 2.79

Short description of error
Animation on a node, that then gets put into a node group, effects other nodes later on

Exact steps for others to reproduce the error

Open attached blend file
Make sure you have blender 2.79 hotkeys otherwise i dont know if this will work 100%
in the material editor, press ctrl g to add it to a node group
press tab to exit out
shift a -> c -> m (add mix node)
drop it between the node group and the hue sat value node
scrub the timeline

Expected behaviour
New node does not have a animation applied to it
materialAnimationBug.blend

note that the issue goes away after saving/reloading (so in this step the borked animation paths seem to be cleaned up)

**System Information** Operating system: Ubuntu 21.04 Graphics card: GTX 1080 **Blender Version** Broken: 3.2.1 Worked: 2.79 **Short description of error** Animation on a node, that then gets put into a node group, effects other nodes later on **Exact steps for others to reproduce the error** 1. Open attached blend file 2. Make sure you have blender 2.79 hotkeys otherwise i dont know if this will work 100% 3. in the material editor, press ctrl g to add it to a node group 4. press tab to exit out 5. shift a -> c -> m (add mix node) 6. drop it between the node group and the hue sat value node 7. scrub the timeline Expected behaviour New node does not have a animation applied to it [materialAnimationBug.blend](https://archive.blender.org/developer/F13497413/materialAnimationBug.blend) note that the issue goes away after saving/reloading (so in this step the borked animation paths seem to be cleaned up)

Carlo Andreacchio commented

2022-09-16 02:59:22 +02:00

Added subscriber: @candreacchio

Richard Antalik commented

2022-09-16 07:13:07 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-09-16 07:13:07 +02:00

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

Richard Antalik commented

2022-09-16 07:13:07 +02:00

That's quite interesting, it actually affects the result, so it's not just UI glitch...

Carlo Andreacchio commented

2022-09-16 07:16:41 +02:00

Yep, and whats more crazy is that the element thats animated, is not highlighted yellow / green

Philipp Oeser commented

2022-09-16 10:19:04 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-09-16 10:19:04 +02:00

There is something wrong in interpreting that FCurve path.
Since this is name-based, blender somewhat gets confused because of that "duplicate" name (both nodes are named "Mix.001" - only one is inside the nodegroup, the other one not...)
If the "failing" one is renamed, the issue goes away on it (it is still preserved on the "working" in the nodegroup.

On a side-note: Just realized that if a node has animation (such as the Factor here) and it gets grouped, the Factor is then noodled up to the nodegroup (which is generally a good thing -- issue being that the effective animation on the node is now disabled, since the Factor on the nodegroup itself is not getting the animation transferred over).
Will report that separately though.

There is something wrong in interpreting that FCurve path. Since this is name-based, blender somewhat gets confused because of that "duplicate" name (both nodes are named "Mix.001" - only one is inside the nodegroup, the other one not...) If the "failing" one is renamed, the issue goes away on it (it is still preserved on the "working" in the nodegroup. On a side-note: Just realized that if a node has animation (such as the `Factor` here) and it gets grouped, the `Factor` is then noodled up to the nodegroup (which is generally a good thing -- issue being that the effective animation on the node is now disabled, since the Factor on the nodegroup itself is not getting the animation transferred over). Will report that separately though.

Philipp Oeser commented

2022-09-16 10:20:37 +02:00

In #101109#1418068, @lichtwerk wrote:
On a side-note: Just realized that if a node has animation (such as the Factor here) and it gets grouped, the Factor is then noodled up to the nodegroup (which is generally a good thing -- issue being that the effective animation on the node is now disabled, since the Factor on the nodegroup itself is not getting the animation transferred over).
Will report that separately though.

@candreacchio : is that what you meant with the following?

In #101109#1418015, @candreacchio wrote:
Yep, and whats more crazy is that the element thats animated, is not highlighted yellow / green

> In #101109#1418068, @lichtwerk wrote: > On a side-note: Just realized that if a node has animation (such as the `Factor` here) and it gets grouped, the `Factor` is then noodled up to the nodegroup (which is generally a good thing -- issue being that the effective animation on the node is now disabled, since the Factor on the nodegroup itself is not getting the animation transferred over). > Will report that separately though. @candreacchio : is that what you meant with the following? > In #101109#1418015, @candreacchio wrote: > Yep, and whats more crazy is that the element thats animated, is not highlighted yellow / green

Carlo Andreacchio commented

2022-09-16 10:54:02 +02:00

Factor colour i was commenting on
2022-09-16 18-15-52.mkv

Following on from this, if you instead of adding in another mixrgb node, you rename the Hue Sat node to Mix.001, it will animate the Hue 0,1 and not the factor.

The animation gets unlinked if you save / revert the file. However, it is not an ideal workflow.

I have also had duplicated objects be effected similarly previously (where trying to make unique animation, doesnt actually make it unique animation) and the only way to fix it was to save close reopen, but unable to replicate it like this instance.

Factor colour i was commenting on [2022-09-16 18-15-52.mkv](https://archive.blender.org/developer/F13498817/2022-09-16_18-15-52.mkv) Following on from this, if you instead of adding in another mixrgb node, you rename the Hue Sat node to Mix.001, it will animate the Hue 0,1 and not the factor. The animation gets unlinked if you save / revert the file. However, it is not an ideal workflow. I have also had duplicated objects be effected similarly previously (where trying to make unique animation, doesnt actually make it unique animation) and the only way to fix it was to save close reopen, but unable to replicate it like this instance.

Philipp Oeser commented

2022-09-16 10:54:06 +02:00

Also note that the issue goes away after saving/reloading (so in this step the borked animation paths seem to be cleaned up)

Philipp Oeser changed title from ~~Blender 3.2.1 - Animation on Material Nodes gets bugged out when dealing with Node Groups~~ to Blender 3.2.1 - Animation on Material Nodes gets bugged out when dealing with Node Groups (duplicate node names)

2022-09-16 10:54:58 +02:00

Philipp Oeser commented

2022-09-16 10:57:14 +02:00

Same is true for Geometry nodes as well

Philipp Oeser changed title from ~~Blender 3.2.1 - Animation on Material Nodes gets bugged out when dealing with Node Groups (duplicate node names)~~ to Blender 3.2.1 - Animation on nodes gets bugged out when dealing with Node Groups (duplicate node names)

2022-09-16 10:57:29 +02:00

Philipp Oeser self-assigned this 2022-09-16 12:37:53 +02:00

Philipp Oeser commented

2022-09-16 12:37:53 +02:00

Think I got the fix