Past EED rants


Live leaderboard

Poker leaderboard

Voice of EED

Wednesday 29 October 2003

Halo revisiteth [am]

Despite having all my games on my old drive which is in Guinness 2, various one's of 'em are objecting to not finding the key to the game, presumably in the registry. Sounds a bit screwed up to me. But I thought oh well what the hell and reinstalled it having decimated my den to find the box - it was in the desk draw naturally. So given my new uberness, I let Halo configure everything (basically everything on, everything on high) and played through the first few chapters again.
Now this is hardly news but what a resource hog this game is! Every single ounce of my new rig's horsepower is necessary to play it at 1024x768 with all the gubbins. It can do it, but you can tell it's taking every single last slavering ounce. I mean it looks reet purdy and that but it did make me wonder a bit at just how this thing has been coded that a 3.2 p4 and a radeon 9800pro is sweating heavily. Another thing is that interestingly it doesn't seem to want to apply anti-aliaising when set from the mobo (everything still looked jaggy from time to time and in any event the frame rate was slowing). Finally, the oddest thing about getting some decent horsepower is that the Warthog becomes a damn sight more driveable. On my old system, the Warthog was very prone to drifting around and while the oversteer / countersteer thing is still going on, it's now actually feeling like it's gripping. Gone are the days of endlessly bumping into Convenant walls at high speed. I do love the game but I wish they'd coded it for PC and not Xbox first. Death to ports!

1 comment:

  1. It's a very poor port. It's not doing anything that should remotely slow it down as much as it does.