This looks like it’s going to be a lot of fun – can’t wait! =D

Relatedly, wearing my hat of cynicism +5 and staring into a magic eight-ball, I predict a re-badged Armagetron Advanced getting ported to every mobile OS in existence… which to be perfectly honest isn’t a bad thing: light-cycles ftw!

No related posts.

Click here to view the embedded video.

Apparently it’s only about four hours of gameplay, but it’s one of those games that when you finish it you’ll be happy to sit down and discuss what it all meant with your mates… Hmm, very tempted to pick it up (1200 points, 117MB) – and it seems there’s a demo available too.

Might just check that out right now

Related posts:

1. New XBox 360 Motion Capture System
2. Shadow Complex

And if they don’t, then there’s always IDDQD… =P

Well played, CollegeHumour peeps! Found via bitmob.

No related posts.

Good on’ em! =D

Related posts:

1. How To: Use a Wired XBox 360 controller in Linux
2. Game Controller Hanging Ornaments

Oh, man – This game is going to break my head… Can’t wait =D

No related posts.

Intermahresting…

Related posts:

1. Pixels by Patrick Jean
2. World History with the Pope
3. 99 16-Bit Problems…

… because sometimes you deserve one. Especially after some particularly rage-inducing boss battles!

Get from: http://www.supermandolini.com/ – they’ve got heaps of nice stuff

Related posts:

1. The Gaming Revolution Will Be Televised

Run At Any Resolution

By default, Q3 gives you a rather poor list of available resolutions – to see what’s available, just hit the tilde key (i.e. ` – backtick, just left of the “1″ key) and type: \modelist and you’ll see something like this:

Well, we can do better than that – just enter the following couple of lines (changing the width and height to any valid, known resolution) and you’re set! Personally, I use these:

\r_mode = -1
\r_customwidth 1920
\r_customheight 1080
\vid_restart

And presto – full resolution! Be aware than if change any options in the Options | System part of Q3 it’ll override your custom resolution, so you’ll need to set it back by repeating the above lines.

You might see some people talking about changing \r_customaspect (which by default simply has the value 1), but I didn’t really see it doing a great deal. But if you want to experiment yourself, your aspect ratio is just your horizontal resolution divided by your vertical resolution, so for me it’d be 1920 divided by 1080, which gives 1.7777778, so I might put it just as 1.7 or 1.8 – but really, I didn’t see much if any difference when I’ve messed with it, apart from a possible slowdown when I actually used 1.77777778, which could have just been my perception of things… I did a quick side-by-side comparison with different r_customaspect values and did a \vid_restart between each one:

Record and Play Demos

To record demos (i.e. record you playing against your mates or randoms) you need two commands which you can happily issue from the command window (i.e. stab tilda and type ‘em):

• record – records a demo
• stoprecord – you guessed it, stops the recording…

However, typing these at the prompt can be a pain, so why not just bind them to some keys? You can do this easily enough by opening the file ~/.q3a/baseq3/q3config.cfg and adding the following lines somewhere in it (then saving it, obv!):

bind F5 "record"
bind F6 "stoprecord"

Now, all you need to do is stab F5 to start recording a game and F6 to stop the recording. You might see some moaning about needing g_syncronousclients 1 set, but you can safely ignore it as it’s a legacy requirement that doesn’t even exist in recent versions of Q3.

Your demo will be recorded with the filename demoXXXX.dm_68, where XXXX is a number starting at 0000 and going upwards with each demo recorded. It’ll be saved in the folder ~/.q3a/baseq3/demos/, but when you go to play it from the Demos part of the main menu – it won’t play. Instead, it’ll come up with the error “Couldn’t open demos/demo0000.dm_68″ or the like:

The fix/workaround for this is to go to the location of your demos (~/.q3a/baseq3/demos/) and RENAME THE FILE TO ALL CAPITALS! No, really. I guess this is a really old error which has reared it’s ugly head because Windows systems aren’t case sensitive (so myfile.txt, MYFILE.TXT and MyFiLe.TxT are all seen as the same thing to Windows) whereas Linux takes case sensitivity into account… I’m tempted to go digging in the code and apply an upcase statement to the demo filename retrieval mechanism…

Wrap-up

I guess those are the main two things I’ve been concerned about getting working properly, besides getting the thing to work in the first place, so I guess I’ll leave the VOIP stuff until I’ve got some more time… Got any comments, suggestions, improvements? Sling ‘em in the comments! Cheers!

Related posts:

1. How-To: Fix Missing Bots in ioquake3 in Linux

^1Error: file bots/default_c.c, line 2: file charsh” not found
^3Warning: couldn’t find skill 1 in bots/default_c.c
^1Error: file bots/default_c.c, line 2: file charsh” not found
^1Error: file bots/default_c.c, line 2: file charsh” not found
^1Error: file bots/default_c.c, line 2: file charsh” not found
^3Warning: couldn’t load any skill from bots/default_c.c
^1Error: file bots/kyonshi_c.c, line 2: file charsh” not found
^3Warning: couldn’t find skill 1 in bots/kyonshi_c.c

Apparently it’s only been an issue with the 64-bit version – but even the older version I had was showing the same problem (which I don’t quite get how) – anyways, I recompiled ioquake3 and it’s all fixed up – and thought that if anyone else was up against the same issue it might be useful to know how to fix it quickly and easily.

1.) Get the source

For this we need to have subversion installed to download the source trunk, if you do – great!, if not, run this first:

sudo apt-get install subversion

With subversion in place, from the command line create a folder with mkdir ioqcode or the like, go into it with cd ioqcode and then grab the source with:

svn co svn://svn.icculus.org/quake3/trunk ioquake3

2.) Build it

Go into the downloaded trunk code with cd ioquake3 and then build that bad-boy with this complex command:

make

Geez, linux is tech To be fair, you’ll need the sdl-dev packages installed (libsdl1.2-dev) and of course build-essential – I didn’t have to get any extra packages, it just built.

3.) Pick a place to stick it

Because I’m the only user of my laptop, I have a folder called Games in my home directory, so I just created ~/Games/ioquake3 and then copied all the files from the build/release-linux-x86_64 sub-folder (created when you successfully built ioquake using that complex make command – your folder won’t have _64 on the end if you built it on a 32-bit system) to ~/Games/ioquake3/, and then copied the pak0 to pak8.pk3 files from my original Windows install of Quake III into the baseq3 subfolder of the ioquake3 folder.

4.) Frag on!

Launch ioquake3.x86_64 and get your game on =D

Click here to view the embedded video.

I have absolutely no idea how they’ve got motion blur on the game (unless it’s applied post-game to the captured footage) – but it looks AWESOME! Want! If you know how they did it please feel free to smack me with the clue-stick in the comments! Cheers! =D

Update: It turns out they’re using the Excessive Plus mod in the video (which works fine with ioquake), still no clue about the motion blur though…

Another Update: Turns out this issue exists in the 64-bit version of OpenArena as well as ioquake3. I rebuilt openarena using the 0.81 version from the svn here – but still no dice with getting bots to spawn. Apparently the 32-bit version of OpenArena is unaffected.

Related posts:

1. How-To: IOQuake3 Linux Tips n’ Tricks
2. How To: Compile and Use the Dolphin Gamecube/Wii Emulator in Linux
3. How To: Fix Broken Sound in ScummVM under Linux

Absolutely loved the first one – bring on the second. Plasma Cutter FTW! =D

No related posts.