Quote:
Originally Posted by davidthefat
Also this is why I personally think that its good practice, its significantly more complex than robots, which is GREAT practice. BTW its not as complex as you say, its a big loop pretty much, handle input then logic then draw and repeat until game is exited or done
|
That's like saying that the code running on the stealth fighter is just "a big loop pretty much, handle input then make it fly." You're over-simplifying the concept.
Maybe the game is just a loop, but there's a lot of other stuff that goes into it... user interface, options, save systems, scene/level management, plot (or if you're doing a multiplayer game lots and lots of networking code), art assets/graphics, lighting, optimization, etc... I too have development experience outside robotics and I'm good friends with a professional game developer. On average, it takes him 3 months per product,
working on it 40+ hours per week as his full-time job.
I'm not saying this is a bad idea. It is great practice and a great way to get people involved in more programming. I'm just saying it's not a cakewalk either.