A month later I actually got round to having the console collected, and off it went on a jaunt to Germany. Procrastination is seemingly still rife for me when it comes to some things, despite having a job that should supposedly make me get stuff done.

Still, just over a week later and it was returned to me – complete with a month’s free XBL gold and a sheet explaining that not only had they replaced the motherboard (which was expected given the RROD) but also the DVD drive, which was unexpected. This has seemingly caused my Xbox to get quieter, as the DVD drive was never particularly subtle and the fans make one hell of a noise, and I’m certainly not going to complain about that.

All in all, excepting the fact that some shoddy design has been involved and has lead to it failing, I’m quite happy with how the process has worked. I’d have probably had it back working within 10 days had I been more efficient with getting it sent off, and Microsoft have been quite good with the communications as to the repair status. Of course, I know people who have had multiple failures, and I’m going to be wary of that happening again – but touch wood I’ll avoid that problem.

All sensible enough so far, until you find out that the only way to get the libraries that it needs from the server is to download the whole server and install that using their application for this (which takes two passes at the same command to do that for some reason). This pulls about 780MB of stuff down onto the machine, including all of the HL2MP maps, textures, models and sounds (apparently it needs some of these in case you want to run a pure server without people having their own custom sounds and whatnot). All in all the libraries that I wanted were no more than 35MB of this, so it was a little bit frustrating.

You then get to the build process, which first compiles a util (vcpm) to read the vc++ project file and use that to make a makefile for the mod itself. This is all well and good and all done in one fell swoop with a simple ‘make’. Unfortunately if, for some reason, you want to do a clean build of the mod – ‘make clean’ won’t help you. That just cleans up vcpm, leaving the server objects there waiting for you to do it manually.

The whole compile process was also very slow, although that could be my machine (it is 4-5 years old now) and produces one hell of a binary. I’m pretty sure that this is down to it linking statically with a lot of libraries, including some of the c/c++ ones, although I have yet to verify this or follow the guide on the wiki that suggests you can cut 5MB off the binary with some magic. Perhaps in future builds I’ll look at getting that done, but for now I’m just happy that it compiled.

Having done this with gcc-4.1 (4.2 just plain doesn’t work, but then isn’t claimed to on the wiki) I found that crashes occured for other people, hardly good. So I dug out gcc-3.4 and had a bash with that, only to find that errors were soon the scourge of my life again, some of them seemingly in the Valve code – great. Fortunately a bit of digging around in the documentation turns out that it’s a known thing where gcc-3.4 won’t inline functions unless you give it a -O option. This fixed it was clean sailing and I had a nice compiled version.

Unfortunately this version also segfaulted, so it was off to the debug build and to see what was going on with it. This proved rather useless, as the engine produces a stack trace without any symbols (even after the mod is compiled with them) so I’ll need to have a rummage around what’s going on at some stage, probably something to do with my system configuration compared to that of the server. Nothing is ever simple eh?

The hype around the launch, including articles about it heading towards the fastest selling game ever (eclipsing last year’s new record breaker – Halo 3) lead to a lot of people pre-ordering, queues to get the game at midnight and people suggesting that there’d be no chance in hell of getting hold of a copy without a pre-order. Of course, this was all nonsense as I happily walked into a shop at lunchtime on Tuesday and picked up a copy with no problems whatsoever.

Eventually I arrived home and threw the disc into the Xbox, and away I went to Liberty City. For those who aren’t aware, Liberty City is modelled on New York; in a not-very-loose way. The names have been changed, but there’s no mistaking the Statue of Happiness for the Statue of Liberty, or Star Junction for Times Square (especially with the replica of one of the offices at work on it). This resemblance makes the game very interesting, especially having only visited New York within the past couple of months.

So far I haven’t managed to explore too much within the single player, as work has got in the way of playing, but what I have encountered has been good fun. Compared to Vice City, the last GTA game I played, the vehicle handling is much better, and the AI is also very good (with people getting out of their cars and running away if you point a gun at them). Another great new feature is the mobile phone, allowing you to call up your contacts to arrange things, prank call the police, and most crucially – get to the multiplayer.

GTA IV is the first of the GTA games to support multiplayer natively, although previous versions have seen the Multi Theft Auto mods add this to it, and despite it being a new venture for them it seems to work remarkably well. There are a number of different game modes, with different ones being suited to different numbers of players, and my only criticism would be that at times the areas seem a little too large when playing with 8 people.

All in all, GTA IV is one of the best games I’ve played, and with the mass of achievements available and stats being tracked left right and centre, I’m sure that I’ll be playing it for a while yet.