-
Notifications
You must be signed in to change notification settings - Fork 52
Enable synchronization2 in feature chain #279
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
base: main
Are you sure you want to change the base?
Conversation
otherwise an error is reported
SaschaWillems
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That chapter does not make use of any sycn2 features, so no need to enable that yet.
This should match what the code does instead:
vk::StructureChain<vk::PhysicalDeviceFeatures2, vk::PhysicalDeviceVulkan13Features, vk::PhysicalDeviceExtendedDynamicStateFeaturesEXT> featureChain = {
{}, // vk::PhysicalDeviceFeatures2
{.dynamicRendering = true}, // vk::PhysicalDeviceVulkan13Features
{.extendedDynamicState = true} // vk::PhysicalDeviceExtendedDynamicStateFeaturesEXT
};|
following the tutorial, the program failed without sync2. besides i was using vulkan api 1.4 not 1.3 if it means anything. p.s. |
|
besides please also note that in the C++ code example: https://docs.vulkan.org/tutorial/latest/_attachments/04_logical_device.cpp has these required extensions: std::vector<const char *> requiredDeviceExtension = {
vk::KHRSwapchainExtensionName,
vk::KHRSpirv14ExtensionName,
vk::KHRSynchronization2ExtensionName,
vk::KHRCreateRenderpass2ExtensionName}; |
|
We have recently removed most of those extensions, see #260. Docs.vulkan.org prob. hasn't been updated yet. |
@SaschaWillems thanks for that. I found also that in other pages is was referencing to the like this page is "not ok", as well its code after: https://docs.vulkan.org/tutorial/latest/_attachments/05_window_surface.cpp and closed that gap. |
|
The docs site is updated when spec updates are released, so updates can take up to a week before they show up there. We are aware of the issue regarding differences in documentation and code, and they'll be fixed (see the other issues). Fyi @gpx1000 |
|
thanks |
otherwise an error is reported