Mix Shader not working for 2nd node tree (Using B 2.90.0)

[gurnea]

Following along with the tutorial fine until one of the last steps where you add the mix shader and move the animation of the 2nd tree 250 frames forward.

As per the video Frame 1 of shader 1 should be a “duplicate” of frame 251 of shader 2, however shader 2 gives me nothing in viewport or render.

Shader 1 Frame 1:

Shader 2 Frame 251

Have rechecked the shader values to make sure there are no errors in values entered.

Is this a conflict or issue with Blender 2.90.0 ?

[spikeyxxx]

Could you provide  screenshots of the entire Node tree at Frame 1 and 251?

(The Mix Shader is not ‘broken’ or changed in 2.90)

[gurnea]

Thanks @spikeyxxx 

Frame 1:

Frame 251:

I havent reached the stage of adding keyframes to the mix shader yet – still trying to get the test renders to match

SS of Graph editor (if I’ve made an error with the interpolation or extrapolation):

Thanks for taking the time to look at this.

[spikeyxxx]

Well, it looks like you have two Mapping Nodes on top of each other in the bottom part of your tree:

The top one, that is visible has the keyframes, bot no input in the Vector socket, so in stead of using the Object Coordinates, it just uses one point:0, 0, 0), So everything that comes after that Mapping Node is being calculated in that single point. Hence the single color on frame 251.

I hope that helps.

[gurnea]

Why, that sneaky little bas..ket!!

Thank you @spikeyxxx, it was exactly as you said.

I do’t think I would have ever spotted that, so thank you for looking at it. Its appreciated!

I now know another thing to check before rage quitting a project.

[Mark Smith]

@spikeyxxx what tipped you off that it was two stacked?

[spikeyxxx]

@me1958424 looking carefully 😉

I first noticed that the Vector field said (0.000, 0.000, 0.000), meaning the Vector input socket was not connected, but it looked connected at first glance..then I noticed the other Mapping Node ‘shining through’…

[Kent Trammell]

@spikeyxxx with eagle eyes!

[spikeyxxx]

@theluthier Once you’ve noticed it, it’s so obvious (too many input sockets, some ‘brighter’ than others, etc…), that I’m ashamed that it took me so long to notice 😉

[Author]

Posts