So adding that noise texture to the bump node, then stretching the Y for that wood effect worked for 90% of the planks, but I noticed a few didn't stretch the same as the others, as if their X and Y orientations are different, How would I go about fixing that? I tried applying transformations to the troubling planks, but no effect.

If I  try to open your files for the lesson 12, 13 and 14 with Blender 2.82 a  and Sierra they can't open.

Blender stop responding until I force quit.

Thanks.

When I open the file for lesson 11 and I go in the Shading mode, the two spheres in the bottom right of the 3D viewer are black/white noise and black instead of mirrored and white...

Where are the setting to change that?

What control them?

In the video, the object's UV map is sent to two Image Texture nodes, which are mixed in a MixRGB node, and then piped to a Color Ramp, which is then sent to Principal BSDF's  specular input. 

I realize that Texture Coordinate's outputs vector date, and Image Texture nodes outputs non-vector data, but how does Texture Coordinate's UV map information affect the resulting specular calculations when the Image Nodes are already using UV map images (namely treasure-chest_COLOR and DVC-bake)?

Also, what happens a RGB color output is connected to a Black and White input (such as the Color Ramp)? Are the values in the HSV data extracted from the Color data or are RGB values somehow mapped to greyscale for the Color Ramp to use?

When I connect the overlay to colorramp as shown, it seems like all the input values to the colorramp are really close to 0. With default ramp settings, I see the following:

If I open this image in an editor and use the eye dropper on the chest, I find that the brightest parts of the wood have a brightness of around 120 (out of 256) and the darkest around 40. So I'd expect the range of input values to the colorramp to range from 40/256 = .16 to 120/256 = .47. But in fact it seems like all the input values are around 0.1 or lower. Here I've added another stop to the ramp, and observe how even with this extra stop the chest doesn't show any blue:

Only when I move the stop's position to .1 does blue start appearing, suggesting that none of the input values are much greater than .1:

Why is this? If a color value of 120/256 corresponds to a position of only about 0.1, then do all the positions above 0.25 correspond to colors "brighter than pure white"?

So, generally, when I connect Mix Shader directly to the material output, everything seems fine.  But this node won't' connect to BSDF's Base color. Also, there's no blending option in Mix Shader (probably because I'm on a newer version of Blender)

Probably I have to create another node or use a different approach?

Man, this video blew my mind. thank you Kent!

Question - if you were to take this asset into Unity, can you reuse the shader somehow, or do you need to recreate it? What about when uploading to Sketchfab?

Thank you,

Things were going well and then the treasure chest went bright pink and has stayed that way. Previously it had been just fine...so I turned something on/off somewhere, by accident. Unhooking the nodes back to where they were producing brown and grey, dirty vertex paint, etc., just fine, didn't help. Started getting pink at the time I started with the Noise Texture node. My nodes, connections, and visible settings match those in the lesson. Any suggestions? Thanks. (Loving the lesson by the way.)

theluthier  At video time I noticed that the material output socket is colored green. I presume that must take "shader" information.

Is a green shader node a combination of all other nodes' info (color, vector, b&w info)? Or is it that and something more perhaps?