GPSnoopy / RayTracingInVulkan

Implementation of Peter Shirley's Ray Tracing In One Weekend book using Vulkan and NVIDIA's RTX extension.
BSD 3-Clause "New" or "Revised" License
1.27k stars 116 forks source link

Validation Errors #51

Closed kyamant closed 3 years ago

kyamant commented 3 years ago
- loading '../assets/textures/white.png'... (1 x 1 x 3) 0.0003277s
- built acceleration structures in 0.0429433s
ERROR: VALIDATION: Validation Error: [ UNASSIGNED-spirv-shaderClock-shaderSubgroupClock ] Object 0: handle = 0x19450f759e8, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa73ec9c2 | VkShaderModule 0x57fea6000000023e[]: OpReadClockKHR is used with a Subgroup scope but shaderSubgroupClock was not enabled.

  Objects (1):
  - Object[0]: Type: DEVICE, Handle: 0000019450F759E8, Name: ''

ERROR: VALIDATION: Validation Error: [ UNASSIGNED-spirv-shaderClock-shaderSubgroupClock ] Object 0: handle = 0x19450f759e8, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa73ec9c2 | VkShaderModule 0x57fea6000000023e[]: OpReadClockKHR is used with a Subgroup scope but shaderSubgroupClock was not enabled.

  Objects (1):
  - Object[0]: Type: DEVICE, Handle: 0000019450F759E8, Name: ''

Swap Chain:
- image count: 2
- present mode: 2

ERROR: VALIDATION: Validation Error: [ VUID-VkMappedMemoryRange-size-01389 ] Object 0: handle = 0x1a4aac0000000255, type = VK_OBJECT_TYPE_DEVICE_MEMORY; | MessageID = 0xee4872d | vkFlushMappedMemoryRanges: Size in pMemRanges[0] is VK_WHOLE_SIZE and the mapping end (0x8638 = 0x0 + 0x8638) not a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize (0x40) and not equal to the end of the memory object (0x8700). The Vulkan spec states: If size is equal to VK_WHOLE_SIZE, the end of the current mapping of memory must either be a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize bytes from the beginning of the memory object, or be equal to the end of the memory object (https://vulkan.lunarg.com/doc/view/1.2.176.1/windows/1.2-extensions/vkspec.html#VUID-VkMappedMemoryRange-size-01389)

  Objects (1):
  - Object[0]: Type: DEVICE_MEMORY, Handle: 1A4AAC0000000255, Name: ''
GPSnoopy commented 3 years ago

I thought I had fixed these already. Which source version are you using?

kyamant commented 3 years ago

Up-to-date code does not have these errors