Slashdot Mirror
Bungie Explains Halo 3's Resolution
For some folks artisitic merit or financial success of Halo 3 isn't what's really important: it's about how many pixels are on the screen. After there were some complaints about the 'truth' of the game's HD nature Bungie posted a missive on their site clarifying the output process for Halo 3's visuals. "Halo 3 uses not one, but two frame buffers - both of which render at 1152x640 pixels. The reason we chose this slightly unorthodox resolution and this very complex use of two buffers is simple enough to see - lighting. We wanted to preserve as much dynamic range as possible - so we use one for the high dynamic range and one for the low dynamic range values. Both are combined to create the finished on screen image. This ability to display a full range of HDR ... gives our scenes ... a steady and smooth frame rate, which in the end was far more important to us than the ability to display a few extra pixels."
Is it a fun game, or not? Debate that question if you must, but skip the minor technical details. It reminds me of the original Xbox's CPU -- some people swore it was a Celeron, some said a P3. I say what ends up being played on the screen is all that really matters.
I was expecting an article about how the game ends, and was prepared to make an epic post about a bunch of dots...
The article stole my joke!
I haven't had a chance to play Halo 3 yet, so I can't say anything about the game as a whole, but I'm glad to see they're more concerned with a steady frame-rate than killer visuals. I'd rather play a game at 320x240 with acceptable FPS (which I did back in the days of the original Unreal when I didn't have an accelerator) than play at 1024x768 at 20. Anything under 30 FPS irritates me to no end.
Those who care about this can wait for the PC version which I'm sure will allow you to pump the resolution to 1600x1200 (or possibly more by editing the .ini files) and zip along in glorious DirectX 10 goodness with their $500 video cards. Of course, by the time it comes out for the PC it will look dated (like Halo 2) and the people with the high-end rigs will be playing something else.
But if you really want it, it's coming.
All the complaints about Halo 3's resolution reminds me of all the "pixel peeping" that goes on when it comes to digital cameras. Everyone gets hung up on tech specs to the point that they stop looking at the image in question.
Halo 3 looks nice, and plays great. That's all that matters to me. I'm certainly willing to forgo some extra pixels in favor of a smoother experience.
Don't get me wrong, I have no problem with what they did, but I wouldn't be saying "extra". They are sacrificing pixels for FPS, not excluding "extra" pixels. I didn't know that 640p was standard and 720p was "extra".
We all know it's nit-picky to count pixels, but I am glad that someone called them on this. this 'NextGen' of consoles was supposed to be the HD-era of console gaming and here we are getting our corners cut secretly!
:)
I remember Peter Moore saying that this generation will also eliminate the jaggies. the anti-aliasing is better in these new consoles but not enough to eliminate aliasing. The marketers can spout lies upon lies before release because no one ever calls them on it later, so I say GOOD JOB and KEEP IT UP!
so they cut corners to get a good frame rate. good grief! if this Gen of consoles were really the HD-era, then every game should be able to do 60fps at 1080p, period. I don't blame Bungie for this though, it's squarely MS's bucket of lies. Also, I am no Sony fanboy - for the PS3's price, it should have no jaggies and every game running 60fps at 1080p as well as my laundry. Guess we'll have to wait until next generation for the NextGen... until then, we're all suckers - albeit having fun with exceptional gameplay
certified elipsis abuser
What really matters is the quality of character and environment designs? Really? I guess you don't own a next generation system then; there's really no point to, ever, when there are so many good (and better) games out there for older systems. But I guess everyone who owns a PS3 or a X360 is just a graphics fanboy.
This issue is not overblown; we're talking about a flagship game on a next-generation HD platform, which isn't even HD. The game essentially runs at 640 and is upscaled because they couldn't figure out a way to get enough FPS to run it smooth at 720.
They have the gall to suggest that it's "practically impossible to discern a difference" (higher resolution makes zero difference?) and then insult people who notice. The "tinfoil hat wearers" are 100% correct in this case -- this is not an HD game. It may be loads of fun, and while it may run in HD, it's upscaled just like the fucking PS2 game on a PS3 without any of the smoothing extras.
The Xbox 360 will display every game at whatever output you choose. On your cousin's elite, he's apparently set it to 1080p. That doesn't mean that games change how they render. It just means that when the framebuffer passes through the on-board scaler chip prior to heading out the the TV, the image is upscaled to 1080p rather than 720p or whatever else you may choose. The two games you mentioned, Gears and Bioshock, actually render internally at 720p (or more precisely, 1280x720, since designations like "720p" don't make sense until the output is heading to a TV). Bungie made the decision to render at 1152x640 using a two-pass method (actually a two-buffer method) to render low-dynamic range and high-dynamic range lighting. The two buffers are then merged for the final picture. There's actually a Powerpoint on Bungie's HDR lighting method floating around the internets somewhere, if you feel like investigating why they did this. Anyway, the end result is mostly the same -- the 360's hardware scaler chip is quite good, and only the OCD pixel counters will ever notice that the game is natively rendered at 640p rather than 720p or 1080p.
History lesson: The graphics engine from Halo 1 was not re-used for Halo 2. It was re-used for Stubbs the Zombie (a game built by an ex-Bungie guy who which licensed the Halo 1 engine). The Halo 2 engine was all new. I haven't heard specifically whether or not the Halo 3 engine was again a new engine or if it was based on the Halo 2 engine, so for now I'll assume the latter.
As for not being able to handle double-buffered 1920x1080 resolutions, there are currently exactly two games on the Xbox 360 that render in 1080p -- Virtua Tennis 3 and some basketball game (NBA Street Homecourt, I think). It's also good to keep in mind that Microsoft has all but said that 720p is the sweet spot for Xbox 360 (HD movies and trailers on the marketplace are all encoded at 720p rather than 1080p, for example). The hardware scaler is capable enough to convert the image to your TV's native resolution without compromising image quality. Obviously an upscaled 1080p image will not be quite as good as a natively-rendered 1080p image, but if you're playing the game rather than counting pixels you're never going to notice.
How many enemies and physics-affected items are on-screen at one time in Gears or Bioshock? How large are the areas? Now compare that to Halo 3, where you can have 30+ enemies on-screen at one time, with hundreds of items strewn about being affected by physics, on maps with draw distances measured in kilometers. Making a game is all about trade-offs. If you're going for small-scale battles in confined areas (think Doom 3), you can optimize for graphics because you'll have more free GPU and CPU time. If you're going for large-scale battles in wide-open areas, you're probably going to sacrifice some visual quality in order to get the gameplay right. You can't do it all, and if you can then it means you weren't ambitious enough.
I'll see your three buffers and raise you an aloe strip!