|
Badassbab said: They are not using MSAA though. But I get you're point, it's a situation much like the 360 where resolution was dropped to avoid tiling and fit all the rendering targets in the 10MB EDRAM thus taking advantage of the high bandwidth afforded by it. |
I know... I just used his example 
To make a comparison a 1080p framebuffer with good MSAA needs close to 70MB of RAM... MS knows that so for that they inserted 4x DMEs in Xbone to try to move fast data between DDR3 and eSRAM but the bad part is that you need to chance your code to do that with a good performance because you still have the slow DRR3 to work.
At the end the dev will compromisse what they need fair (like most important for their game) to get a good performance.
I think we have these scenario on Xbone:
- 1080p@30fps with bad AA
- 900p@60fps with bad AA
- 900p@30fps with good AA
- 720p@60fps with good AA
- Few exceptions (1080p@60fps, 900p@60fps with good AA, etc)... most of them when the learn how to deal with eSRAM and MS optimize the devtools to make it use less complicated
