I've been studying mostly, but to relax I've been developing a library for graphics manipulation - to produce something like below in a .NET 3.5 environment. :D
And yes, that is from a screenshot. :D
Photo: 00 Raiser Box!
After more than a month of thinking about it, and allowing it to run out of stock all over the place, I've decided to finally buy a 1/100 00 Raiser kit. I've yet to open it - since I bought it just so that when I do want to buy and build it (which is after exams) - I actually have a kit to buy. It's been awfully difficult to find at the right price - but I've finally bought it.
You can guess what this means: more photos in May or June once I'm done building it - of course, I don't paint, so it's bound to look like crap (although it does mean it'll only take me one afternoon, rather than one month). :D
Photo: My Calculators!
Well, obviously, considering my course, I obviously use calculators. Here are the three I currently use the most. (besides my computer and my PDA)
cfgt's Lua Interpreter v0.01! - Updated!
Here's an awesome release of one of the components from my upcoming game! It's a Lua interpreter! It doesn't work perfectly yet. I've added a command so that you can print out variable contents (since lua can't write out to the console normally using the print command): it's called consolewrite - and all you have to do to use it is type 'consolewrite(variablename)' and it'll print out the contents of the variable no problem. It's a great piece of software - very minimalist user interface (I love command line programs). You'll need .NET Framework 3.5 (grab it here if you don't have it installed) installed on your computer to run it.
Have fun playing with it! I've hidden a command in it (it's real easy to find, trust me - so you don't have to worry about spending hours trying to decipher a crazy puzzle - that's for next year).
A few things you should know before trying it out:
If you've got a Lua script that's purely Lua and nothing else, it should run perfectly using the dofile command (I've made sure it works.)
I believe the program shouldn't crash just because you're typing gibberish into it. It may be rudimentary - but it should have pretty OK error handling.
To exit the program, type 'exit' or 'quit' and the command prompt and the program will close itself. It doesn't leave behind any log files and the error messages are generally unhelpful - although that's probably something I'll work on.
If you find any bugs in this very early alpha version, report it!
Update - I made a small mistake during compiling which may cause problems for some people. Not sure if it'll fix anything, but I've updated the EXE anyway. I've called the new version 0.02 although it's only a hotfix.
Red Alert 3: Uprising Short (P)Review!
Well, not too long ago, RA3 Uprising was released on digital download! Woo-hoo! I managed to try it out and play a couple of missions. (OK, that's a lie, I finished the relatively short campaign.) I believe most of the meat in the game is in the Commander's Challenge, which I'm not going to play until later.
The campaign is simple and short - 13 missions total. Then again, the Tale of Yuriko doesn't really feel like missions, so there are 10 new campaign missions to play through. I'd say a lot of them are standard RA3 fare - start off, fight your way through to gain a foothold, whack everything else in sight. I can't say much about how good they are, but they're a good way to get a look at the new (and most certainly IMBA) units like the Mortar Cycle, Pacifier and Giga-Fortress.
The Tale of Yuriko is interesting, putting the game into a dungeon crawler-esque mode where you have 4 abilities to use against your enemies. The story is ultimately pointless, but the campaign is fun nevertheless. What else could be better than whacking everything with a single unit? It even comes with boss battles! (Well, sort of.)
I haven't played the Commander's Challenge, where I believe most of Uprising's content is actually at. I guess that'll have to wait until after my exams. :D