CBOAT strikes again: Says not to expect 1080p in Xbox One

[Mnementh]

fatslob-:O said:

Mnementh said:

fatslob-:O said:

Mnementh said:

fatslob-:O said:

 

What exactly is the difference ?

I showed you a counter example to your statement about diminishing returns and you give me "30fps is good enough." -_- (epic fail)

Do you even understand the 'diminishing returns' argument? It means, the jump from 480 to 720 is more important than from 720 to 1080 and that is more important than from 1080 to 4K. For framerate it means, trhe jump from 30 to 60 fps is more important than the one from 60 to 120 fps or from 120 to 240 fps.

How do you even start determining which jump is more important when 1080p@30fps is more demanding than 720p@60fps ? How!?

As I said, you didn't even understood the argument. Thanks for proving it.

Simple facts. 1080p is more demanding than 60fps. #Dealwithit

The jump to 1080p is bigger than the jump to 60fps according to the power required.

Like I said earlier just because you don't notice it doesn't mean people with 50+ inch screens won't.

Again, you didn't understood the argument of diminishing returns.

And if rendering in 1080p@30fps or 720p@60fps is using up more hardware-resources is - as often - depending on other circumstances. You're going from the pure pixel-number: 1080p@30fps ~ 62M Pixels/sec and 720p@60fps ~ 55M Pixels / sec. You completely ignore, that every new image (so 30 for 30fps and 60 for 60 fps) needs additional calculations for changes in the scene (you will not look at static images that are rendered again and again). Depending on how much effort is put into the changes in scene, it can be more demanding than the bigger number of pixels for 1080p. So basically it can differ from game to game. And it is not that the difference between 62M and 55M is so big, that the other calculations are without importance.

Anyways, the argument of diminishing returns ISN'T about the question if 1080p or 60 fps needs more power.