|
|
 |
| [Jul 30, 2012, 11:24 am ET] - Share - Viewing Comments |
Post Comment
Enter the details of the comment
you'd like to post in the boxes below and click the button at
the bottom of the form.
 |
| 11. |
Re: Morning Consolidation |
Jul 30, 2012, 17:28 |
Beamer |
|
|
jdreyer wrote on Jul 30, 2012, 17:22:
Beamer wrote on Jul 30, 2012, 12:21:
avianflu wrote on Jul 30, 2012, 12:17:
if it can actually run at 60 frames per second on all games made for it? That would be interesting.
That's a weird thing, though. No hardware can guarantee that. My computer can't. Your computer can't. So either you have a policy that forces it, and limits creativity, or you accept that not everything can run at 60 fps. Some game genres don't need to, so it's better to push the limits of the machine than do 60 fps.
Is that a requirement for the system? I think they had a 30 fps or 24 fps requirement for 360.
That is a more sensible requirement, as anything under is objectively unplayable, but even then it's not something easy to force. Any good developer will try to push the limits of a system, and pushed limits will absolutely fall below 60fps at times (and it's a fine tradeoff in many circumstances.)
As others said, it would be nice if it forced 1080p, but even then... did Halo 3 look significantly worse than any other game because of its resolution? I'd argue no, even on a giant TV. I'd be ok with the system dropping to lower resolutions in favor of more fluid action for certain games. (Halo 3, for the record, looked worse due to its morbidly low poly count. But decent lighting and particle effects seemed to have made plenty of people miss that.)
Maybe it's just me, but I couldn't tell Halo 3 was a lesser resolution than any other Xbox game. I think the decision to render lower and upscale in favor of more fluid graphics was fine for that game. I think some games that go to 30fps are fine, too. There are other games that do one or the other and look pitiful for it. I blame the dev, not the console. Bad developers that can't properly prioritize. |
|
|
|
|
|
|
|
| |
|
|
.. ..
Copyright © 1996-2013 Stephen Heaslip. All rights reserved.
All trademarks are properties of their respective owners.
Twitter 
