Hey /g/ So do you guys have any good suggestions for books about

>>55322460

Watch OpenGL tutorials on youtube anon.

Your best bet is C++, but Graphics can be done in Java. A game engine is far more than a renderer and graphics pipeline tho.

That great big game development book that everyone recommends doesn't go into enough depth.

>>>/3/

>>55322583
I'm planning to start simple. Maybe 2D. At the most a doom engine clone.

File: 81HP+upmFML[1].jpg (331KB, 1145x1499px) Image search: [Google]

331KB, 1145x1499px

http://learnopengl.com + pic related

For 2D games the knowledge in these two is maybe a bit overkill. At the end of the day 2D games is generally just putting quads on the screen with sprites on them.

I'd recommend you don't just copy and paste what learnopengl says. It teaches you the concepts but it doesn't do it in a flexible or extensible way, so you're going to end up with a bunch of programs that only do one thing rather than an "engine" as such.

I'd recommend you target OpenGL 4.3 if you can. You end up leaving a lot of people behind (I don't think Mesa drivers support it yet and no idea about Mac) but you also get compute shaders and SSBOs which I think are great. If you want max compatibility you need to stay with like OpenGL 3.2 or something.

Use http://docs.gl for an API reference, it also tells you which version all the functions are available in.

>>55322971
Cool, thanks

What about DirectX? Should I be worried about learning that as well if I want to one day do this professionally?

>>55323062
Yeah but it'll be easier to learn when you know OpenGL already. Same with Vulkan and DX12, even if they're very different in terms of how you write them they still contain the same core concepts.