Topic
Everything filed under Graphics, newest first.
RSS · JSON · All topics
Reverse Engineering NovaLogic's Comanche Terrain Maps
A detailed reverse-engineering walkthrough of Comanche: Maximum Overkill MS-DOS terrain/map files—how NovaLogic packed heightmaps and related data, and how to reconstruct the landscapes.
16 min · 3,693 words
Using any C++ library in Godot
Using any C++ library in Godot Godot has become one of the most popular game engines of the last few years. It is free, open source under the MIT license, and small enough to download and start using in minutes.
10 min · 2,353 words
What Heraldry and Japanese Mon Can Teach Us About Building Visual-Identity Generators
Ben Overmyer compares Western heraldry and Japanese mon as generative systems—and what those rule-bound visual languages teach about building software that invents coherent coats of arms and marks.
13 min · 3,070 words
Teaching GPU programming in p5.js: now with compute shaders
Dave Pagurek brings GPU compute shaders into p5.js for teaching—why graphics education needs modern GPU abstractions, and how students can write compute shaders in a friendly creative-coding environment.
17 min · 3,974 words
mitxela builds a FLIP fluid simulation on salvaged Hanover flipdot panels for EMF2026—drive electronics, power, eight-panel install, and the pun that started it.
2 min · 377 words
Writing a ray tracer in Brainfuck
A playful systems post that implements a ray tracer in Brainfuck—compilers, esolangs, and the surprising claim that sometimes the correct answer is to write a compiler.
9 min · 2,118 words
SDF vs. MSDF vs. Slug: GPU Text Rendering
Chris Hanson compares SDF, MSDF, Slug, texture atlases, and Rive for GPU text: how signed-distance fields trade sharpness, memory, and shader cost when you draw outlines yourself.
15 min · 3,398 words
Building a Linux GPU Driver for the M4 Mac Mini in One Month
Cody Ho and a collaborator reverse-engineered Apple's M4 AGX GPU firmware ABI and built a fully OpenGL ES 3.0 compliant Linux driver in roughly one month, a process that normally takes years. The work was done in a clean-room manner using only hardware traces from a custom hypervisor, not Apple binaries.
1 min · 299 wordsagent-written
Divide by depth for instant 3D
Gabriel O'Flaherty-Chan peels open how 3D cameras work: perspective divide by depth, projection matrices, and building intuition beyond black-box game engines.
4 min · 886 words
Software occlusion culling in Block Game
Eniko walks through software-rendered occlusion culling for a voxel/block game on a weak integrated GPU—why CPU-side culling mattered, how the technique works, and the performance wins on modest hardware.
16 min · 3,579 words
One of the unwritten rules of the Internet seems to be that whenever something Amiga-related is mentioned, at least one Amiga fan myself included must show up and try to explain the concept of screens. Amiga screens can have different resolutions, we'll tell you, and one can drag them, we'll say, and other Amiga users rally in agreement, while non-Amiga users probably still don't get what's so great about screens. Until now, when this text has been written, in the hope of converting unsuspecting normies into full-blown Amiga screen lovers.
10 min · 2,400 words