fenster

how basically every rendering tutorial just skips over drawing text on screen, which is super useful for debugging. For drawing single pixel lines, this page has everything on Bresenham: http://members.chello.at/easyfilter/bresenham.html For 2d rasterization, here's an example of 3 common approaches: https://www.mathematik.uni-marburg.de/~thormae/lectures/grap... Scanline rasterization tought me a lot about traversing polygons, I recommend trying it even if you end up preferi g a different method. Sean Barrett has a good overview: https://nothings.org/gamedev/rasterize/ Side note: analytical antialising is fast, but you should be carefull with treating alpha as coverage, the analytic approaches tell you how much of a pixel is covered, not which parts are. For 3d rasterization Scratchapixel is good: https://www.scratchapixel.com/lessons/3d-basic-rendering/ras... Someone mentioned the Pikuma course which is also great, though it skips over some of the finer details such as fixed point rasterizing. For good measure here's some classic demoscene effects for fun: https://seancode.com/demofx/ Anyway, this is just scratching the surface, being progressively able to draw more and more types of primitives is a lot of fun.

ou vastly lower your expectations, and target say, 320x240 at 8bit colour, you can happily have a naïve implementation that works just fine (Don't believe me? Quote: > Having this we can now draw complex polygons and would probably need a “flood fill” algorithm. Typically it is implemented using a queue of pixels to check and paint, but we can use recursion, as long as the filled area remains small enough to not overflow the stack ^ This is the very definition of a naive implementation, and https://github.com/zserge/fenster/blob/e71d493fa6d544243dd60... settings one pixel at a time, is too. Delightfully charming as it might be to write your own functions that set one pixel at a time, it's a joke, really, if you expect to do anything serious)