What about 100% Rec2020 12-bit? Anyway, I still am unable to find a *OLED panel completely without glare issues on high contrast scenes, even on phones. *OLED technologies are still immature imo, remember that TFT LCD (led and IPS and IPS-like includes) take over 2 decades to become decent...
Yeah not all games handle higher refresh rates very well. Sometimes they simply can't hit the frame rates. Other times they can but since they are simulating on a fixed time step it doesn't help much beyond just making camera movement slightly smoother. Still others simulate on a fixed timestep but will interpolate to get smoother animation at higher frame rates. Suffice it to say it varies a lot!
I beat the final campaign mission on a i5 4570 + 6970 2GB @ 1080p and it stuttered badly once the fighting got thick. I had it on the Low preset I believe. It may have been partially the 2GB VRAM. The game will happily fill even 4GB VRAM from what I've seen.This is also seen with the ps2 emulator where the cpu is always the bottleneck. Last time I checked the ps2 emulator pcsx2 performs somewhat worse with amd gpus regardless of how low you drop the resolution and that is most certainly a cpu bottleneck as ridiculous resolutions high don't impact framerate on modern AMD gpus, and as even an old nvidia/amd cards from could 2010 up the resolution from 1650x1080 to 3000x2000 without seeing much of a drop in framerate in pcsx2.
HOCP did an interesting run with AOTS benchmark, They used Top of the line i7-5960X, 8 Cores and 16 Threads, then decided to handicap it @1.2 GHz, then fully overclock it from 3.5GHz to 4.5GHz and see what happens:
When the CPU is handicapped:
The classic picture returns, we have seen it several times before, NVIDIA rules when the CPU is the bottleneck in DX11, and even in DX12.
AMD suffers massively when the CPU is the bottleneck in DX11, but comes back in full force in DX12.
When the CPU is unlocked:
NVIDIA practically equals out, delivering a slight increase in performance.
AMD is a little faster, but nothing to brag home about.
Thoughts?
== Hardware Configuration ================================================
GPU 0: NVIDIA GeForce GTX 860M
CPU: GenuineIntel
Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz
Physical Cores: 4
Logical Cores: 8
Physical Memory: 8112 MB
Allocatable Memory: 134217727 MB
==========================================================================
Quality Preset: Standard
==========================================================================
Resolution: 1920x1080
Fullscreen: True
Bloom Quality: High
PointLight Quality: High
Glare Quality: Low
Shading Samples: 4 million
Terrain Shading Samples: 8 million
Shadow Quality: Low
Temporal AA Duration: 0
Temporal AA Time Slice: 0
Multisample Anti-Aliasing: 2x
Texture Rank : 1API: DirectX
== Total Avg Results =================================================
Total Time: 60.008465 ms per frame
Avg Framerate: 21.714109 FPS (46.053005 ms)
Weighted Framerate: 21.282160 FPS (46.987713 ms)
Average Batches per frame: 13357.952148 Batches
==========================================================================API: DirectX 12
== Total Avg Results =================================================
Total Time: 60.001305 ms per frame
Avg Framerate: 20.881351 FPS (47.889622 ms)
Weighted Framerate: 20.032330 FPS (49.919308 ms)
CPU frame rate (estimated if not GPU bound): 56.753651 FPS (17.620012 ms)
Percent GPU Bound: 98.123894 %
Driver throughput (Batches per ms): 3520.489746 Batches
Average Batches per frame: 13116.093750 Batches
==========================================================================
Dynamic load balancing is a thing - yes, and it is a hardware feature. But it's nowhere the same, or even remotely comparable to GCN's async execution via the independent command lists dispatched by the ACE units.
But they are unfortunately still referring to their preemption extension for DX11 as "Async Compute" too. On purpose.
Sorry, oversimplification from my side. I only referred to draw and dispatch calls going via the graphics command processor (which also handles the "compute" queues in DX12), and forgot that independent command processor handling CUDA.
It means they don't have a clue what they are talking about and should be ignored.
