News Archive

Apr 1, 2016 Posted some short stories

Had a few short stories laying around, so I figured I might as well post them. They’re under the About section.

Mar 24, 2016 Generating Quality Content Quickly

I’ve been experimenting with ways to generate quality content quickly.

Delusion, the game series I’m working towards, is based on the idea of releasing weekly episodes like a TV show. I want to maintain the pace of producing one episode per month – I am roughly estimating having three seasons per year, where each season is four or five episodes.

In order to do that, I need to be able to produce content quickly.

Attempt 1: Blender

My first attempt was to model everything in 3D, using Blender. Here’s the start of a level:

I think I spent roughly 3 hours modeling the desk and computer. It would probably take me another 6 hours to texture map it. That means for 1 day of effort, I would be roughly 2% done with the level.

In order to fit this technique into 24 days of labor, I would need to use a lot of canned content, cut my levels in half, and basically do nothing else except model and texture the entire time.

So I gave up on 3D modeling the levels. Not fast enough.

Attempt 2: Pixel Art with Filtering

My second thought was: maybe I could do pixel art? Lots of indie developers use pixel art.

I spent some time mucking around with pixels, and thought the only real way I could get away with it was if I produced really low resolution pixel art. The lower the resolution, the faster the development time.

So maybe I could cheat my way to higher resolution?

I created a filter for upscaling pixel art in real-time, just to see what sort of quality I would be looking at.

Here is someone else’s art running through my filter:

Not bad… I guess.

Here’s my art running through the filter:

Boy, that looks like crap 😓.

Attempt 3: Vector Art

It seemed weird to be spending time manipulating pixels to get certain shapes out of the filtering process. Can’t I just input the shapes directly?

So, now I am attempting vector art.

But I had a little idea at the same time.

Sink

I’ve been working on another programming language I call Sink (because making programming languages is a time sink 😛).

I know I need a simple language in order to do scripting inside the games – I could use Lua, but I don’t really like Lua all that much. While working on Kong (my old language, that I eventually ditched after 7 months of development), I had an idea for a much smaller language.

Sink is extremely simple. The first full Kong compiler was roughly 9,000 lines of code. Sink’s compiler is 2,000 lines of code.

Kong has 12 types (void, null, bool, num, str, blob, code, list, map, handle, task, worker). Sink has 4 types (nil, num, str, list).

I took 5 months to create the Kong compiler. I took about 4 days to create the Sink compiler.

Sink + Vector Art

Since Sink is done, I thought it would be cool to make a vector art program with Sink embedded inside of it:

There are some reasons why I really like this idea:

1. I can write programs that create art. Nearly all other techniques involve manual creation of art from start to finish.
2. Programs are powerful. I can store colors in variables, calculate geometry, create functions, etc. This (hopefully) translates to speed of creating content.
3. Text programs are easy to store, diff, track, change, etc. Binary image formats – not so much.
4. Vector art has infinite resolution.

The editor in the screenshot above is actually pretty cool too – I can point to things in the image and push a button to have the coordinates pasted into the script on the right side. I can highlight any color and use a color picker to change the values in the script.

So I’m going to be using this for a while and see if I can produce content quickly with it.

If not, I don’t know what the hell I’ll do 🙃.

Mar 7, 2016 Movement to Pure C

I had to make a difficult decision about 3 weeks ago. I gave myself 6 months, from July 2015 to the New Year, to make my programming language, Kong.

I worked on it the entire time, through several major refactors, and had a pretty solid product by January – but it wasn’t complete. I spent another month trying to fill the holes, and had a cube rendering.

The problem was the speed.

It just isn’t fast enough for game development.

So, all wasn’t lost: I knew of a lot of ways I could speed it up. I could rework the virtual machine bytecode, to make it more efficient for execution; I could write a partial JITer; I could write a Kong-to-C transpiler, or an LLVM backend, etc.

But I was out of time. My next deadline for having a game developed is only a few months away, and my first experimental changes to Kong would take another 2 months. And then, what if it still wasn’t fast enough? I would be way over schedule without any games.

So I ditched it.

One good thing about writing the VM in C is that I became really comfortable with C. I used to program in C++ a long time ago, and I had spent most of December and January working on the VM in C99, which is a pretty nice language, all things considered. It’s much better than C89, and is widely supported.

What sucks is that I’m basically throwing away 6 months of work, and giving up on the dream of creating a programming language – at least, for now.

I didn’t make the decision lightly, but I also didn’t really have a choice. I could let Kong consume all of my time, and never ship a game, or I could let it go, and focus on game development on a proven platform, C.

So, starting around February 15th 2016, I chucked the majority of my codebase, and started over, using pure C.

The bad news is that I’m behind schedule (and if I had skipped Kong completely, I would be ridiculously ahead of schedule!). But I’m not that far behind, and I’m making up ground pretty quickly.

And instead of meditating on how to improve the Kong codebase, and how to speed up compilation, and how to speed up the garbage collector, or speed up the VM execution: my focus is now (correctly!) on how to make a game.

I’ve learned Blender, and have a pretty cool setup so far. I’ve written around 8,500 lines of code the past 3 weeks, and have the start of an animation engine:

What’s nice too is that I can now post a lot of screenshots of my progress, since I’m working on graphical things, and not compilers 😀.

Follow me on Twitter @velipso to see random screenshots as I do actual game development 😀.