Page MenuHome

Color controllers stuck in multiply node and «infect» other nodes. Viral behaviour!
Closed, DuplicatePublic

Description

2.80 (sub 45), 798d2cadc307, 2019-03-04 00:30

IDK how to reproduce, I just working a lot with shader, trying to achieve certain result.
But here is the file.
As I found: error is inside material: it remains if i append material.

May be it is similar issue, that was with value-node stucking.
And the bug is «viral»: look 3rd video. It seems, it expands to all nodes with color, not only multiply

Even after deleting bugged material and data, there is strange behaviour… 4th video and 2nd file





Details

Type
Bug

Event Timeline

Vyacheslav (hitrpr) renamed this task from Color controllers stuck in to Color controllers stuck in multiply node and «infect» other nodes.
Vyacheslav (hitrpr) renamed this task from Color controllers stuck in multiply node and «infect» other nodes to Color controllers stuck in multiply node and «infect» other nodes. Viral behaviour.Mar 5 2019, 11:14 AM
Vyacheslav (hitrpr) renamed this task from Color controllers stuck in multiply node and «infect» other nodes. Viral behaviour to Color controllers stuck in multiply node and «infect» other nodes. Viral behaviour!.Mar 5 2019, 11:19 AM
Vyacheslav (hitrpr) updated the task description. (Show Details)
Jacques Lucke (JacquesLucke) triaged this task as Confirmed, Medium priority.Mar 5 2019, 11:29 AM

I can see the issue in the file you provided.

What's weird is that the error does not happen when the Color output is connected to the Material Output in some way.

Also, I can't seem to be able to reproduce the issue in a new file, unfortunately.

Oh, i remember another one thing, that can be bonded.

I tried to use drivers. And once driver stuck. I will try to reproduce.
It reminds me previous value-stucking bug

Sadly can`t reproduce, but such stucking looks like the driven behavior.
And yes, it is look totally the same as I reported before: https://developer.blender.org/T61729

same symptoms as T61963, T60900

Everthing seems to be fine again when you call

bpy.data.materials['TexturedCelshader4'].node_tree.animation_data_clear()

I am pretty sure these 3 reports have the same roots, but am uncertain to merge the reports.
In any case (since all this seems to originate in double recalc -- and @Brecht Van Lommel (brecht) did rB83f8f44791374dd051728e44d89fbdeee15c60aa), will add him here...

@Philipp Oeser (lichtwerk) Yes, it helped, THANKS!
So it looks like some animation was created and it pinches value?