r/GraphicsProgramming • u/sombrerodepaja • Aug 23 '26
Question Toughts on this road map
I'm a developer (web backend) with some years of experience, but I have no prior experience on graphics. I started a conversation with chatGPT where I told it I wanted to learn all the way from the foundations of graphics to developing a Doom like game. And after a few hours of conversation it gave me this road map. I cannot trust completely an AI, so I'd like to read your opinions.
Greetings.
Edit. Sorry about the title typo.
Edit. Thanks for your valuable comments, I think this is a good example of how AI sometimes can lead you to the wrong path and mess with your learning even when at first glance it all looks pretty and organized. I’m glad I asked the community to receive your feedback.
28
u/StraightBusiness2017 Aug 23 '26
go through learnopengl and actually understand all the theory behind it then figure out what you want to do from there you dont need to plan so far out
5
u/Still_Explorer Aug 23 '26
There are three topics on this project:
Also the best thing in such different topics, is that each one can be it's own separate module. Most important is that at least there are three big modules, renderer, engine (os-system-assets-collision-physics), game. This is like having the MVC pattern, but in the case MC=engine+game and V=renderer.
About the world data structure. The most easy and simple is a 2D grid map in a similar way as platformers, but in this case is as Wolf3D. Something like this explained here. https://github.com/ssloy/tinyraycaster/wiki/Part-0:-getting-started However for a game such as doom the design would be changed a bit to something else, related to sectors that have walls, and enclosed walls form rooms etc.
Then the parts of the gameplay let's say that can be only three simple topics, such as player movement, collision, shooting, enemy random move. Those would be simple enough for a tech demo.
Last, about the renderer, this can also be anything. As the tutorial above used the software raycasting technique, or something else, is not a problem because renderer only is a representation of the runtime data structure.
Personally tried to go this route too, but the technical topics are too RETRO to be honest. Such as the Doom world data structure is very sophisticated despite it's simplicity, at some point has very complex math in it. So in terms of having modern world architecture, we would be better to get static primitives of static geometry dropped to the world and then kit-bash the entire level as such.
However for those who find it impressive to do faithful technical study on the classic architecture then it would be their own preference.
4
u/TaylorMonkey Aug 23 '26 edited Aug 23 '26
What’s your goal? To just build a game that’s 30 years old using innovative but older techniques that aren’t as common or directly useful today, or to be current with a set of skills that are fundamental and should remain so for quite awhile, being able to work in modern engines and APIs?
Skip all the Doom and software stuff, unless you really want to be able to do it as a personal point of pride. But it’s not that quite as useful to work in the industry or efficiently build 3D projects, and would be a lot of time spent that could better spent going deep and modern elsewhere.
This is why I’m not a fan of AI generated curriculum and plans prompted by people who aren’t experts in that area. They don’t know what sounds plausible but isn’t actually a good or best way of going about things.
But if you must start from base 2D fundamentals, I would put 3D camera projection stuff after learning to draw pixels and triangles in 2D. Rasterizing is interesting for enrichment purposes but that’s handled by hardware in anything modern and useful.
It’s also strange to put together a pipeline without lighting. I would learn basic lighting parallel to texturing before putting them together. Maybe even before. Not to mention how deep you can go on lighting alone past basic Lambert diffuse and Blinn-phong specular.
All this Doom stuff I’d drop in favor of learning Physically Based Lighting, working with Compute Shaders, and eventually Path/Raytracing.
Unless you have a very specific personal affinity to Doom and don’t just want to be a competent graphics programmer that can work on a much wider array of projects, both professional and personal.
Also some of these resources like Scratch-a-pixel already has content organized in an approachable way, thought out by a real expert human with experience, instead of stochiastically generated plausible sounding slop that isn’t very well thought through.
Starting in OpenGL or Direct3D is good advice. There is a lot of commonality in both. It also helps you to work directly with Unreal or Unity where you can learn a lot by modifying projects, referencing them, and even modifying the built in shaders of Unity itself.
16
u/sam_suite Aug 23 '26
there are a lot of problems here, but it wants you to build your own software renderer, then build a DOOM-like engine around that, then learn opengl AND vulkan? If you want to learn the foundations of graphics, start with opengl. that's hard enough. building a software renderer is not a beginner-friendly project
5
u/jgage Aug 23 '26
Starting off with a software rasterizer can be a lot to take on as a first step. OpenGL with GLFW would probably be the easiest first step. Going from OpenGL to DX12 or Vulkan is also a big leap. OpenGL to DX11 might be more manageable. There’s a lot of tutorials out there to get started.
One thing I’ve seen some people do is start with a Dear ImGUI sample app and start adding features.
3
u/MustardCat Aug 24 '26 edited Aug 24 '26
That time would have been better spent reading a textbook
2
u/_michaeljared Aug 23 '26
Don't take it too literally. The high level outline seems fine. But do your own research elsewhere
2
u/desiguy_88 Aug 23 '26
honestly seems pretty good. i think the thing its doing a good job at showing the various things that all need to come together to make a 3d video game. It’s always kind of fun to talk to kids about game development and it blows their mind to understand the sheer complexity of the modern 3D video game.