T w e n t y S i d e d

One of the major goals of this project is to see if we can furnish a space station. That is, we want to load in some models and arrange them around the level in ways that make sense.

My first thought is to build some crude models, just to prove that my idea is sound. I don’t want to stop programming so I can re-learn 3D modeling. I haven’t done any serious modeling since the turn of the century, and all the technology has changed since then. So I figure I’ll just make a few basic cubes to represent the various objects in terms of size.

That wasn’t a good idea. It just didn’t give me the sense of whether or not the system is working. I could see it was probably working in theory, but that wasn’t a very satisfying way to conclude this exercise. I don’t have any screenshots of this experiment, which is fine since the screenshots would be roughly useless.

So let’s skip that misadventure and jump ahead to the point where I finally open up Blender and decide to make some models.

Continue reading ⟩⟩ “Project Bug Hunt #6: Model Madness”

Shamus Young is a programmer, an author, and nearly a composer. He works on this site full time. If you'd like to support him, you can do so via Patreon or PayPal.

Last time I talked about what an atlas texture is, why we need them, and how I use them. The important thing is that I’m not hand-crafting the atlas every time I add a new texture. I have some code that does all of this for me. It reads all the images in a particular folder, sorts them-large-to-small for efficient packing, and then generates my atlas texture. It also stores the location of each texture within the atlas. So later when I’m busy generating walls and level geometry, I can say:

cell = LibraryAtlas.Lookup (“textureName”);

That gives me the location of the sub-texture within the atlas. Now I can plot uv coords as if I was using a standalone texture and not worry about the atlas at all. That’s immensely important when you’re building polygons with code and you want to keep things as simple as possible.

Last time I shared my atlas texture. Actually, that was just one fourth of the atlas. Sort of? The point is, I don’t just have one atlas texture. I have four.

Continue reading ⟩⟩ “Project Bug Hunt #5: More About the Atlas”

Shamus Young is a programmer, an author, and nearly a composer. He works on this site full time. If you'd like to support him, you can do so via Patreon or PayPal.

I’m afraid this one got away from me. I wanted to talk about code reuse. So I decided to talk about the atlas texture I’m using. But then I needed to explain what that is and why we need it. And then I got dragged into asides about how I use my atlas and some theory about how texture addressing works.  

So my two-paragraph aside is now an entire entry of information that’s not directly connected to the problem of generating 3D levels. I could send this mess back for another round of editing and restructuring, but then I’d have nothing to post this week and you would be sad.

I have made this longer than usual because I have not had time to make it shorter. – Blaise Pascal

I don’t know if this entry will hold up, but I think we can all at least agree that Blaise Pascal is one of the coolest names ever. My anglo-centric take on his first name is that it ought to be pronounced “Blaze”. Blaze Pascal! That’s practically a superhero name.

Anyway, I’m now making this overlong post even longer by complaining about the length. Let’s just Get On With It before I make everything worse.

Continue reading ⟩⟩ “Project Bug Hunt #4: Atlas”

Shamus Young is a programmer, an author, and nearly a composer. He works on this site full time. If you'd like to support him, you can do so via Patreon or PayPal.