A few months ago I opened up a service called SteamCoin that lets you buy Steam games, packs and DLC for Bitcoin. Over the past couple of months I’ve put a bunch of updates live on the site, including support for packs and DLC, as well as a back-end update that ensures that all Steam game prices are accurately reflected on SteamCoin.
Unlike other services out there that let you buy Steam games for Bitcoin, SteamCoin.com doesn’t require you to remember app IDs, nor do you need to download any browser plugins or other programs. These features make SteamCoin.com the leader in Steam gift services for Bitcoin.
I’ve written up several new posts over at the Project Broadside blog, focusing on Tim’s work on the model for the Imperial Crewman (the concept for which he finished based on the original front view by Eric) as well as the first two posts in my series on integrating NVIDIA’s APEX SDK.
Work has been going along steadily on my main development project, Project Broadside. A team-based multiplayer FPS set in the skies, Broadside pits two teams against eachother in physics based airship combat. Captain the ship while your team mans the cannons, or fight it out as a crewman against the enemy team using pistol, sword or cannon. The first team to destroy the enemy ship and send it plummeting from the heavens wins! More info about Broadside here.
And now, the part everyone always waits for: art!
The final pistol model changed quite a bit from this initial concept.
As you can see, the evolution of the pistol from concept to model introduced a lot of design changes. The original design was much less traditional.
For more development art shots of Broadside, check here.
For US readers, you are no doubt celebrating Thanksgiving today with your families. For those of you that (for some reason) decide to visit my very modest blog on this holiday, Happy Thanksgiving.
To my international readers (if any) Happy Consolation Pseudo-Holiday. Or something.
This post really brought to light something for me, which is that I don’t really understand the readership of this blog. When I checked the stats today, and noticed there were 31 views across the blog, I was somewhat perplexed.
What I *do* know is that it seems my OpenVG/SVG related posts are easily the most popular, which isn’t a surprise to me. There is very little information about how to properly get SVGs loaded and rendered fast enough for interactive framerates (needed for games or other simulations involving rapidly changing path data). It took me about a month, spread over a couple of years to really find the best ways of doing these things, and there was almost no information, and what there was is very outdated.
Anyway, Happy Turkey-Day to those of you celebrating, and happy reading to the rest.
This was originally going to be a post on my Facebook page, but it became a little too long. It’s been a while since I posted on the blog here, and I’ve mostly been working on things other than the SVG Game Engine. Although I’ve back burnered that for now, I will definitely revisit it when I stabilize my job situation somewhat. I’ve been mostly working on contract projects with some tinkering on the side for the past few months.
I’ve started working on a Windows Phone 7 game to hone my C# skills and I found a loader class for the map files that Tiled (a FOSS 2d tile map editor) spits out.
I decided to use the “Object Layers” feature of Tiled to place the fortresses on my map. I go into the code and look for how to access the objects loaded in…oh, it doesn’t handle them. Shit.
So I go in and look at the map file (it’s just an XML file) and figure out the structure and start expanding the loader to load in Object Layers and objects, and their properties (which are key=value pairs, essentially). I write it all up, I’m basically ready to test it. As a courtesy to the author and other people using the class, I post on the blog saying I’ll go ahead and release my changes to incorporate the new feature.
But wait…what’s this? The post has a link *in the first sentence* to someone that already fixed the loader to have the features I just wrote. And *that* post has a link to a CodePlex page where someone took the loader and properly fixed it up into a XNA Content Pipeline library. Goddamnit.
Now I am going off to completely rejigger my project to use the proper lib, which is all set up nice and neat the right way.