*@Sean Kennedy* I did cram a lot of information into quite short time in these videos to make it easy for people to come back and look up specific things. The workflow examples should help to understand the concepts and make the connections, being more slowly paced and in-depth :)

*@Simon Thommes* Is it ok to skip right to the workflow examples and then comeback to these chapters for a clearer concept? Or do i have to go through these chapters first?

*@victor p* Totally! I made the workflow examples to go along with the course and get progessively more advanced. If you feel like that is a better way for you to understand everything, you can start with the first workflow examples an then go back to the explanation videos.

But the workflow examples get more advanced quite quickly. I made a note for each one what level of the main course they are meant for, so keep that in mind.

Okk thank you Simon

*@Vítor* I added the file for download in the description

*@Simon Thommes* Sorry, that was stupid from my part. Thanks for the reply.

*@Vítor* No it wasn't! I added it only after you commented, because I forgot about it before. Thank you for reminding me :D

*@Simon Thommes* Oh, l was feeling so stupid, lol. Glad I could help in my own simple way. This course is sooooo interesting but sometimes there is a lot of information to absorb. Having the actual scene files will help. Again, thanks for the reply.

*@Michael Schwarz* The red, green and blue channels of the color represent the x, y and z components of the vector map that is displayed. Negative values cannot be displayed and result in black and when both x and y component are positive, that results in yellow because it mixes red + green.

If that concept is still difficult for you, you can go back to the chapter 1-1 about colors, values and vectors, or simply connect a 'Combine XYZ' node to the viewer node and observe what happens when you change the values around.

It takes some getting used to the colors until you can read a color map and understand the vector map that it represents. I hope this helps.

*@Simon Thommes* I think I've got it. x = red y = green z = blue zero and negative black. Thanks for hint. And of course I should have known it ;)

@Michael Schwarz I'll chime in here because the concept of a vector map has confused me for a while. I just started to understand it through this course. Maybe this will help others. A vector is a list of 3 values, like Simon said. In this case, X, Y, and Z. The plan is 2D, so it's like a spreadsheet of values, with rows and columns, each "cell" containing a vector. So one cell would have [0,0,0], another cell might have [1,1,1]. The range of these values depends on the properties of the "spreadsheet" (coordinate map). Some maps will have vectors with values -1 to 1, others with values 0-1. In the case of our 2D spreadsheet, each cell's vector's z component is always 0.

But with a third dimension, it's like stacking spreadsheets on spreadsheets, the z component's value varying depending on what position that spreadsheet is in in the stack.

The node tree takes every single cell in every single spreadsheet and operates on the vector in that cell, and in the case of colors, the output of the node tree determines the output color. The mix of X Y and Z values (only X = red, and Y=green values though since this is 2D) determines the resulting color for that cell. If you were to apply this to a 3D object, you'd see an even greater range of colors because now you have a Z (blue) component mixing with all the other red and green components.

@Tighe Racicot Yea, that's a good way of thinking about it! Only that the size of the spreadsheet/ the number of cells is dynamic and dependent on pixels and ray intersections.

*@victor p* It is the 'Vector Math', set to the 'Length' operation. It simply gives you the value of the length of a vector, which is, in terms of coordinate vectors, the distance to the center.

@Tighe Racicot It sounds like you are using the regular math node instead of the vector math node. That one interprets the input as a simple value and so you simply get a repetition along the x=y axis

@Simon Thommes Thanks, yes, that was it. In 2.92 the vector math nodes are a different color, and the regular math nodes are blue like in the video (you’re using 2.83 in the video). The “vector” label on the input and output clued me in that it was vector math, since the math node’s in/out labels are “Value”.

@Tighe Racicot Ah right, yes!

@Chien Hey, I'm not sure that I understand your question correctly but maybe this helps: After dividing the coordinates into cells you can do anything randomly to the parameters that are generating the shapes inside them. If you want to shift their positions, you can add a random vector to the coordinates they are using. However, you inherently can't go beyond the limits of the cells to make the shapes overall, due to the logic of how this works (I go a bit more into the logic in chapter 2-5). If you want overlapping shapes you can do this method multiple times in parallel, offset the different grids and then blend the result. But even just shifting the textures within a cell can be quite useful (I'm showing this later in chapter 4-3).

@西蒙·汤姆斯 Thank you very much for your answer, it made me understand more fully

@Victor D Yes, you're totally right, I changed the order. Thanks for pointing that out!