Soldato
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Essentially a complete switcharound from DX11, where it's the AMD driver that has a lot more CPU overhead. I suppose it's not that surprising, given how long AMD have been laser-focused on low-level APIs, from Mantle onwards. To the detriment of anything else actually, like their completely broken OpenGL performance on Windows, which they refuse to fix because it's been "replaced" by Vulkan. Nvidia seemed to be rather more dragged kicking and screaming away from older APIs, since they were top dog already. I still remember all the arguments about asynchronous compute from years ago when DX12/Vulkan games first started appearing.
Essentially a complete switcharound from DX11, where it's the AMD driver that has a lot more CPU overhead. I suppose it's not that surprising, given how long AMD have been laser-focused on low-level APIs, from Mantle onwards. To the detriment of anything else actually, like their completely broken OpenGL performance on Windows, which they refuse to fix because it's been "replaced" by Vulkan. Nvidia seemed to be rather more dragged kicking and screaming away from older APIs, since they were top dog already. I still remember all the arguments about asynchronous compute from years ago when DX12/Vulkan games first started appearing.
Apologies, haven't got time to watch the video, but where the CPU loading is higher, is that simply completed by one of the spare cores, that most of us now have? In which case, does it matter?
Nvidia drivers work ok but they are in desperate need of a overhaul, as does the Windows XP control panel.
How the tables have turned! This used to be an AMD problem.
True, but Nvidia are much bigger than AMD with a lot more cash and an army of software developers so they have no excuse. I wonder whether this is part of the reason why Assassin's Creed Valhalla performs so much better on AMD as both my Nvidia cards never go above 95% GPU usage in that game whereas AMD are pegged at 99% and it's a DX12 game, all the YouTube videos I've seen show this GPU utilisation problem.Essentially a complete switcharound from DX11, where it's the AMD driver that has a lot more CPU overhead. I suppose it's not that surprising, given how long AMD have been laser-focused on low-level APIs, from Mantle onwards. To the detriment of anything else actually, like their completely broken OpenGL performance on Windows, which they refuse to fix because it's been "replaced" by Vulkan. Nvidia seemed to be rather more dragged kicking and screaming away from older APIs, since they were top dog already. I still remember all the arguments about asynchronous compute from years ago when DX12/Vulkan games first started appearing.
Yeah the control panel works, but it's so dated looking and sluggish compared to what amd have. I can't even recall when nvidia brought that control panel in, must be well over 10 years at this point.
Yeah the control panel works, but it's so dated looking and sluggish compared to what amd have. I can't even recall when nvidia brought that control panel in, must be well over 10 years at this point.
It might also be a problem that the Ampere architecture is a very wide Vega-like architecture with many compute units and it's tough to keep them all occupied with work.
However, that wouldn't explain the GPU utilisation problem in Valhalla because that happens on both my 1080 and my 3080.