Can't beat Haworth Pizza's tbh ;)

The MEng does sound good a lot of people rate it highly. Unfortunately the industry placement isn't very specific to the course although in the modules we now only share two (instead of the four last(this) year) the others are *very* game specific.

In response to the OP, I just bought two books, an intermediate and advanced book on Game Engine development. The ISBN-10 numbers are 1584504730 & 012229063 respectively. Even if you find them too advanced (or even too basic) they are a good starting point, in my opinion, to give you the general idea of how they work.

If you don't want to build an actual engine and dive straight in, there are many recommended books on the GDNet Resources section that can help you out.

instinKt said it best in my opinion. Set lots of small goals, rather than a few big ones so that you constantly see yourself moving forward. Also, the "building a house" analagy fits quite well. There's no point building the "roof" of your game if you don't have the four walls and foundation. Start at the bottom and build up.

If you were to say, start the GUI first. You would need a renderer and a camera at the very least. So build a Camera first and the a renderer. That is your GUI foundation.

Quote:Original post by Ehrys

In response to the OP, I just bought two books, an intermediate and advanced book on Game Engine development. The ISBN-10 numbers are 1584504730 & 012229063 respectively. Even if you find them too advanced (or even too basic) they are a good starting point, in my opinion, to give you the general idea of how they work.

Actually, I wouldn't recommend that you start with making an engine. There are many pitfalls and complexities of engine design and development which mean you could dig yourself into a hole. Starting out on something that big you could end up disheartened and lose your motivation.

Definitely make 2-3 manageable small games in the API of your choice first before attempting to write an engine.