Language Selection

English French German Italian Portuguese Spanish

Quake. Fleshed out. Up to date. Brutal.

Filed under
Gaming

To say that a new single-player Quake has been a long time coming is something of an understatement. It's been positively agonising, with nearly eight years skipping past since id's legendary Quake II took PC gaming to new heights.

In the intervening years we've had Arena, of course, but the focus there was very much keeping multiplayer gamers happy and showing off a brand new engine. In terms of keeping the lonesome players satisfied, there was unfinished business to attend to, and the completion of the Doom III engine allowed id, along with Raven, to fill that gaping void.

The results are thrilling. Predictably thrilling, but thrilling all the same. You probably already know what to expect by now, and Todd Hollenshead and Tim Willits' half-hour demonstration delivered a knockout punch to the senses. It's in no way even trying to be original. It's playing to the crowds, it has everything you could want from a gib-filled, all-action Quake game and brings it bang up to date - and frankly we're quite happy about that.

Slightly confusingly in number terms, IV picks up directly from where II ends, and the game wastes no time at all in getting straight into the action. This is no Doom III. There's no brooding tension. It immediately struck us as a brutal fusion of linear Call Of Duty wargame intensity set against the frenzied brown-tinged Quake backdrop that we all know and love.

You play as "one certified badass" Matthew Kane, and after a brief but beautiful intro sequence that depicts a sea of floating debris, body parts and detritus drifting through space, it cuts to an ongoing war with the Strogg on the planet's surface, with seemingly the whole base under heavy aerial attack, with huge, terrifying explosions going off everywhere. Missile launchers fight back desperately, but the onslaught of huge ships swooping overhead lends an oppressive sense of panic to get the hell to somewhere safer as soon as possible. Not that anything left standing won't be blown to smithereens soon anyway...

As you'd expect these days, the first thing to do is get some instructions from the nearest NPC you come across, in this case Sgt Morris. Unlike Doom III there's no messing about building up tension or anything; it's straight into the action, darting into the shattered remains of a dark, dingy, smouldering brown-hued metallic base and shooting any enemy resistance you come across. Which is to say a lot.

The familiar metallic sounds of the weapons takes you immediately back to the late 90s, and a wave of nostalgia crashes over you. Quake is back. Bring it on. But this time it's not just a one man army. Expect intelligent buddy AI finding appropriate cover points and carefully ducking in and out of the rusty industrial setting to pick off the advancing enemies. And what's this? A torch mounted on the end of your gun? Clearly someone out there listened to the barrage of complaints post-Doom III...

"If you haven't played Quake 2 it doesn't matter," Hollenshead insists. "Players unfamiliar will still be able to understand what's going on. It's the usual Earth struggles against the Strogg yadda. But if you have played the originals you'll recognise the tweaks. It's a totally separate story. Now you actually have a name - Matthew Kane. We wanted to give Kane an independent personality. All members of your squad have a personality as well," he adds. Quake. Fleshed out. Up to date. Brutal.

Full Preview.

More in Tux Machines

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)