Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task list for Vulkan Ray Tracing Provisional release #1205

Open
dgkoch opened this issue Mar 17, 2020 · 11 comments
Open

Task list for Vulkan Ray Tracing Provisional release #1205

dgkoch opened this issue Mar 17, 2020 · 11 comments
Assignees

Comments

@dgkoch
Copy link

@dgkoch dgkoch commented Mar 17, 2020

Today the Khronos Vulkan Ray Tracing Task Sub Group (TSG) is announcing the public release of the provisional Vulkan Ray Tracing extensions. See the Press Release for the announcement.

The provisional version of Vulkan Ray Tracing that we are releasing today consists of 3 Vulkan, 2 SPIR-V, and 2 GLSL extensions. See the introductory blog post for more details and an overview of the functionality.

Vulkan Specifications:

SPIR-V Specifications:

GLSL Extension Specifications:

Khronos welcomes feedback on the Vulkan Ray Tracing set of provisional specifications from the developer and content creation communities through the Khronos Developer Slack and Vulkan GitHub Issues Tracker. Developers are also encouraged to share comments with their preferred hardware vendors.
Your feedback is critical to enable us to finalize the first version of Vulkan Ray Tracing and make it genuinely meet your needs!

However, as this is a provisional release, some functionality is likely to change before the final release, consequently we are asking that driver vendors not ship it in production drivers and that ISVs not use the provisional version in production applications.

Applications using the provisional functionality must specifically opt into the interfaces being defined in the Vulkan header using one of the following techniques (similar to the process for enabling the windowing system extensions), either by:

#define VK_ENABLE_BETA_EXTENSIONS
#include <vulkan/vulkan.h>

or by

#include <vulkan/vulkan_core.h>
#include <vulkan/vulkan_beta.h>

and should also check for the exact Vulkan extension version that they are expecting.

Although we do not have a specific timeframe to announce for specification finalization, we want to move forward as quickly as we can, while ensuring the developer community is happy and we have a completed set of conformance tests and at least two implementations that can pass those tests.

The task list for the Vulkan Ray Tracing provisional release is:

Public installable Vulkan Ray Tracing Provisional (aka Beta) drivers are available for download from the following vendors at the supplied URLs:

@Perksey

This comment was marked as off-topic.

Copy link

@Perksey Perksey commented Mar 17, 2020

What's with the deleted comments? If this issue is not to be commented on by the public, please can you lock and limit it so that we're not confused :P

CHEF-KOCH added a commit to CHEF-KOCH/nVidia-modded-Inf that referenced this issue Mar 17, 2020
Presentation:
https://www.khronos.org/assets/uploads/apis/Vulkan-Ray-Tracing-Launch-Mar20.pdf

Press Release:
https://www.khronos.org/news/press/khronos-group-releases-vulkan-ray-tracing

Changelog:
Multi-vendor Vulkan ray tracing
VK_KHR_ray_tracing
VK_KHR_deferred_host_operations
VK_KHR_pipeline_library
For details see the Ray Tracing in Vulkan blog post
VK_EXT_pipeline_creation_cache_control
VK_NV_device_generated_commands
For details see the new device generated command developer blog
Replaces the now deprecated VK_NVX_device_generated_commands
Added support for a new device-local VkMemoryType which is host-coherent and host-visible

Issue tracker:
KhronosGroup/Vulkan-Docs#1205
@dgkoch

This comment was marked as off-topic.

Copy link
Author

@dgkoch dgkoch commented Mar 17, 2020

What's with the deleted comments? If this issue is not to be commented on by the public, please can you lock and limit it so that we're not confused :P

They were from unrelated people I'd accidentally tagged when I created the issue. I figured removing them was better so that they don't get all the notifications from this issue. Now I'm going to have remove this thread so it's not cluttering things up too :-P

@mikew-lunarg

This comment has been minimized.

Copy link
Member

@mikew-lunarg mikew-lunarg commented Mar 18, 2020

I've updated SDK release to "first half of April", which depends on updates from other upstream repos.

@starbucksDave

This comment has been minimized.

Copy link

@starbucksDave starbucksDave commented Mar 19, 2020

Slight error in this post: the macro to enable the beta extensions is VK_ENABLE_BETA_EXTENSIONS and not VK_ENABLE_BETA_EXTENSIONS_KHR. Sorry for the nitpick!

@dgkoch

This comment has been minimized.

Copy link
Author

@dgkoch dgkoch commented Mar 19, 2020

@dgkoch Ah ok understood. As to not further clog up this issue with an unrelated thread, please can you use the Hide function instead of the Delete function (as I do still want to receive notifications as well as I want people to see why comments have been deleted)

Done. I was unaware of that option. Thanks for pointing it out.

@dgkoch

This comment has been minimized.

Copy link
Author

@dgkoch dgkoch commented Mar 19, 2020

Slight error in this post: the macro to enable the beta extensions is VK_ENABLE_BETA_EXTENSIONS and not VK_ENABLE_BETA_EXTENSIONS_KHR. Sorry for the nitpick!

🤦‍♂ Doh. That was a last minute change I forgot to reflect in the documentation. Corrected above (and soon in the blog post as well).

@dneto0

This comment has been minimized.

Copy link

@dneto0 dneto0 commented Mar 19, 2020

I updated Shaderc's known-good branch with a build with necessary support from SPIRV-Tools, SPIRV-Headers, Glslang, and Shaderc itself. google/shaderc#1006

@dgkoch

This comment has been minimized.

Copy link
Author

@dgkoch dgkoch commented Mar 24, 2020

Validation layer support has been merged.

@dgkoch

This comment has been minimized.

Copy link
Author

@dgkoch dgkoch commented Mar 25, 2020

I updated Shaderc's known-good branch with a build with necessary support from SPIRV-Tools, SPIRV-Headers, Glslang, and Shaderc itself. google/shaderc#1006

@dneto0 can we get another shaderc update to include KhronosGroup/glslang#2139 ?

@dgkoch

This comment has been minimized.

Copy link
Author

@dgkoch dgkoch commented Mar 25, 2020

I updated Shaderc's known-good branch with a build with necessary support from SPIRV-Tools, SPIRV-Headers, Glslang, and Shaderc itself. google/shaderc#1006

@dneto0 can we get another shaderc update to include KhronosGroup/glslang#2139 ?

See google/shaderc#1018

@mikew-lunarg

This comment has been minimized.

Copy link
Member

@mikew-lunarg mikew-lunarg commented Apr 8, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.