Ad: Manage updates with the Download App

f.e.a.r

preGame 55: Shadows of the Damned; F.E.A.R. 3

This week's game demos are intended for mature audiences only. Viewer discretion is advised.

With Mark back in the preGame lineup, we're set to demo two very dark and creepy titles on today's show. First up is Shadows of the Damned, the collective offspring of an all-star Japanese development team. Talent from such series as Resident Evil, Silent Hill, and No More Heroes have collaborated to form a truly unique and remarkably odd tale of a man who must travel through hell to save his girlfriend.

Next up is the third title in the F.E.A.R. series. The tone in F.E.A.R. 3 is creepier than ever, but the game's iconic mechanics--like distinctive slow-motion effects--are still well in tact. Players will be greeted (or terrified) by Alma over and over again as her dark presence still runs rampant through the universe.… Read more

Larrabee performance--beyond the sound bite

Hello, Slashdot.

In a story on PC Pro, Nvidia architect John Montrym (whose name was incorrectly spelled "Mottram") quoted my recent blog post on Larrabee as concluding that "the 'large' Larrabee in 2010 will have roughly the same performance as a 2006 GPU from Nvidia or ATI."

Alas, this isn't really what I said or meant.

What I actually described as equating to "the performance of a 2006-vintage...graphics chip" was a performance standard defined by Intel itself--running the game F.E.A.R. at 60 fps in 1,600 x 1,200-pixel resolution with four-sample antialiasing.

Intel used this figure for some comparisons of rendering performance. If Larrabee ran at 1GHz, for example, Intel's figures show that… Read more

E3 2007/Update: Does performance drop in 'F.E.A.R.' point to larger PC gaming problem?

UPDATE: Well, we just met with Monolith, developers of the original F.E.A.R. and we don't have much new info to provide. We were told that Monolith heard from Logitech about the issue and Vista, but that Monolith never heard back when it asked Logitech whether the glitch happened in Windows XP. Even if it had, it would still be up to the hardware vendors to dig up the problem and point to a specific place in the F.E.A.R. code. The developer theorized that it could be due to something going with DirectInput, the … Read more