We’ll discuss this more in a future post. In 3D, different engines use different conventions! For example, some engines use z-axis for depth, others use y-axis for depth. In 2D, the x-axis is always horizontal and the y-axis is always vertical. In 3D, we have an additional “depth” axis (often called z-axis). In 2D, there are horizontal and vertical axes, which we refer to as the x-axis and y-axis respectively. A coordinate system is defined by its origin and its axes. In video games, we represent object positions relative to a coordinate system. And gameplay events are often tied to position - if Pac-Man’s position is too near to a ghost’s position, Pac-Man will die (unless he has eaten power pellet). As you might expect, an object’s position affects where it renders on screen. The positions of objects are important for both rendering and gameplay reasons. When you’re driving in the real world, your car has a different position compared to other cars and stationary objects around you. Let’s start by stating something obvious: in video games (and the real world), objects have different positions! When you play Pac-Man, the ghosts and Pac-Man each have different positions in the maze.
If you’re already familiar with vectors and just want to read about coding them, skip down to Writing a Vector Class. This section provides a “crash course” in vectors and vector operations. This post will cover Vectors, which enable the engine to represent important spacial concepts such as “position” and “direction”.īefore we talk about coding vectors, we need to understand what vectors are and what they can do. In particular, I want to implement Vectors, Matrices, and Quaternions. We have added a basic math library to the 3D engine, but we’re still missing several fundamental mathematical building blocks to move forward and build full-fledged 3D environments.
0 kommentar(er)
