2k to patch PS3 BioShock
October 15th, 2008 @ 16:45

According to this 2K forum post made by 2K community manager Elizabeth Tobey, the publisher’s going to patch the PS3 version og BioShock to get rid of some unwanted graphical quirks.
The game’s out on Friday.
From the post, two issues will be dealt with:
Big Daddy Bouncer and Elite Bouncer textures appeared pixelated
Fix for an issue where large blocky pixels would show up whenever viewing the Bouncer and Elite Bouncer variants of the Big Daddy.
White bars
Fix for an issue where white/discolored bars would show up at the right and bottom sides of the screen during the plane crash / water scene at the beginning of the game.
More through there, including comparison shots between the PS3 and 360 versions.
Posted in: 2K, Action, Hot, PS3, Shooter
Tags: bioshock, patch
You can follow any responses to this entry through the RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.
October 15th, 2008 at 4:49 pm
Oh good - comparison pictures! Time to go home, I think.
October 15th, 2008 at 5:25 pm
As suspected, the resolution, lighting and AA all leave a lot to be desired. Bio on PS3 has a flattened look that is very unappealing. Fer shame… How many teams were working on this again?
Mind you still a great game, just visually lesser than it’s siblings.
October 15th, 2008 at 5:26 pm
This article needs to be patched to remove the typos.
Clearly, this post-release article patching shows what a terrible platform Wordpress is for writing with. I may update this post with a comparison between Wordpress and Notepad.
That is all.
October 15th, 2008 at 5:34 pm
use firefox with a dictionary addon!
October 15th, 2008 at 11:23 pm
I’m going to agree with Shatner again, it seems.
If first day patching makes any game particularly shit, then it makes every game particularly shit. If anyone cares to claim that the PS3 BioShock release is seriously lessened by this, that’s fine, but I wonder if they’d also be willing to claim that the same is true of Fable II, too?