I had a cool idea that I completely gave up on because I tried to learn how to do it and realized what I was asking was so insanely complicated and time consuming that I couldn’t do it. I play a lot of games, I know what would make a good one, there’s just a gaping chasm between knowing and creating.
The problem is that this complexity isn’t just a one-off thing you need to get through. There’s a ton of details which matter, which you will not have thought through as part of your idea.
Many of these details, you will encounter as you write code. As in, you’ve just worked for three weeks on a feature and then realize a glaring problem in one of the details. Then you spend another week trying to find a solution. And worst-case that solution is to rip out that month of work and start fresh.
This has been my biggest learning from dabbling in gamedev for a while: Make a stupid paper model first.
Even if you spend a week glueing sheets of paper, and you don’t really even get that close to your actual idea, the more of these details you think of upfront, the higher your chance of getting anywhere (or scrapping your idea without wasting months trying to put it into code).
Well, and the other big learning was: Holy crap, gamedev is hard.
I know how to “code”. I’m a senior developer and have worked on multiple large-scale software projects.
The scope of the game I was trying to create, was laughable in comparison. As in shitty 2D, tile-based, turn-based.
I encountered performance problems like I’ve never had to deal with in my career, because it turns out the whole games industry is fueled by smokes and mirrors.
Know how ray-traced lighting is the craziest new technology? Yeah, that’s literally just a matter of hardware being strong enough that we can simulate lighting in the way it actually works. It’s conceptually simpler than the ever more sophisticated bullshitting we did beforehand.
I had a cool idea that I completely gave up on because I tried to learn how to do it and realized what I was asking was so insanely complicated and time consuming that I couldn’t do it. I play a lot of games, I know what would make a good one, there’s just a gaping chasm between knowing and creating.
The problem is that this complexity isn’t just a one-off thing you need to get through. There’s a ton of details which matter, which you will not have thought through as part of your idea.
Many of these details, you will encounter as you write code. As in, you’ve just worked for three weeks on a feature and then realize a glaring problem in one of the details. Then you spend another week trying to find a solution. And worst-case that solution is to rip out that month of work and start fresh.
This has been my biggest learning from dabbling in gamedev for a while: Make a stupid paper model first.
Even if you spend a week glueing sheets of paper, and you don’t really even get that close to your actual idea, the more of these details you think of upfront, the higher your chance of getting anywhere (or scrapping your idea without wasting months trying to put it into code).
Well, and the other big learning was: Holy crap, gamedev is hard.
I know how to “code”. I’m a senior developer and have worked on multiple large-scale software projects.
The scope of the game I was trying to create, was laughable in comparison. As in shitty 2D, tile-based, turn-based.
I encountered performance problems like I’ve never had to deal with in my career, because it turns out the whole games industry is fueled by smokes and mirrors.
Know how ray-traced lighting is the craziest new technology? Yeah, that’s literally just a matter of hardware being strong enough that we can simulate lighting in the way it actually works. It’s conceptually simpler than the ever more sophisticated bullshitting we did beforehand.