6 ms·
A trip through the Graphics Pipeline
- jcalabro 4y agoThis is from 2011. Fabian is incredible also, definitely give it a read!
- wg0 4y agoInteresting. I came across this previously too. Not knit picking, genuinely asking how much is this still relevant in context of modern GPUs such as RTX 3090 etc and how much has changed? I'd guess this Ray tracing etc would be new step somewhere in between?
- Agentlien 4y agoMost of this is still perfectly relevant. Looking over this again recently I was surprised how little had changed since.
- sharpneli 4y agoRT is not a different step. Just like compute shaders are not a different step in the graphics pipeline but they're an independent thing. RT dispatches are their own concept and have their own rules.
- dahart 4y agoOptiX dev here. Ray tracing is more or less completely separate from the raster pipeline, which is what this article is discussing. There’s some conceptual overlap when it comes to shading, and both pipelines share compute resources, but the “pipeline” part doesn’t overlap much (and personally I think the reasons why are interesting). The RTX cards have a separate ray tracing core in addition to the raster processing hardware, so both pipelines still exist. What this means is Fabien’s article is still absolutely relevant to the raster pipeline, it’s just missing information about today’s ray tracing pipeline.
- superjan 4y agoIt’s nitpicking.
- bmurphy1976 4y agoGiven that this is from 2011 and that is an eternity in computer graphics, how applicable is this to the modern era?
- antegamisou 4y agoThe fundamental math is always the same so it's still very relevant.
- 4RealFreedom 4y agoReminds me of when I first started learning about GPUs. They've come a long way. I think back then it was basically rasterization and culling. It's been a long time, though.
- sharpneli 4y agoIt's very relevant. The parts shown here haven't changed. The biggest things we've gotten is just more control about command submission and dependencies etc. Otherwise the rasterization pipeline still chucks along exactly as shown here. (Yeah you might want to use mesh shaders, but they're not always supported. And there is RT stuff too. But what's in this article also works fine)
- superjan 4y agoAgreed, but don’t forget about compute shaders: their programmer audience extends way beyond 3D, whereas RT with all it’s current limitations is only interesting for AAA game studios.
- mkl95 4y ago> This series is intended for graphics programmers that know a modern 3D API (at least OpenGL 2.0+ or D3D9+) In other words, it should still be relevant today.
- Agentlien 4y agoFor anyone interested in computer graphics this is an absolutely wonderful series which is still very relevant despite being 11 years old. As an aside, I mentioned this series earlier today on the Graphics Programming Discord server and now it's on the front page of HN? edit: on the other hand, searching the server it seems this article is linked there every few days, so it might just be coincidence
- psychphysic 4y agoPossibly the wrong place/person to ask, but is there a resource on how to mcguyver calculation from a graphics card.
- Agentlien 4y agoDefinitely not the wrong place nor person, but what do you mean by mcguyver in this context? If you want to use it for general purpose computation not tied to rendering I would suggest CUDA. If you want to play with rendering try shadertoy.com
- psychphysic 4y agoThanks for replying! I'll try shadertoy.com Basically how would one use a GPU to compute something without CUDA/OpenCL mostly for curiosity but say I wanted to use a PS2s graphics chip to perform a calculation. How was/is that actually done?
- Agentlien 4y agoPS2 was before the GPGPU age and its GPU is fixed functionality, so it's not suitable for general calculations. Your problem would have to align perfectly with the computations done for regular rendering. If we instead look at something more modern like an early GeForce with programmable shaders what was typically done was to set up your regular rendering of a full screen quad and write a pixel shader which performs your desired computations instead of actual lighting calculations. APIs such as CUDA and OpenCL were introduced to allow people who weren't making games to make GPU calculations without pretending that they were colour calculations.
- billfruit 4y agoWhy does Graphics APIs especially 3D, still remain very much low level? I think 3d graphics is still not as ubiquitous as it could be perhaps due to complex and low level APIs.
- pjmlp 4y agoAnyone that wants to explore graphics programming should start with middleware, 20 years ago we would use something like Open Inventor or VTK for that purpose. No need to always start by learning on how to render a triangle or a rotating cube from scratch.
- dahart 4y agoIt’s not just remaining low level, the trend has been moving steadily toward lower level. The primary reason is performance. It’s hard to squeeze the best performance out of the high level APIs. Another reason is because the people who care the most and get involved in the API and standards committees are people who know the APIs and their limitations inside and out, and care deeply about performance; people like game engine render devs, browser developers, OS developers, and hardware developers. And so newcomers and the ease of learning these APIs aren’t well represented. On one hand, there’s a valid argument to be made that people can write wrapper libraries if they want easy-to-use libraries. On the other hand, some of us really miss how easy and fun using SGI’s GL library was before it turned into OpenGL.
- rwbt 4y agoEarlier versions of GL were indeed a lot of fun and easy to get started without much learning curve, but very easy to get into a pickle and blow your foot once the project gets reasonably complex with everything being a state in the context.
- Agentlien 4y agoOpenGL 4 was a huge shift and felt like such an improvement once you got used to it. It was a bit more work to set things up, but it was so much faster and had a lot less messy global state.
- nicopappl 4y agoI've seen this still be recommended in 2021. I personally read it last year and it was definitively helpful. Just excellent if you want to understand what is going on under the hood. Which is necessary if you are writing anything more than a toy graphic program, or understand the output of GPU debugging/profiling tools from Nvidia and AMD.
- monocasa 4y ago(2011)
- ryandrake 4y agoThe title is likely a nod to Jim Blinn's highly influential book (more like a collection of articles), A Trip Down The Graphics Pipeline[1]. That was the first book I read on 3D graphics that helped me to actually intuitively understand fundamental 3D graphics concepts. 1: https://www.amazon.com/Jim-Blinns-Corner-Graphics-Pipeline/dp/1558603875 https://www.amazon.com/Jim-Blinns-Corner-Graphics-Pipeline/d...
- abnercoimbre 4y agoFabian recently (2019) discussed [0] the GPU again, in the context of queue theory. [0] https://guide.handmade-seattle.com/c/2019/talks/lets-talk-about-queues/ https://guide.handmade-seattle.com/c/2019/talks/lets-talk-ab...