infinityBCRT said:
It's a first party game. lol. Who are they paying?
I'm a Programmer so I have a good idea of how it would work. Unless their code is really bad and not modular (unlikely) it wouldn't be too hard to adapt Reach's rendering to Halo 3
I realize it's not realistic that they will do it but it would be nice to have all Halo games looking sharp, as they will inevitably do a Halo 2 anniversary (they've already hinted at it) and probably won't do a Halo 3 anniversary as the assets are good enough.
But you're not a programmer that worked on Halo 3.
And they have to pay the programmers and certification department employees that make sure the TU wouldn't set the 360 userbase aflame.
In theory, you can patch whatever you want on a 360 game. But you have to weight the cost/benefit and the implications of touching the HDR/rendering portion of the engine, as that code is pretty important (since it's literally present everywhere in the game). You want to make that kind of code solid, a known factor, and not a moving target. You'd have to make sure Campaign, Forge, the lobby system, and Theater mode do not get affected. You'd have to change the screenshot system to accomodate the change in rendering. You'd have to weigh pleasing a minority of people that actually cared that they were only getting 640 vertical pixels and not 720, keeping in mind the vast amount of people playing on SDTV and are getting their "full" resolution already. These people would get angry that their screenshots look "worse" after the patch.
On a big game like that, you can't be Programming Rock Star and just change a few lines of code. You need to weight the risks, benefits, and costs and plan for the future if adding the feature would lose room for potential future and more important bug fixes. When patching a 360 title you have to choose your battles.