claude_code/procedural-3d-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Removed redundant depth attachment layout transition and wrong comment

Browse source
This commit is contained in:
saschawillems 2016-08-04 21:18:05 +02:00
parent 3eeea85e20
commit 563d7c4b9c
1 changed files with 1 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

13
triangle/triangle.cpp
View file

@ -760,23 +760,12 @@ public:
VK_CHECK_RESULT(vkAllocateMemory(device, &memAlloc, nullptr, &depthStencil.mem));
VK_CHECK_RESULT(vkBindImageMemory(device, depthStencil.image, depthStencil.mem, 0));
// We need to do an initial layout transition before we can use this image
// as the depth (and stencil) attachment
// We need to do an initial layout transition before we can use this image as the depth (and stencil) attachment
// Note that this may be ignored by implementations that don't care about image layout
// transitions, but it's crucial for those that do
VkCommandBuffer layoutCmd = getCommandBuffer(true);
vkTools::setImageLayout(
setupCmdBuffer,
depthStencil.image,
VK_IMAGE_ASPECT_DEPTH_BIT | VK_IMAGE_ASPECT_STENCIL_BIT,
VK_IMAGE_LAYOUT_UNDEFINED,
VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL);
// Add a present memory barrier to the end of the command buffer
// This will transform the frame buffer color attachment to a
// new layout for presenting it to the windowing system integration
VkImageMemoryBarrier imageMemoryBarrier = {};
imageMemoryBarrier.sType = VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIER;
imageMemoryBarrier.srcAccessMask = VK_FLAGS_NONE;