Essential Math for Games Programmers(essentialmath.com)
essentialmath.com
Essential Math for Games Programmers
http://www.essentialmath.com/tutorial.htm
9 comments
I agree with most of this post except this:
> Making an amazing indie game is probably the best way to get in the game industry. Studying math is not.
There are many specialized graphics programmers in the industry. They do not design games. They do not write dialogue. They do not make any art. They don't make sound effects. They don't design plots. But they absolutely do need to know linear algebra and a lot of the stuff listed here. I think the only problem with this post is that its title suggests it's aimed at the general game programmer, but it's actually aimed at the graphics or physics programmer, the sort of guy who would work on the Unreal Engine itself, not a game made with the Unreal Engine.
EA is probably a really crappy place to work (don't know for sure, but that'd be my guess). However, I've heard amazing things about, e.g., Valve, and I think they'd be more than happy to hire a brilliant graphics programmer who's never shipped an indie title that he built from scratch.
> Making an amazing indie game is probably the best way to get in the game industry. Studying math is not.
There are many specialized graphics programmers in the industry. They do not design games. They do not write dialogue. They do not make any art. They don't make sound effects. They don't design plots. But they absolutely do need to know linear algebra and a lot of the stuff listed here. I think the only problem with this post is that its title suggests it's aimed at the general game programmer, but it's actually aimed at the graphics or physics programmer, the sort of guy who would work on the Unreal Engine itself, not a game made with the Unreal Engine.
EA is probably a really crappy place to work (don't know for sure, but that'd be my guess). However, I've heard amazing things about, e.g., Valve, and I think they'd be more than happy to hire a brilliant graphics programmer who's never shipped an indie title that he built from scratch.
Fair points. But afaik you won't work at Valve unless you have a shipped title. Where they _do_ make exceptions is with people like the CS devs or Icefrog (DOTA). So I still think that if working as a game dev is what you want to do, making a mod/indie title is the best way to go.
I know 3 people that work at EA. One of them likes it and two of them hate it. I guess it's like working in any big company. My dad worked for IBM and hated every moment. I, like him, don't think that could never really work at a big company where my creativity/intelligence/drive is inconsequential.
Edit: let me just say that maybe there are extenuating circumstances -- for example, if you presented some novel shading algorithm at SIGGRAPH or something. But for the most part, I think my claim holds.
I know 3 people that work at EA. One of them likes it and two of them hate it. I guess it's like working in any big company. My dad worked for IBM and hated every moment. I, like him, don't think that could never really work at a big company where my creativity/intelligence/drive is inconsequential.
Edit: let me just say that maybe there are extenuating circumstances -- for example, if you presented some novel shading algorithm at SIGGRAPH or something. But for the most part, I think my claim holds.
Valve isn't an ideal place to work. It has a floundering management structure, hidden office politics and a failed bonus structure. It's only relevant because of its meteoric success of Steam and skill of acquiring/courting quality teams/devs.
It's been a long while since Valve has worked on one of their own ideas.
It's been a long while since Valve has worked on one of their own ideas.
Portal 2 came out just two years ago
Dota 2 this year
Dota 2 this year
a good demo still beats the crap out of any amount of academic skill. good graphics and physics code often comes from being especially clever and creative with the performance budget and tools available... when your demo implements bits of tech that approach or exceed the quality of commercial games and engines then, so long as you actually made it and people look at it, your actual ability with math is irrelevant, even if you blindly copied all the algorithms to make your stuff work - making things work is far more important. :)
I wasn't really ever referring to pure academic skill.
I have some graphics programming experience outside of a professional context, and I can say you're not going to get stuff to work by blindly copying other people's code in any complex, new, and non-trivial situation. You've got to understand what's going on to at least some degree. You'll never get the top graphics jobs by copying code; you'll very quickly be identified as someone who doesn't really know what he's doing.
With that said, anybody who's truly got the math and programming know-how for this stuff will be able to easily put together demos. A demo is not a self-published indie title. These are two totally different things. If you've got a new terrain LOD algorithm, for instance, you definitely do not need to build an entire published and profitable game to show that off to the world.
I have some graphics programming experience outside of a professional context, and I can say you're not going to get stuff to work by blindly copying other people's code in any complex, new, and non-trivial situation. You've got to understand what's going on to at least some degree. You'll never get the top graphics jobs by copying code; you'll very quickly be identified as someone who doesn't really know what he's doing.
With that said, anybody who's truly got the math and programming know-how for this stuff will be able to easily put together demos. A demo is not a self-published indie title. These are two totally different things. If you've got a new terrain LOD algorithm, for instance, you definitely do not need to build an entire published and profitable game to show that off to the world.
> fantasy land in which the smarter you are, the better game you'll make
This is very true. I can testify that I work very hard at making my own 3D/2D game engines/gui frameworks. Yet, how many games I have finished: 0
> I've probably abandoned about 95+% of game projects I started
We should start a club ( http://jeffrey.io/wall-of-shame )
> perpetuates the idea that good games == good technology
I think, we are very fortunate, to be in this realm of easy and cheap CPU. good technology, back in the old days, were critical to putting out amazing games. This was simply due to the fact that without the crazy tech, you wouldn't have anything worth playing.
Now, woah, I can have my browser in an emulated android instance running on my emulated linux machine run games just as good as SNES.
For some new side projects, when I just "let go" of all the tricks and crazy algorithms I know and just "code to get things done"; it's like flying. Maybe in the next couple of years, I'll actually finish a game... Maybe
This is very true. I can testify that I work very hard at making my own 3D/2D game engines/gui frameworks. Yet, how many games I have finished: 0
> I've probably abandoned about 95+% of game projects I started
We should start a club ( http://jeffrey.io/wall-of-shame )
> perpetuates the idea that good games == good technology
I think, we are very fortunate, to be in this realm of easy and cheap CPU. good technology, back in the old days, were critical to putting out amazing games. This was simply due to the fact that without the crazy tech, you wouldn't have anything worth playing.
Now, woah, I can have my browser in an emulated android instance running on my emulated linux machine run games just as good as SNES.
For some new side projects, when I just "let go" of all the tricks and crazy algorithms I know and just "code to get things done"; it's like flying. Maybe in the next couple of years, I'll actually finish a game... Maybe
"I think, we are very fortunate, to be in this realm of easy and cheap CPU. good technology, back in the old days, were critical to putting out amazing games. This was simply due to the fact that without the crazy tech, you wouldn't have anything worth playing."
i am regularly shocked that 'world class developer a' has no idea about, e.g. bsp trees and partitioning - which are fundamental (or at least good VSD in general) to why e.g. Quake shipped when it did and not 3 years later. and when people moan about memory speeds etc... also the shocking amounts of memory used for simple things.
a couple of years back i replaced an utterly broken vsd solution in a 'AAA' game for the current/last gen consoles - the memory footprint was around 1mb, with about 640k of that being totally uncompressed PVS data as bit vectors, but it lived alongside horrendously wasteful systems that managed to use whole megabytes to do tiny things in the world - much less than, you know, drawing all of it. :P
also, do note, you can finish a shippable game in a week if you just force yourself. with a month or two constructing a usable fps with physics basic ai and loading some 3rd party environment, meshes and animations is completely feasible even with little prior knowledge. finishing things is the ultimate skill it turns out...
i am regularly shocked that 'world class developer a' has no idea about, e.g. bsp trees and partitioning - which are fundamental (or at least good VSD in general) to why e.g. Quake shipped when it did and not 3 years later. and when people moan about memory speeds etc... also the shocking amounts of memory used for simple things.
a couple of years back i replaced an utterly broken vsd solution in a 'AAA' game for the current/last gen consoles - the memory footprint was around 1mb, with about 640k of that being totally uncompressed PVS data as bit vectors, but it lived alongside horrendously wasteful systems that managed to use whole megabytes to do tiny things in the world - much less than, you know, drawing all of it. :P
also, do note, you can finish a shippable game in a week if you just force yourself. with a month or two constructing a usable fps with physics basic ai and loading some 3rd party environment, meshes and animations is completely feasible even with little prior knowledge. finishing things is the ultimate skill it turns out...
The wall of shame is not a bad idea. I'd have to go back to when I was like 15 and catalogue the failures of the past 12 years of my life. I'm already depressed just thinking about it :(
Having worked in that industry for 15 years... You might want to study math after all. It's going to be part of the job interview.
If you are not working at a large game-dev studio, you need both skills. Most of what you need to do is already 'designed' but often you end up taking calls on things that are not clearly laid out for you.
You may also end up working where there is a clear 'game designer' and 'game programmer' separation even if it is a small studio (20-30 people). In both these cases, you need to know your basic 3d maths to be useful in your role.
I concede that it's much easier nowadays since you end up using an engine that abstracts most things for you. Nevertheless, you do end up hitting the limits of the engine and may want to implement that killer feature yourself.
I have encountered all of these situations. I'll say that the minimum you should know if you want to be a game programmer is:
[Edit: Formatting]
You may also end up working where there is a clear 'game designer' and 'game programmer' separation even if it is a small studio (20-30 people). In both these cases, you need to know your basic 3d maths to be useful in your role.
I concede that it's much easier nowadays since you end up using an engine that abstracts most things for you. Nevertheless, you do end up hitting the limits of the engine and may want to implement that killer feature yourself.
I have encountered all of these situations. I'll say that the minimum you should know if you want to be a game programmer is:
- high school level algebra
- high school level trigonometry
- basic 3d vector mathematics
- an understanding of graphics transformation (and the corresponding matrices)
- basic splines
[Edit: Formatting]
There's an extremely important design skill in knowing what kinds of algorithms might be fun to turn into a playable form, and doing that is a mix of getting past preconceived "all games are like this" notions, and having substantial breadth of technical experience(i.e. if you're still in high school, it's too early to expect anything, even if you're a prodigy). But I will agree on this point - it's not the same as doing the complicated engineering needed to match existing game tech feature-for-feature. Nobody will notice a better photorealistic renderer - but they might notice an aesthetic or a kind of simulation that's completely untried or previously abandoned.
And there's also increasingly a place for "outsider" works now, because the off-the-shelf tools are very capable. Tech skills still help smooth the way with those, but I've encountered a lot of people who aren't deep into CS and get by with a lot of handholding from friends. I find this more interesting than traditional gamedev now, since there are so many perspectives outside of the tech sphere.
And there's also increasingly a place for "outsider" works now, because the off-the-shelf tools are very capable. Tech skills still help smooth the way with those, but I've encountered a lot of people who aren't deep into CS and get by with a lot of handholding from friends. I find this more interesting than traditional gamedev now, since there are so many perspectives outside of the tech sphere.
Nowhere in the post does its author imply that a game is good if and only if it was built using good technology.
You present a reasonable idea. But it's totally orthogonal to the content of the post, so I wish you hadn't made it here.
You present a reasonable idea. But it's totally orthogonal to the content of the post, so I wish you hadn't made it here.
> I think many analytic-type of people (I am part of this group) live in a fantasy land in which the smarter you are, the better game you'll make.
These days this should be called "essential math for game engine programmers". You're not going to write a good 3d game engine without knowing how to interpolate quaternions, for example (needed e.g. in skeletal animation).
If you just want to write a game, you should pick up an existing engine and go with that. No extensive math or 3d skills required.
If, however, you want to learn how computer games work underneath the surface, you will have to learn the math.
These days this should be called "essential math for game engine programmers". You're not going to write a good 3d game engine without knowing how to interpolate quaternions, for example (needed e.g. in skeletal animation).
If you just want to write a game, you should pick up an existing engine and go with that. No extensive math or 3d skills required.
If, however, you want to learn how computer games work underneath the surface, you will have to learn the math.
Carmack was a damn good game designer. Considering the reception and the financial performance of RAGE (id's latest release), I'd say he isn't that good a game designer he once was.
I can only recommend for any programmer to get into graphics/game programming even if you dont have any prior knowledge. The required skills are vastly different from web development for example. While in Web Development its alot about Architecture, Services, binding countless of Technologies together in the right way, game/graphics programming is alot more about programming clever and well-performing algorithms and math. Add some network programming (multiplayer) to the mix and you have one more extra level of complexity to master.
Gave me alot to learn!
There's a lot of binding technologies together in games programming nowadays too.
Component oriented programming makes it rather easy to pick a technology, make a component out of it and adding it into your system.
Especially if you use a prebuilt/popular component system like Unity3d you can almost just click and drag technologies together.
It's true that if you need any of your components to perform extraordinarily then you'll have to dive deep and become an expert, or make sure you find an expert to help you.
Ofcourse, if you want to do everything yourself, then you might have to learn everything yourself , and you'll have to master a lot of things. It is true that games programming covers (almost?) every field in computer science. I guess this is the result of games basically being simulations of (part of) the universe.
Component oriented programming makes it rather easy to pick a technology, make a component out of it and adding it into your system.
Especially if you use a prebuilt/popular component system like Unity3d you can almost just click and drag technologies together.
It's true that if you need any of your components to perform extraordinarily then you'll have to dive deep and become an expert, or make sure you find an expert to help you.
Ofcourse, if you want to do everything yourself, then you might have to learn everything yourself , and you'll have to master a lot of things. It is true that games programming covers (almost?) every field in computer science. I guess this is the result of games basically being simulations of (part of) the universe.
I agree with this comment. Developing a game is one of the most complicated and rewarding projects you can perform on your own. I would go as far to say that developing a complex game may even be on the level of operating system development.
I know dozens of independent developers who work on their own games (myself included) - people who work in fields completely unrelated to CS/video games, but still work on games simply because they are such complicated projects to develop.
If you're the kind of person who thrives on difficult algorithmic and code architecture problems, I highly suggest giving game development a shot.
I know dozens of independent developers who work on their own games (myself included) - people who work in fields completely unrelated to CS/video games, but still work on games simply because they are such complicated projects to develop.
If you're the kind of person who thrives on difficult algorithmic and code architecture problems, I highly suggest giving game development a shot.
Game dev certainly also requires a lot of high-level architecture work. Making a good modern game basically requires being world-class at everything, all at once.
You mean for triple A games? Yes.
Right now, I am writing a text adventure bushcraft game and the coding is almost tedious and boring.
Right now, I am writing a text adventure bushcraft game and the coding is almost tedious and boring.
Getting into embedded system is also a very good exercice to structure your mind and pay attention to your algorithms.
Probably worth noting that over time the games industry has become more specialised. The skills listed are essential for working in certain areas, for example rendering, engine work and physics.
Knowing how to interpolate a catmull rom spline is not required of a network programmer.
If you're considering a career in the games industry the best advice I can give you is to create a demo of your work. Do not build something ontop of a mod, build something of your own, be original and creative (something that the list does not emphasis). Don't worry if you can't draw, it matters not.
Knowing how to interpolate a catmull rom spline is not required of a network programmer.
If you're considering a career in the games industry the best advice I can give you is to create a demo of your work. Do not build something ontop of a mod, build something of your own, be original and creative (something that the list does not emphasis). Don't worry if you can't draw, it matters not.
I disagree slightly. I think that building a mod is, bar none, the best way to test the waters of game design. Furthermore, many (many) extremely talented game designers got into "real" game design by modding: from Counter-Strike, to DOTA, to Natural Selection, building a good mod is easier and far more consequential than slogging through building yet another Pong clone.
Wow this resource is awesome. I don't really write games per se, but I enjoy writing interactive visuals - and this will definitely help me get to the next level. Thanks!
I was thinking the same... I was about to browse through some of the demo code, but the links are broken..
Besides this, are there any other resources you would recommend for getting into writing visuals?
Thats the thing - Its hard for me to give you an exact resource - since the first thing I ever coded was a visual, using logo, when I was a wee lad. Over time I just kinda picked stuff up here and there, mostly by reading code that others have done. For a long time I was obsessed with coding straight up pixels, and writing putpixel routines. Even lots of the html5/canvas stuff I do these days is just getting the context imagedata buffer and writing straight to that. It was a totally organic process with zero structure.
So if I were going to start again from scratch, I would probably do the following:
So if I were going to start again from scratch, I would probably do the following:
- Choose one platform to target (HTML5/Canvas, WebGL, OpenGL, DirectX, etc)
- Pick up a book and learn the basics of that platform, and do the exercises
- Learn what you can about the APIs and start playing around.
- Fractals and cellular automata are always fun - you can find Mandlebrot and game of life examples in pretty much any language.
- Think of something in your head and try to make it happen!
- Add interaction
- Rinse and repeatThis is only useful if you're writing your own 3d engine. For 2d and for using existing engines just go read about polar coordinates and get really good at trigonometry in general, both not much represented on this ... probably a requirement new reading any of those anyway.
I really wish they'd use PDF instead of powerpoint.
It's really surprising there's this much math in videogame programming.
There is all kinds of awesome geometry algorithms out there but I didn't know if they were used in the real-world. http://www.cs.jhu.edu/~misha/Fall09/
My background is in math without too much knowledge about specific video games but I really love shapes. I wonder if I could fit in there.
It's really surprising there's this much math in videogame programming.
There is all kinds of awesome geometry algorithms out there but I didn't know if they were used in the real-world. http://www.cs.jhu.edu/~misha/Fall09/
My background is in math without too much knowledge about specific video games but I really love shapes. I wonder if I could fit in there.
The universe is governed by math. There's a surprising amount of math in everything.
As a starting web programmer who has to create a lot of css/javascript animations, this is amazing.
i'm always wary of this kind of stuff. learning things upfront - not just for games, but in general for programming - is often a fantastic waste of time. the greatest skill to learn imo is how to research a problem effectively when you hit it and how to (re)invent wheels when you need to... also, my experience is that things learned this way stick better and are understood more thoroughly.
Commenting to save.
No need. If you up-voted the post:
https://news.ycombinator.com/saved?id=kyle_martin1
https://news.ycombinator.com/saved?id=kyle_martin1
I'd sum up the most important skill like this: "learn how to finish projects". You can know all the math (or design) in the world, but if you can't finish anything, no one will be impressed unless you want to be code monkey #3249 at EA (and who wants to be that?). This seems easy when read on paper, but in reality it's fucking hard a shit. I've probably abandoned about 95+% of game projects I started. Anyone that says they finish more than 50% of the projects they start is full of shit. This is a skill -- and it's by far the hardest one to hone.
Note that it's not that I don't approve of OP's hard work compiling the list, I just think it perpetuates the idea that good games == good technology. Carmack is a CS genius, sure. But more importantly, he's a damn good game designer.