This course covers a lot of 3D graphics terminology and the basics, but it helps if you're already familiar with gaming concepts and how a game renders a scene. You should know how to read code since the course dives a little into the source. You also need Windows 8 or later and a machine capable of running Unity 3D games with the Unity game engine.
- [Instructor] We go over the 3D graphics pipeline, but you should be familiar with some terminology, like what a vertex is and what a pixel is. You should also know your way around the Unity environment. The time we spend in Unity is focused on how to improve a Unity 3D scene. We don't go over what each window in Unity does. To brush up on Unity, check out the Unity 5: 3D Essential Training course. In fact, the very same Unity scene that we analyze is from that course. Now, I want to point out that the file we analyze in this course will be different from the one you collect on your own machine.
This is because system resources vary from machine to machine. You could have a different processor with a different number of cores. You could also have more memory or less memory. These differences will affect what is shown inside the Windows Performance Analyzer when analyzing game data. For instance, the file that we analyze in this course was collected on an Intel i7-based Ultrabook that had four logical cores and 16 gigabytes of memory, but your desktop PC could have an Intel Xeon processor with 64 gigabytes of memory.
This will cause different results to show inside the Windows Performance Analyzer, so keep that in mind. And for those of you who have access to the exercise files, feel free to follow along with the provided files.