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."

25 of 181 comments (clear)

  1. BFD by Eponymous+Crowbar · · Score: 4, Insightful

    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.

    1. Re:BFD by onecheapgeek · · Score: 4, Funny

      Less making sense, more complaining please.

    2. Re:BFD by p0tat03 · · Score: 5, Informative

      Er... less ignorance, more knowledge plz. These frame buffers are on TOP of the double (or maybe even triple) buffering that is already done from frame-swapping. The whole idea is that 32-bit screen buffers do not have enough range to properly account for HDR lighting (i.e. that nice effect where your eyes take time to adjust after coming out of a dark tunnel, and also the real way to do light blooms). So in essence what they're doing is two 32-bit buffers to simulate a very large 64-bit buffer, where each pixel has 64 bits of range. In total they would need to have at least 4 of these to account for the double buffering.

      In an ideal world I should just be able to tell the machine to give me 64-bit color, but our hardware isn't quite there yet (almost).

    3. Re:BFD by bn557 · · Score: 2, Informative

      Halo 3 : 5 Hours @ $12 an hour = $60
      GO-Carts: $5 per ride, 10 Minutes Per Ride, $30 an hour, 2 hours = $60

      Did said person enjoy 5 hours of halo 3 more than they'd have enjoyed 2 hours on a go-cart?

      I've been using go-carts as my baseline for whether something is worth it or not for a few years now.

      --
      Humans are slow, innaccurate, and brilliant; computers are fast, acurrate, and dumb; together they are unbeatable
    4. Re:BFD by TheQuantumShift · · Score: 2, Interesting
      Since I can't playback HD content with it, I'm going to have to say Celeron. Man those things suck. The entire collective of Intel must have been drunk throughout the nineties. I can't believe they still exist, worthless pieces of trash that they are.

      cat /proc/cpuinfo

      processor : 0
      vendor_id : GenuineIntel
      cpu family : 15
      model : 4
      model name : Intel(R) Celeron(R) CPU 2.53GHz
      stepping : 1
      cpu MHz : 2533.610
      cache size : 256 KB
      fdiv_bug : no
      hlt_bug : no
      f00f_bug : no
      coma_bug : no
      fpu : yes
      fpu_exception : yes
      cpuid level : 5
      wp : yes
      flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pni monitor ds_cpl tm2 cid cx16 xtpr
      bogomips : 5070.99
      clflush size : 64

      God damn it...

      --

      Shift happens. Fire it up.
  2. Ending? by dws90 · · Score: 5, Funny

    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!

  3. Fun should come before visuals, but... by TriezGamer · · Score: 4, Insightful

    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.

    1. Re:Fun should come before visuals, but... by p0tat03 · · Score: 4, Informative

      I can attest that Halo 3 runs smooth as butter, with consistently high framerates that haven't dipped even once in frenetic battle. It certainly feels smoother than graphical powerhouses like Gears of War, and in a multiplayer game framerate is king above all else.

      I also have to add that Halo 3 is amongst the most beautiful games I've ever played. They use this incredible lighting model (I suspect it's some offshoot of ambient occlusion) that simulates global illumination remarkably well. This is a nice change from the shiny "oh look we have bumpmaps! look!" feel that most other "next-gen" games have. Everything looks natural - shiny things shiny, dull things dull, and everything in between. Really have to give kudos to their coders and artists for making it all come together so well.

  4. Wait for the PC version... by rtechie · · Score: 5, Insightful

    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.

    1. Re:Wait for the PC version... by Kalriath · · Score: 2, Informative

      Actually, you're wrong. Xbox Live is a multiplatform service - it's available on Vista, and Xbox 360. Yeah, the name's a misnomer.

      The PC version (as with Halo 2) is generally able to do local multiplayer, and Xbox Live (renamed just Live). Internet play is out of the question (I guess you could VPN up some games, or actually collect lists of IP addresses, though).

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  5. Pixel Peeping Video Game Style by ScotchForBreakfast · · Score: 5, Insightful

    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.

  6. Resolution by Wilson_6500 · · Score: 2, Insightful

    I think it happened right around the time that HDTV became available, but at some point resolution--previously a technical term--somehow became a buzzword related to quality. It's gotten to the point where I can't stand hearing people talk about 640p or 1080i or whatever, because it just comes off as marketing spew and e-penis-waving.

  7. "extra pixels."? by PoderOmega · · Score: 3, Informative

    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".

  8. All these Microsoft apologists... by Ang31us · · Score: 2, Insightful

    Gears of War and BioShock are both displayed at a native 1920 x 1080 in progressive scan on my cousin's 360 Elite. The lighting in both games is amazing, as are the visuals, and the gameplay.

    The real problem is Halo's graphics engine, which has been too demanding of the graphics card/processor since Halo 1. They're not going to admit that their graphics engine is slow or that the 360's graphics card can't crunch through double-bufferred 1080p using an engine that is maintained at Microsoft.

    It goes to show that third-party developers have a better handle on getting the most out of the 360's PC hardware than Microsoft.

    1. Re:All these Microsoft apologists... by Osty · · Score: 5, Informative

      Gears of War and BioShock are both displayed at a native 1920 x 1080 in progressive scan on my cousin's 360 Elite. The lighting in both games is amazing, as are the visuals, and the gameplay.

      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.

      The real problem is Halo's graphics engine, which has been too demanding of the graphics card/processor since Halo 1. They're not going to admit that their graphics engine is slow or that the 360's graphics card can't crunch through double-bufferred 1080p using an engine that is maintained at Microsoft.

      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.

      It goes to show that third-party developers have a better handle on getting the most out of the 360's PC hardware than Microsoft.

      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.

    2. Re:All these Microsoft apologists... by Gulthek · · Score: 2, Insightful

      It's not just "lighting" that Bungie is talking about. But high dynamic range rendering. Notice how in Halo 3 when you are coming out of a dark tunnel the sunlit areas are blindingly bright? That's just a bit of the HDRR magic at work. Bioshock and Gears of War, both great, beautiful games, don't have this. It's a tradeoff to be sure, but as a amateur photographer I have to give Bungie the edge here. I don't notice the loss of pixels (I didn't even know about it until this article) but I sure as hell notice the lighting's range.

  9. but NextGen was supposed to be the HD era! by captain_cthulhu · · Score: 3, Insightful

    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
    1. Re:but NextGen was supposed to be the HD era! by NeutronCowboy · · Score: 2, Insightful

      I'm guessing that you started gaming with the XBox and PS2? Otherwise you'd have experienced first-hand that the statement "it's next gen, so it should x at 60 FPS!" is as old as gaming in general. It used to be that things should be 60 FPS at 256 simultaneous colors or GTFO (no getoffmylawn jokes, please). I guess it's now 60 FPS at 1080p. This complaint is based on the complete lack of understanding how graphics technology and how game development works.

      1. Just because hardware can output things at resolution x, color-depth y and z objects on screen doesn't mean that it'll draw things at a particular frequency. Maxing out a particular aspect of an architecture generally means that there's a cost that has to be paid elsewhere. There is no free 60FPS.

      2. Developers will always focus on shiny pictures. Most PR material is still sent out as still-pictures, and most people judge beauty by still frames. As a result, developers tend to optimize for prettyness rather than smoothness.

      Yeah, I know. The original poster is little more than an HD troll, and should be ignored. This complaint is still my major pet peeve anytime a new generation rolls around - invariably, tons of people will complain 6 months after launch that it doesn't do x, y, or z at 60 FPS. Then they blame it on developers, manufacturers or PR people, when the problem is simply that they don't understand the topic they're talking about.

      Yeah, there is a problem with marketing promising the moon and delivering a shiny pebble. But if you don't know this by the time you see your second commercial.... that's your problem, and not the problem of the developers.

      Rant off.

      --
      Those who can, do. Those who can't, sue.
  10. Re:So... by Bhodi · · Score: 4, Interesting

    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.

  11. Re:well i know how to make a better game now! by dryueh · · Score: 5, Funny

    I'll see your three buffers and raise you an aloe strip!

  12. Karts, eh? by tepples · · Score: 3, Funny

    I've been using go-carts as my baseline for whether something is worth it or not for a few years now. How fast did you blow through Mario Kart DS?
  13. To see what you're sniping by tepples · · Score: 2

    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. If you're a sniper, you have to see what you're sniping, and high resolution helps you spot targets from farther away. It's like having normal vision vs. uncorrected myopia.
  14. Re:So... by Kalriath · · Score: 2, Informative

    Actually, you're STILL wrong. If a game chooses to render at native 1080p, it can render that. The fact that the first Xbox 360 game to support it wasn't released until February this year is not relevant. If your console has the October 2006 software update, it can natively output true 1080p. NOT upscaled. Note that only if your model was built after July 2007 do you get an HDMI port. Bastards.

    In fact, what you'd find if you did read any information released around that time, is that the 360 will upscale anything rendered in less than 1080p to it, and will render 1080p content as is (i.e. no upscaling).

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  15. 720p Guarantee by Enderandrew · · Score: 2, Insightful

    Didn't Microsoft DEMAND that all games must meet 720p to qualify as a 360 title?

    Didn't they guarantee that they were ushering in the HD era?

    I guess that didn't apply to their own internal titles.

    Bioshock looks better all around, has far more detail, oh, and runs natively at 720p without any problems. Why can't Halo 3? I don't get it.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  16. Fuck Upscaling by Ren.Tamek · · Score: 2, Insightful

    This is actually a rampant problem on the xbox 360. I used to own one, and one of the first things I noticed about the machine was that images which should be crisp on your display were actually blurry around the edges. This odd phenomenon occurs everywhere, from the 360 dashboard, to the game menus and fmv's, to the in game graphics themselves. It seemed likely to me that this was because the machine is rendering things at a low resolution, and they trying to upscale by 20-30% in both x and y directions, which causes distortions in the image because it isn't a sensible division, like 100%. Every single game i've played has this problem, except settlers of catarn. If you are reading this and you have a 360, go download the demo of this off live arcade and try it out. Notice how crisp and clean the visuals are? The game is rendered from the get go in your native resolution, nwhich results in a sharp image with no distortion. You also never see any stretching, because if you're using an unorthodox screen shape (I used my monitior, which is 5-4) it will use your exact resolution as the buffer size. This post it entitled 'fuck upscaling,' because the fuzzy blur you get from every game the machine plays gives me a headache after about 2 hours play. If they want to reduce the resolution then fine, but just output whatever you render, don't upscale. I had to sell my 360, and one of the reasons was because of badly defined visuals. It should be the first thing people consider after high frame rate, in my opinion.

    --
    "If you want a vision of the future, Winston, imagine a boot stamping on a human face forever." - George Orwell, 1984