Week 10

We then went over polygons in the context of 3D modelling and design. This is a topic that I already had some knowledge about, as I've got prior experience with software like Blender3D. Polygons in geometry are shapes made up of points, lines and areas. In 3D, however, these terms change to 'vertices', 'edges' and 'faces' respectively. Altogether, these are referred to as topology, and can be good or bad. It's best to strive for neat and organised topology, as it can warp the way the model renders if done badly. I love working in 3D, and follow a lot of online tutorials to teach myself the art, so these particular concepts are already familiar. 

Following this, we touched on cartesian and quaternion coordinates. These are, simply put, points or locations in 3D space. The main difference between the two is that cartesian coordinates encapsulate three values (x,y,z), and quaternion coordinates encapsulate four (x,y,z,w). Cartesian is the most common as it exists on the three axes. Additionally, the Eular concept is the idea that all angles exist within a scope of -180° and 180°. 

Finally, we moved on to vectors. These are simple enough; a vector determines direction and/or magnitude and is typically made up of two or three values. In coding, a Vector3 is coordinates for the x, y and z position of the target. To create movement using a vector, the input must include the direction along cartesian space + the distance travelled. For example, (0,1,0) means moving one increment along the y axis. 

A ray-cast us a hypothetical (i.e. without thickness or physical substance) line from one point to another. A common use for this is when determining whether a bullet will connect with something without having to actually release the projectile itself. I think I understand the basic idea of what a ray-cast is, but I might need to see it in practical application to fully get it.