6 votes Posted March 18, 2020 by unknown user Topic deleted by author 2 comments Collapse replies Expand all Comments sorted by most votes newest first order posted relevance OK [2] rmgr March 18, 2020 Link This is pretty huge. The gap between DirectX and Vulkan keeps narrowing! This is pretty huge. The gap between DirectX and Vulkan keeps narrowing! 2 votes Moonchild March 18, 2020 Link Parent Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan. Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan. 2 votes
[2] rmgr March 18, 2020 Link This is pretty huge. The gap between DirectX and Vulkan keeps narrowing! This is pretty huge. The gap between DirectX and Vulkan keeps narrowing! 2 votes Moonchild March 18, 2020 Link Parent Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan. Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan. 2 votes
Moonchild March 18, 2020 Link Parent Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan. Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan. 2 votes
This is pretty huge. The gap between DirectX and Vulkan keeps narrowing!
Not really. There was already VK_NV_raytracing. This just means it's standard. There's not really a meaningful gap between d3d12 and vulkan.