Author Topic: Vulkan SDK 1.0.17.0 Released  (Read 3524 times)



0 Members and 1 Guest are viewing this topic.

Stefan

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4228
    • View Profile
Vulkan SDK 1.0.17.0 Released
« on: June 24, 2016, 04:18:15 PM »
 
This SDK supports Vulkan API revision 1.0.17.  The prior SDK supported Vulkan API revision 1.0.13.
Device layers are now deprecated! Any device layers must be converted to a layer that is queried and enabled at vkCreateInstance. vkEnumerateDeviceLayerProperties is deprecated.
  Overview of new features in SDK 1.0.17.0
  • VulkanInfo has been improved
  • Fence tracking and validation has been rearchitected
  • Validation layer test suite has been enhanced
  • Added default validation error callbacks
  • Additional structural and architectural layer improvements and cleanup to core_validation
  • Scores of bugfixes, new validation checks, and feature additions
This version of the SDK components are based on the following specifications and source code repositories:
   Last Commits
  • LoaderAndValidationLayers:     e966288576573  docs: Fix broken link in LoaderAndLayerInterface
  • VulkanTools:                  e0306ab0e1eeb2  winsdk: Fix multiple RT uninstall issue
  • VulkanSamples:                cb82ddaab2f5e1  winsdk: Fix multiple RT uninstall issue
  Known Issues
  • This WSI extension is not supported: VK_KHR_display_swapchain
Vulkan-LoaderAndValidationLayers Issues:
 
  • github #677 Problem with vkWaitDeviceIdle() in Validation Layers
  • github #676 Core validation layer incorrectly reports that swapchain image memory has not been filled
  • github #663 VkBuffer objects not bound to VkDeviceMemory objects are not detected on use
  • github #660 VS Input error when using push constants gi- thub #659 Instance extension from an implicit layer cannot add entry points. github #658 Inconsistant handle display in api_dump and validation layer messages
  • github #650 Core_validation: ValidateCmdBufImageLayouts() should be treating D views of DS images as DS image views
  • github #648 Core_validation: "Buffer Barrier X has offset Y and size Z whose sum is greater than total size W" error refers to the wrong size
  • github #621 IMAGE: "unsupported format" error may be too strict
  • github #618 object_tracker doesn't use the correct wsi extension flags
  • github #616 Crash if binding point is used with no resource has been bound
  • github #615 unique_objects layer doesn't use the correct wsi extension enable flags
  • github #605 vkCmdResolveImage generates invalid "Cannot read invalid memory..., please fill..." message github #561 Resetting command pool doesn't track fences properly
  • github #527 Core Validation: Invalid "explicit dep needed" warning is issued at vkCmdBeginRenderPass() call time.
  • github #462 Validation for pCreateInfo structures does not report actual index (attachments, vertex input state)
  • github #410 DS: vkQueueSubmit checks Event state too early when vkSetEvent is used
  • github #403 [CTS] Object tracker maps need to be per device
  • github #370 loader needs to use object allocators passed by application for memory allocations
  • github #335 Undefined memory tracking is not fine grained enough
  • github #328 Validation layer reports errors if memory object alias same memory
  • github #321 vkAllocateMemory not handling null pointers
  • github #306 race on globalLockInitialized: it is reset after releasing the mutex lock
  • github #282 layer_validation_test failures
  • github #281 Cube -- validate with screenshot crashes on AMD/Intel Win 10
  • github #280 Cube resize stops updating image on Win 10 Intel driver
  • github #279 Samples validation errors on AMD driver
  • github #278 tri resize broken on AMD driver
  • github #277 render tests --show-images doesn't work
  • github #276 render tests have validation errors
  • github #128 Memory layer: "Cannot read invalid memory X, please fill the memory before using" is incorrectly reported
  • github #90 loader: Add support for WSI VK_KHR_display_swapchain extension
  • github #54 vk_layer_validation_tests test failure
  • github #36 loader: pointer cast build warnings
LunarXchange Issues:
 
  • LX #552 Declining Frame Rate
  • LX #549 vkreplay segfault when used with xlib
  • LX #532 Bindless and ' descriptor index %d is being used in draw but has not been updated'
  • LX #527 The draw state validation layer incorrectly reports layout error when submitting command buffer. Vulkan-LoaderAndValidationLayers GitHub
  • LX #523 When I enable validation layers vkCreateWin32SurfaceKHR returns garbage pointer and vkCreateSwapchainKHR crashes
  • LX #484 vktrace puts trace file in same dir as trace library if -o not specified
  • LX #305 [1.0.1.1] Validation draw state layer too slow for vkGetQueryPoolResults()
VulkanTools/VulkanSamples issues:
 
  • github #1 [VulkanTools] Running vktrace with validation enabled causes vkreplay to fail.
  • github #3 [VulkanTools] writes to device memory allocated with VK_MEMORY_PROPERTY_HOST_COHERENT_BIT are not captured
  • github #33 [VulkanTools] The trace file generated on 32bit system cannot be read by 64bit traceviewer
  • github #42 [VulkanTools] miss alignment for some arm cpu vfp load instructions
  • github #45 [VulkanTools] Examples at https://github.com/McNopper/Vulkan don't trace/replay
  • github #49 [VulkanTools] Examples at https://github.com/SaschaWillems/Vulkan don't all trace and replay
  • github #50 [VulkanTools] vktrace: VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT is not being handled consistently with regards to VkUpdateDescriptorSets()
  • github #51 [VulkanTools] Message "VS consumes input at location 0 but not provided" could be more helpful
  • github #53 [VulkanTools] vktrace dies on Win7/32