QUOTE(adilz @ Jul 12 2016, 01:55 PM)
An article from extremetech
http://www.extremetech.com/gaming/231527-n...rformance-boost
Not only talk about the Vulkan patch, but general response from both camps on shifting to the new APIs.
On the Async Compute, here is excerpt from that article
"According to AMD, Doom now takes advantage of asynchronous compute and shader intrinsics that allow the game engine to directly access hardware (a video describing how this works is embedded above)."
I can only hope Nvidia lack of response is only because they are working on way to overcome this.
Actually, NVIDIA responded during GPU Technology Conference during the talk "VULKAN OVERVIEW" by Piers Daniell http://www.extremetech.com/gaming/231527-n...rformance-boost
Not only talk about the Vulkan patch, but general response from both camps on shifting to the new APIs.
On the Async Compute, here is excerpt from that article
"According to AMD, Doom now takes advantage of asynchronous compute and shader intrinsics that allow the game engine to directly access hardware (a video describing how this works is embedded above)."
I can only hope Nvidia lack of response is only because they are working on way to overcome this.
http://on-demand.gputechconf.com/gtc/2016/...an_Overview.pdf
NVIDIA TODO
What’s not in our first release?
Transfer-only queue to expose copy engine(s) (implemented already on 364.91)
Compute-only queue for potential async compute
This post has been edited by Demonic Wrath: Jul 12 2016, 02:15 PM
Jul 12 2016, 02:07 PM

Quote



0.0280sec
0.60
6 queries
GZIP Disabled