Project Line Counter is super handy, but it hasn't been updated since Visual Studio 2005. Here's how to get it to work in Visual Studio 2010…

So I drink Coke when I work. That's about as relevent as this post is going to get, but this is so mindboggling I had to share.

I have a case of 24 Coke in my 70 degree crawlspace that nobody had touched in a week. There was no visible damage on the case. It had a 12-pack of Coke Zero on top of it. I'd taken four cans out of it so far. When I went to get a couple more cans out of it on the weekend, I found the case was full of Coke - not in cans. Damn.

Digging the cans out of the Coke-soaked case, I found this can which blew my mind. The pictures are exactly as I found it (other than I rinsed the remaining Coke out of it.) Check out the ends of the vertical rip, those are horizontal tears. This Coke exploded. Yet the top and bottom aren't bulged. I never would have imagined a Coke could burst like this.

I'm glad nobody was holding it when this happened.



You can click on the images for the full-resolution images.

Last week I attended the first Canadian Games Conference. Having attended GDC Canada the last two years, I was a little unsure what exactly to expect, but to my surprise, the conference was very good, although a little small. So if you didn't attend this year, you should reconsider for next year.

Last night I was working off my regular development machine, when to my surprise, I discovered that one of my tools wouldn't run. It just stopped with a mysterious Windows error message. Some googling around I discovered that one of the libraries I use was looking for a specific version of a Visual Studio runtime DLL which is part of a security fix for Visual Studio 2005. Hmm.

I got shirts made - which turns out to be surprisingly easy. These are the mockups:

This week I'm working on a tool to generate a navigation mesh for my world. The world is currently made up of about 200,000,000 triangles. For each of those triangles I need to evaluate if they are walkable, and then combine those triangles into larger convex polygons, removing any unneeded vertices so that the navmesh is smaller and more efficient for searching.

The example I have been looking at builds its navmesh by comparing every triangle in the world with every other triangle in the world to see if they are connected. Thats 40,000,000,000,000,000 comparisons. And you end up with tens of millions of triangles in your navmesh. Even on a quad-core hyperthreaded Core i7, I need something a little more efficient.

In a few days I'll have been working on this game for 18 months. Longer if you consider previous projects that are now incorporated into this one.

That's a long time. Longer than any other project I've done. In the past when I reached the year mark, I wanted that software out the door. And it went.

At 18 months, this one isn't ready yet. And that's hard.

Persistence, determination, confidence, they all fail at some point. This takes faith.

A few years ago I built a credit card processing system. It used 2048 bit RSA encryption to encrypt the credit card data on the customer's own computer, then stored the encrypted information on our server until the order could be processed. Then that encrypted data was transferred via floppy to a PC which was never connected to the internet where the decryption key was stored so the order could be processed. That system was pretty secure against outside breaches.

I had to shut it down when the credit card PCI data security standard came out because the cost of security auditing the software plus annual third party security audits for the rest of the company combined with the potential for $500,000+ fines levied by the credit card companies in the event of a security breach made it totally not worth the hassle and financial risk.

So I feel a lot of irony today with Sony saying this about their 77 million PSN accounts:

we believe that an unauthorized person has obtained the following information that you provided: name, address (city, state, zip), country, email address, birthdate, PlayStation Network/Qriocity password and login, and handle/PSN online ID ... profile data, including purchase history and billing address (city, state, zip) ... PlayStation Network/Qriocity password security answers ... your credit card number (excluding security code) and expiration date may have been obtained.

Wow. All that information. Apparently none of it encrypted. Too bad they're big enough that those PCI fines won't really hurt. I expect their security auditor will get hung out to dry.

This week I built the other major component of my game's user interface: my own HTTP 1.1 server. The server is now built into the client to serve up web pages to my Chrome UI. At some point I might also put it into my servers so remote monitoring tools can check for server status via a simple web page request (a server I worked on previously dumped an XML file of status variables any time a browser did an HTTP GET request to it.)