BioShock Widescreen Slices Vertical View
by Nick Breckon, Aug 21, 2007 11:03am PDTIn a rapidly-expanding thread on the 2K Games forum, reports are
coming in that 2K Boston and Australia's just-released shooter BioShock (PC, X360) uses a cropping method for its widescreen display, cutting down on the vertical view rather than expanding the horizontal width (illustrated left). The problem apparently exists for both the PC and Xbox 360 versions, and cannot be fixed with an edit of the game's FOV (field of view) setting.
The issue took forum goers by surprise, as 2K Boston lead programmer Chris Kline assured fans last May that BioShock's widescreen view would show more, rather than less. "The game will render in full 16:9 aspect ratio, with no letterboxing unless your resolution is not true 16:9," Kline said in a thread on the 2K forums. "You will see more in widescreen. We use a different projection matrix; there is no squashing or stretching of the image involved." Shacknews can confirm that the problem exists in the PC demo of BioShock, and has contacted 2K Games for comment.
Report: Frostbite 3 games to be 'optimized exclusively' for AMD cards
Candy Crush dev exploring IPO
Castle of Illusion preview: more than a repaint
Steel Diver sequel is Nintendo's first free-to-play game
Why Pikmin hasn't made the jump to handheld






Comments
http://images.pikapuff.com/games/bioshockws.png
Thread Truncated. Click to see all 60 replies.
The gaming Internet detectives with possibly too much time on their hands are out in force though. So far the most compulsive-obsessive thing I've even seen is someone making the bizarrely esoteric complaint that the water isn't "double-sided." Whatever that means. However, they were quite upset about it, lol.
But really, none of this is worth starting a progrom over, or anything other than the mildest of criticism. Not a single review (that I've read so far) has even mentioned it and I bet it's because none of those reviewers noticed. For the average person who will buy and play this game, I'm going to bet it's a complete non-issue. (Of course, it should still be fixed, I guess.)
You must be logged in to post.