3 ms·
I'm an "enterprisey" software developer and have tried a few times to make a game by myself. When it comes to putting software and math to work, I've never been
by ehnto 7y ago
I'm an "enterprisey" software developer and have tried a few times to make a game by myself. When it comes to putting software and math to work, I've never been more impressed than with graphics rendering pipelines. It's a realm of software I'm not sure I will ever dive into, just marvel from afar. I "get" a lot of the techniques on a conceptual level, but I'm not sure I'll ever grok the code that pulls it off without spending much more time than I'm willing to commit to it.
- dahart 7y agoFWIW, it doesn’t take that much time if you start with a good setup. Writing your own game engine in order to write normal maps will take a loooong time, but you could whip up some normal maps on (for example) ShaderToy in an afternoon, easy, and there are tons of great examples there to reference and learn from.
- jayd16 7y agoIt's actually not so hard to groc once you emerce yourself in it. The hard part is you don't really experience these same patterns in enterprise work. It'll click eventually. The main thing for me was realizing the goals of the pipeline. You need to process each pixel on its own in parallel to get the speed you need. All these texture techniques are in service of prebaking data down such that it can be effeciently prefetched before the shader needs it. At least for me, understanding the why helped me understand the what.