weekends are for leisure

When I started working on this project nearly a year ago, the frame rate rarely stayed consistent as the player moved around the world. The engine was simply allocating and discarding too much memory, resulting in frequent pauses in gameplay as the interpreter ran garbage collection. As I re-wrote more and more of the game engine, I came to understand exactly which types of objects and arrays I needed to allocate, where I could cut down on allocations, and where I might use an “object pool” to stash allocated objects for re-use. The old engine used typedarray-pool, but I’ve decided to create my own object-pool.

Continue reading

I’ve finally rounded out some more features that I felt were necessary for a somewhat-compelling demo.

Open Google Chrome then click here to explore and build: http://voxeling.greaterscope.com

Recent updates include:

• Updated character model to more closely match the one from voxel-engine
• Added skins from voxel-engine and other projects
• Refactorings and optimizations
• Simple water animation (of sorts)
• Made jumping less jarring (implemented the Skyrim float)
• Pause physics until user clicks the world for the first time. This prevents user from falling through the world before it has a chance to load.
• Trees have leaves now

Continue reading

Floating in the diaper tank. Space leprechaun fade away.

Continue reading

The voxeling engine now supports textures with transparent cutouts. Thus, leaves!

Will write about what I’ve learned along the way later. Check the voxeling project on github to see what it took, or to play around with it on your own.

Continue reading

The ISS has been housing astronauts continuously for the past fifteen years (press release here).

That’s cause for a celebration!

Continue reading

One of Ian’s best game reviews ever. Laughed my ass off!

Continue reading

Five months ago I started messing around with voxel-engine and it has thoroughly re-kindled my love for measuring and optimizing code. You can see a demo of my project in my previous video post. However, I’ve taken the three.js-based engine as far as it can go. I want to increase the draw distance, want world chunks to load and draw faster, to make changes to the physics engine and reign-in the garbage collection pauses (caused by excessive memory allocation). So I took the plunge, and I’m now 1.5 months into a full re-write of the voxel-engine code. The good news is that I finally have something to show (the image above).

Continue reading

Wanted to show some of the new features I’ve added to the voxel game: maps and streamlined mouse/keyboard input handling!

The revamped input handling also includes support for game controllers, but it’s not complete yet, so don’t tell anyone.

Continue reading

I’ve been writing about an in-browser voxel game project of mine over at voxeling.tumblr.com. The game – if it can actually be called that (probably not) – is built on a JavaScript game engine for building minecraft-like environments. If you want to try it out, contact me.

The following screenshot shows a lava flow created in-game using lava and obsidian textures. Credit for the textures and lava flow goes to phionabrie. (fullsize):

Continue reading

I finally got voxeling to work from my linode server! And just in time for Tuesday night’s Meetup.

The night summed up in a phrase: “Thanks for digging!”

At one point we had four players simultaneously walking around, creating blocks, digging holes under each other. There remains a glitch where some players were invisible to the others, but other than that, things went quite well. Player position updates and world changes were relayed over the internet without any serious issues … until the node.js server app crashed due to an unexpected client disconnection. Gotta fix that issue eventually.

Continue reading