Vulkan: VkFramebufferCreateInfo doesnt allow for just passing the attachmentCount
See original GitHub issueEnvironment
- LWJGL version:
3.3.0
- LWJGL build #:
SNAPSHOT
- Java version:
java.version
- Platform:
Linux
- Module:
Vulkan
Description Of Issue
for ImagelessFramebuffers (A Core feature of vulkan 1.2), you need to be able to specify just the count of attachments. Specifying the attachments causes problems within Khronos Validation Layers. we have tried VkFramebufferCreateInfo.nattachmentCount(framebufferInfo.address(), 2);
but this unfortunately doesn’t work due to the checks causing a NullPointerException
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
VkFramebufferCreateInfo(3) - Khronos Registry
attachmentCount is the number of attachments. pAttachments is a pointer to an array of VkImageView handles, each of which will be used as...
Read more >KhronosGroup/Vulkan-ValidationLayers - GitHub
TEST_DESCRIPTION("Use a pipeline for the wrong subpass in a render pass instance"); ... Set level count to 2 (only 1 is allowed for...
Read more >Vulkan - Loading depth attachment in the second renderpass ...
In second pass, depth attachment description, it "loads" image in undefined state: attachments[2].initialLayout = VK_IMAGE_LAYOUT_UNDEFINED;.
Read more >Framebuffers - Vulkan Tutorial
The attachments specified during render pass creation are bound by wrapping them into a VkFramebuffer object. A framebuffer object references all of the ......
Read more >Vulkan with rust by example 4. Swapchain.
An image is just memory, and this entire step is dedicated to these special ... VkFramebufferCreateInfo attachmentCount of 2 does not match ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hYdos Thanks! This was a bug in lwjgl3-vulkangen that has been fixed with https://github.com/LWJGL/lwjgl3-vulkangen/commit/f62d362c032a2216168b0ce9cf303c321f3fa4b0. The validation will be removed in the next 3.3.0 snapshot.
As a work-around you can disable those consistency-checks in LWJGL in the meantime:
by either calling
Configuration.DISABLE_CHECKS.set(true)
or by setting the system propertyorg.lwjgl.util.NoChecks
totrue
.