Nothing on a website upsets me kid. I think it's hilarious you cows are just pathetic. You've become that meme "leave my Sony alone" whenever someone mentions them, good or bad. It's just an automatic response from cows. Funny to sit back and watch and even better to respond to cows just to watch the reactions. Take you for example.

You couldn't actually say anything about my post without making up something so you resorted to just repeating that I'm upset. It's funny how easily I can get under skin and I didn't even have to put Sony down to do it hahaha.

So what with the 8th cycle? ESRAM is a full duplex memory technology hence it has less mode switch overheads than half duplex DRAMs.

Sorry, it's just a technology type difference. My PC GPUs are also affected by QB's memory access patterns and it's different from Hitman DX12 (AMD Gaming Evolved title).

My speculation...

If QB uses XBO's ESRAM strength with large among of TMU/ROPS read/write memory operations for it's effects layers (shader program could be simple with high memory write operations), it will gimped on PC GPUs without comparable memory bandwidth. 980 Ti has enough memory bandwidth to replicate XBO's ESRAM memory read and write operations. PC GPU's higher FLOPS power can't do anything about very large memory read and write operations bottleneck.

If it falls into the 80's even if it's an 89 it will be considered a flop, you will hear it from everyone everywhere until the end of time.

If you recall from Oxide's BradW statement on eSRAM, the programmer access eSRAM via Xbox One's specific eSRAM APIs. Microsoft updated eSRAM API to make it easier to use.

Xbox One's ESRAM is treated like local video memory with 32 MB size.

Did you remember Tiled Resource API being run NVIDIA GPU that consumed 16 MB of VRAM?

While DX11 layer was thrown in the bin, programmers doesn't have real access to the hardware with current generation consoles i.e. programmer has to go through the GPU driver e.g. for PS4's low level API's case.

At the driver level programming, the programmer can create any multi-threading model just like AMD's driver programmers e.g. bolted Mantle API on AMD's WDDM 1.3 drivers and bypassed DX11 layer, but Xbox One programmers doesn't have AMD's driver access level, hence they are stuck with DX11.X multi-threading model. It took MS DX12 update for XBO to change multi-threading model.

The real metal programming is the access level to create a GPU driver with any multi-threading model.

Furthermore, modern X86 CPUs translates CISC into RISC and programmers doesn't have access to X86's internal RISC instructions i.e. the secect sauce remains with Intel and AMD.

AMD K5 has provided programmer access to it's internal RISC core instruction set i.e. the ability to bypass the X86 decoders to gain additional performance. On PS4's Jaguar CPU, you don't get that access.

BradW has asserted PS4's low level API as last gen API with updates.

lol @ anyone who believes this rubbish.