A mysterious fact about linear transformations is that some of them, namely nonuniform scalings and shears, make a puzzling distinction between “plain” vectors and normal vectors. When we transform “plain” vectors with a matrix, we’re required to transform the normals with—for some reason—the inverse transpose of that matrix. How are we to understand this?

It takes only a bit of algebra to show that using the inverse transpose ensures that transformed normals will remain perpendicular to the tangent planes they define. That’s fine as far as it goes, but it misses a deeper and more interesting story about the geometry behind this—which I’ll explore over the next few articles.

Read more...

Here’s a cute bit of math I figured out recently. It probably doesn’t have much practical application, at least not for graphics programmers, but I thought it was fun and wanted to share it.

First of all, everyone knows about rotations: they make things go in circles! More formally, given a plane to rotate in and a center point, rotations of any angle will preserve circles in the same plane and with the same center. By “preserve circles”, I mean that the rotation will send every point on the circle to somewhere on the same circle. The individual points move, but the set of points comprising the circle is invariant under rotation.

Read more...

In two previous articles, I’ve explored some unusual methods of texture mapping—beyond the conventional approach of linearly interpolating UV coordinates across triangles. This post is a sort of continuation-in-spirit of that work, but I’m no longer focusing specifically on quadrilaterals.

A problem that often afflicts texture mapping on smooth, curvy models (such as characters) is distortion: in some regions, the texture may appear overly squashed, stretched, or sheared on the 3D model. A related but distinct problem is that of different regions of the model having different texel density, due to varying scale in the UV mapping. I wanted to explore these issues mathematically. Are there ways to create texture mappings that have low distortion by construction?

Ultimately, I didn’t come to an altogether satisfying resolution of this question, but I encountered plenty of interesting math along the way and I want to share some of it. This post will be on the more esoteric, less immediately-applicable side—but I hope you’ll find the topic intriguing nonetheless.

Read more...

It’s been quite a while since the first entry in this series! I apologize for the long delay—at the time, I’d intended to write at least one more entry, but I couldn’t get the math to work and lost interest. However, I recently had occasion to revisit this topic, and this time was able to make progress.

In this article, I’ll cover bilinear interpolation on quadrilaterals. Unlike the projective interpolation covered in Part 1, this method will allow us to maintain regular UV spacing along all four of the quad’s edges, regardless of its shape; but we’ll see that to achieve this, we’ll have to accept a different kind of distortion to the texture.

Read more...

Ｕｎｉｃｏｄｅ! 🅤🅝🅘🅒🅞🅓🅔‽ 🇺‌🇳‌🇮‌🇨‌🇴‌🇩‌🇪! 😄 The very name strikes fear and awe into the hearts of programmers worldwide. We all know we ought to “support Unicode” in our software (whatever that means—like using wchar_t for all the strings, right?). But Unicode can be abstruse, and diving into the thousand-page Unicode Standard plus its dozens of supplementary annexes, reports, and notes can be more than a little intimidating. I don’t blame programmers for still finding the whole thing mysterious, even 30 years after Unicode’s inception.

A few months ago, I got interested in Unicode and decided to spend some time learning more about it in detail. In this article, I’ll give an introduction to it from a programmer’s point of view.

Read more...

When the same word is used to mean slightly different things, there’s always a chance of creating confusion—and the word “shader” is a bit overloaded in computer graphics. Between engineers, artists, and DCC tools’ terminology, there are at least four different meanings of “shader” out there.

Read more...

One difficulty with GPU hardware tessellation is the complexity of programming it. Tessellation offers a number of modes and options; it’s hard to remember which things do what, and how all the pieces fit together. I use tessellation just infrequently enough that I’ve always completely forgotten this stuff since the last time I used it, and I’m getting sick of looking it up and/or figuring it out by trial and error every time. So here’s a quick-reference post for how it all works!

Read more...

View on GitHub

Welcome back, readers! You may have noticed that the site looks a bit different now. Over the last few weeks I’ve redesigned the theme, making it more modern and mobile-friendly, and also converted it from Wordpress to a static site generator, which should make it faster in general as well as hopefully more resilient to the occasional slashdotting. 😅

I ended up building my own little static site generator in Python, and I’ve put it up on GitHub in case it’s helpful as a starting point for anyone else’s efforts.

Read more...

Download (2.5 MB)

In June 2016, game developer Sophie Houlden held a month-long game jam inspired by Star Trek. Although my initial plan was to actually make a game, after one thing and another I ended up radically de-scoping and I decided instead to re-arrange the Next Generation theme music, as an exercise in orchestral writing. Working from a piano score and my nostalgia for the original, I turned out this take on the classic.

The show’s original version (one of them—there are a few slightly different variants used in different seasons) can be found on YouTube here.

Download (12 MB)

Like many people, my first foray into game development was modding. In the early 2000s I spent a lot of time making maps for Doom, and later Half-Life. But I hadn’t touched it for about ten years, until this winter, when Eevee posted a series of blog articles on Doom mapping, and I was inspired to take up the editor again. This map was the result.

I spent about a month on this (my initial plan turned out to take a lot longer to execute than I thought—big surprise), and I’m pretty happy with the result. It was neat to come back to Doom after this time and see how my perspective had changed. The tools available today are a lot better than what I remember, and I’m way smarter about level design than I was ten years ago. Still, by the end of making this, I was starting to get frustrated with Doom’s limitations, and I’m definitely all mapped out for awhile.

I’ve packaged up the map with a copy of the ZDoom engine and the Freedoom asset pack (since the original Doom textures, sprites, sounds, etc. are all under copyright and can’t be redistributed). If you have a copy of Doom 2, drop your doom2.wad file in the directory and use that; otherwise, you can play it with the Freedoom assets.