Quicksync async depth driver#

Quicksync async depth driver#

It did not all come from an AMD driver release or Windows 10.īatman. My frame rate in Project Cars went from 18fps to over 70 fps since all hell was raised. I'd like to think that there had to be a reason for these changes and fixes other than they suddenly figured all of these and the thousands of issues fixed before. Nvidia users have tessellation settings now right? The patch today is 15GB and not all 'expansion'. Suddenly there are a ton more graphics sliders.

Really you have to look at the GameWorks suite from this year and how they have morphed and changed over time.įirst look at the Witcher 3. Taking about code paths, PS4, Xbox one, Maxwell 2, Fiji, and the r3xx series all need different code paths, varying amounts of ACE's (queues) cause this problem when we are talking about aysnc. GCN hardware also have the same issue but its lessened because they do have fine grained context switching, but even that will introduce latency into the system, lesser degree yes but its still there. If we use a context switch in this case it will stall the pipeline, that is opposite of what you want when you want to do async compute.Īnd the do's and don'ts say that too, using context switching too much unnecessarily will give bad performance. Both kernels have to be running for async to work. Context switching is only when you want to shut down one type of kernel and start another in the same pipeline, with async you don't need to do this, we are taking compute instructions from a compute task and placing into the graphics task. There is nothing such as transparency when the GPU is doing its thing, there is a reason for this because the developer doesn't have control over the async work unless they use context switching, which they shouldn't be using. What is out of spec for you? Cause I can tell ya, they aren't out of spec.