Just so I'm clear, you're saying in complete seriousness that DICE didn't have the ability to lower the resolution of the PS4 version by nearly 40% give or take and render at 1280x720 and do your magical contrast adjustment because they/PS4 didn't have the hardware to spare the cycles...the same cycles they used to simply increase PS4 version's resolution....and you're serious?
Dropping down to 720p without good scaler hardware to get it back to 1080p would only result in having lots of pretty fx smeared all across the screen. Devs would prefer to avoid that on PS4. You are forgetting that you still need to output at 1080p.
Though I will say your new stance on resolution is a dramatic change from just 6 months ago in which you were pretty adamant in your speculation that Xbox One would have more games running at 1080p than PS4 because display planes.
That speculation is likely still correct, as X1 likely has all games with a native 1080p HUD. MS could have been marketing that but didn't.
Also you should inform Turn 10 about how pointless higher resolutions are. They clearly didn't get the memo. Perhaps they should have lowered Forza to 1280x720 applied the magical display plane magics and add some AA. It would have "popped" more.
I am 100% in favor of lowering Forza's resolution in favor of better AA and more fx. Nothing magic going on with the display planes btw. You can stop with that nonsense any day now Ketto.
And you're right, COD's engine is pretty old. You'd think such an old engine that was developed primarily for Xbox 360 would have no problem running at 1080p on Xbox One given the new system is per your own words remarkably similar to the Xbox 360 and the development environment is almost the same, thus the idea that developers are having a hard time developing for Xbox One because of the eSRAM is FUD.
Development environment isn't almost the same. X1's dev tools are behind schedule, as we've known since the guy from Avalanche told us so months back. Nice try though.
Kinda like how you're ignoring that DF messed up the entire process...
Their capture was perfect. The X1 unit was malfunctioning. Stop spreading FUD you KNOW is bulls***.
...and introduced BTB with the Xbox version due to the fact they set Xbox One to 0-255 and but there was a bug and it gave a 16-235 signal to their capture device that caused clipping that wasn't nor is intended and contrary to your initial assessment had nothing to do with the magical display planes or per frame contrast adjustment?
The color adjustment with the display planes is something that allows for the colors to pop and the contrast to be a higher ratio on X1. DF's comparison was limited by the X1's RGB output for that bugged unit which crushed blacks. It wasn't intended nor did I ever claim the HDMI bug was done intentionally. You're just lying compulsively about what I had said now. Back to the old Ketto I see.
I said this on day 1 of those comparisons. What the HDMI bug did was cut off the RGB spectrum and crush blacks. It didn't magically create a surge of color vibrancy and contrast adjustments by sheer happenstance that miraculously conspired to make the X1 version look better for so many ppl.
What I'm "championing" is the fact that the display planes and their capabilities are unique to X1 and that they allow devs the flexibility to do various things not possible on PS4's scanout engine, which result in contrast/hue adjustments that can make the X1 version of a game look more vibrant and sharper, even with lower native resolution. We see that in BF4 and AC4 as demonstrative examples. You are fighting a losing battle. You are arguing against your own eyes because ya don't like what the reality in front of them is suggesting.
Anyone who thinks crushed blacks/BTB is a good thing is an idiot unarguably.
The X1 doesn't crush blacks. You are reading too much of GAF's FUD. Those pics are captures from the Game DVR, not the actual game itself. It's not doing that in other games so clearly it's not some mysterious hardware level issue doing that to all games. It's likely more to do with Game DVR having messed up settings to accommodate smaller upload files. Nobody noticed this issue with KI until they saw Game DVR footage/screens.
You mean a solution you assume costs cycles on PS4 based on your limited knowledge?
No, based on what your own whitepaper says. If it's in the GPU, it costs cycles. On X1 that isn't the case.
As for the PC you mean other than the fact that OSX since like forever and Windows since DX10 can create multiple planes in their graphics API?
...which is in software.
You assume because individual software creates their own planes that PC OSes are incapable of doing such on their own. Flimsy logic. Not even sure what the point of mentioning culling is for at all.
Wat? I never suggested anything like that. said they are done via software which eats into processing power in the main processors.
UVD is part of the VCE block that resides on the GPU. It's the most logical place to put it since it requires GPU bandwidth to function, where else would it be done exactly?
I never claimed it was a bad place for it. I said it's not external to the GPU and as such eats into GPU cycles when used for post fx.
