We see only one instance where only one thread hits a max 100% usage and it is there for a split second moment. Actually, DX11 shows higher CPU usage than DX12, and DX12 with DXR set to Ultra is less CPU intensive than DX12 alone. The fact of the matter is that DXR/NVIDIA Ray Tracing is GPU limited even at 1080p. So you can say what you want to say, but we did the research, and while BFV is surely CPU intensive for a 4C/8C CPU (and remember ours is overclocked to 5GHz across all cores), a six or eight core CPU is not in any way needed at the clocks we are running. Now using a 2080 Ti, we are likely moving to a 9600K, because yes, as the GPU scales higher, it certainly puts you in a situation where you are more likely to be CPU limited, but that has not been the case with the 2070 or 2080, but the 2080 is certainly pushing it.On my machine I do notice higher CPU usage when I made the switch over to DX12 along with more memory being used. BFV uses all 12 of my threads, so perhaps there is something to the 7700K not having enough threads to push DX12 properly?
We have other articles that already fully cover that in other games. We will not be doubling or tripling the workload and time it takes to get these done in order to accomplish that.Thanks [H].
On the 2080ti review, can we also get 980ti and 1080ti's added to just the "No DXR" Graphs? So to see the performance increases without regard to DXR, when the games' patch level, os's directx, rigs CPU, etc are all the same?
Is this game worth it to buy? I may try out Dx 11 and than 12 with some Vega’s and compare to a 1080 Ti. Wondering if a solely game engine issue or NVidia issue or both.I switched back today and can confirm I do see higher CPU useage in DX11, by 5-8%. Ive been on DX12 for awhile now, and my move to DX12 followed the first big patch, so perhaps that swayed things...looks like I was wrong at any rate! VRAM and RAM usage is lower under DX11 still though I notice. Frametimes are a little better and more consistent under DX11 on the AMD side as well.
Its too bad they didnt make more of a push for DX12 optimizations earlier on. With ray tracing being unfortunately tacked on at the end of the game development, that probably would have provided more incentive if introduced earlier. Perhaps we will see a focus on DX12 performance gains in future updates, given the 2 shot mandatory performance penalty that ray tracing and DX12 is currently handing out to the green team in order to implement the star feature of Turing.
Looking forward to future game updates and perhaps driver updates to try and fix this sorry situation, and appreciate you guys looking into all these things. Enjoy the 9700K looks to be a great Gaming CPU these days, but I look forward to the days when AAA games can use all of your Threadripper! few years to go id imagine...
Is this game worth it to buy? I may try out Dx 11 and than 12 with some Vega’s and compare to a 1080 Ti. Wondering if a solely game engine issue or NVidia issue or both.
Even with the cpu not indicating 100%, you can have thread dependencies with one thread waiting for results from another and if they are on the same core (too few independent cores) causes stalls and contention with the cache on the same core. Anyways would be very interesting if the larger size caches of Ryzen shows an advantage here as well.
Interesting review, I am not seeing more than 10% drop with DX 12 in their tests for either Nvidia or AMD. Interesting is the Vega 64 is almost as fast as a 2080 at 1080p, only 3fps slower, Ultra settings with the Vega 56 and 2070 the same. Did not expect that.
2080 Ti also appeared to do decently at 4K with DXR as well. Absolutely gorgeous 4K video.
Interesting is the Vega 64 is almost as fast as a 2080 at 1080p, only 3fps slower
Is this game worth it to buy?
That titan purchase is making more sense now!
I am somehow frame limited to 145 fps no matter what I do
Will do, the game in the options has the highest option of 200 fps but it makes no difference between 144 fps setting and 200 fps, it stops at 145 fps for me and obvious limiting. That is with and without FreeSync on . Tried different driver options, no VSync, no FreeSync etc. - same. This game supports FreeeSync 2 as in HDR and FreeSync at the same time, HDR look really good and gives much depth to the rendering and one of the smoothness games I've ever played with FreeSync. Since using the game version of the Pro Drivers - they are not as current as the new AMD Adrenalin drivers. I could load the new drivers but it usually messes up my ability to switch back to the Pro driver easily. This game engine can use a lot of threads even without DXR and how it uses the CPU seems to be different, it is like packets of processing is done, CPU is constantly going above 60% up to almost %100 (That is with SMT off so just 8 threads vice normal 16 threads) then for a period of time 20%-30% and then repeat, very interesting. Using FPS Monitor it looks similar to a square wave when it is graphs in real time. The performance and the IQ this game gives is utterly phenomenal! Love to see how it plays and looks with DXR, have to agree with Brent 2070 review in the end, " This isn’t a game you sit around admiring the scenery. that this game really does not need DXR" ( https://www.hardocp.com/article/2018/12/17/battlefield_v_nvidia_ray_tracing_rtx_2070_performance/10 ) .I know it has no relation to BFV directly but I was recently reading a similar account over at GamersNexus regarding their 9700k testing and some unusual results GTAV. Seems some engines have unusual high FPS caps and in turn will do odd things to CPU usage when they're hit. Might want to give it a read.
Been experimenting with BF5 and getting some different results with Ryzen. With SMT off, 8 core 2700 OC to 4100mhz, 3200men (in sig) DX 11 is much slower than DX 12. CPU spikes to near 100% at times! Using 16gb Vega FE OC.
Anyways DX 11 1080p is around 111 FPS, DX 12 145 fps. I am somehow frame limited to 145 fps no matter what I do. This is one hell of an interesting game engine and it is using all 8 threads of the 2700 when SMT is turned off.