happy medium
Lifer
- Jun 8, 2003
- 14,387
- 480
- 126
You sure you didn't mix the pictures up?
The amount of GPU bound is how much slower the GPU is then the CPU so in your pictures async makes your GPU slower.
So it's not just an nvidia problem...good to know.Re-tested to be sure, yeap the pics are not mixed up.
Async Compute = 1
Actually the setting in the ini file isSo it's not just an nvidia problem...good to know.
1440 and up,nothing new.now amd wins even in dx11.
Look at this crap,if you turn off all effects going from 768 to 1080 hardly looses any FPS(in fact it's even a little faster) ,why? low cpu usage = only GPU compute and the amount of compute (units/effects on screen) is the same no matter the resolution.
What? Can you explain the point you are trying to make here?
1440 and up,nothing new.
This game especially is a GPU compute prOn demo so obviously it's best suited for AMD.
Look at this crap,if you turn off all effects going from 768 to 1080 hardly looses any FPS(in fact it's even a little faster) ,why? low cpu usage = only GPU compute and the amount of compute (units/effects on screen) is the same no matter the resolution.
https://www.youtube.com/watch?v=Le5zNn5dEpI
https://www.youtube.com/watch?v=WqC2OuwBhxU
Also the celeron is supposed to be able to reach ~36FPS...
![]()
No I'm saying that in any other game going from a lower to a higher resolution you are going to loose a lot of FPS.Sounds like he is somehow trying to say that being GPU bound is a bad thing, and that's why the AMD cards are performing better. Never mind that you want GPU bound testing situations to be able to clearly tell which card is better...
No I'm saying that in any other game going from a lower to a higher resolution you are going to loose a lot of FPS.
If you are GPU bound at 768 then 1080 should be a catastrophe and not just as fast.
No I'm saying that in any other game going from a lower to a higher resolution you are going to loose a lot of FPS.
If you are GPU bound at 768 then 1080 should be a catastrophe and not just as fast.
Actually the setting in the ini file is
AsyncComputeOff=0 0 meaning no,so no to the OFF meaning it is using async
AsyncComputeOff=1 1 meaning yes,so yes to the OFF meaning it is not using async
Also, NVNetworkServise?! with AVGuard. is killing his CPU
you can see his GPU is not maxed with utilization dropping to 50%! I guess nv need to release Ready Game Ready drivers mkII for ashes.
now amd wins even in dx11. what kind of crazy optimizing did they do for dx11 or did they downgrade the game somehow? What are the differences between dx12 and 11?
AMD released optimized drivers for Ashes DX11 awhile back, during beta 2. It mostly fixed their crap DX11 performance in this game.
Again, showing how driver reliant DX11 is.
AMD's DX11 driver's were never the issue for the most part ...
It was mostly their front-end with the command processor, you just have to be more aggressive in batching more triangles per draw call with AMD hardware ...
Hard for me to agree with that when AMD's DX11 performance in Ashes skyrocket with one "Game Ready" driver from AMD.
I mean the cause can be command processor limited as you say, but the performance was gained via a driver update.