- make implicit for `vkCmdSetViewport`
- make implicit for `vkCmdSetViewportWScalingNV`
- removed redundant explicit duplicate for `vkCmdSetDiscardRectangleEXT`
- remove redundant VU about the `pDiscardRectanges` vector; it is
implicit
- remove redundant VU about `firstDiscardRectangle` it is fully covered
by `00585` and implicit VU that says `discardRectangleCount` is greater
than 0
- remove redundant VU part saying >=1; it is implicit because of
`discardRectangleCount` > 0
- tweak `VkRect2D` VUs to mention the array they are part of
* Bump API patch number and header version number to 66 for this update.
Github Issues:
* Clarified how and when ename:VK_ERROR_TOO_MANY_OBJECTS is generated in
flink:vkAllocate Memory, and remove incorrect valid usage statement
about exceeding the API limit (public issue 356).
* Minor clarification of the description of
flink:vkUpdateDescriptorSetWithTemplateKHR::pname:descriptorUpdateTemplate
(public issue 564).
* Minor fixes for flink:vkCmdSetViewportWScalingNV (public pull request
588).
* Fix random name markup issues (public pull request 603).
* Fix code:BuiltIn decoration typo in the <<fxvertex-attrib, Vertex
Attributes>> section (public pull request 606).
* Fix synchronization language following the definition of
flink:vkAcquireNextImageKHR (public issue 607).
* Restore descriptions of several commands and structures missing from the
generated spec due to a mistyped asciidoctor conditional (public issue
612).
* Fix 1.0.41 changelog to refer to public issues 403/404 (public issue
618).
Internal Issues:
* Refactor valid usage statements with internal conditionals in
`copies.txt`, `pipelines.txt`, `renderpass.txt`, and `resources.txt` so
each branch of the conditional appears as a standalone statement which
can contain a separate VUID. This should have no impact on the generated
specs, but is necessary given the present state of the VU extractor and
the validation layer code that consumes them (internal issue 1043).
* Fix VkQueueGlobalPriorityEXT enum values missing _EXT suffix (internal
issue 1045).
* Clarified initial ownership of resources bound to shared memory objects,
(internal issue 1068).
* Fix duplicated valid usage ID tag for flink:vkCmdCopyImage, and make the
required layouts include ename:VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIONAL in
both cases (internal issue 1084).
Other Issues:
* Remove the noise functions from GLSL for SPIR-V for Vulkan in the
`GL_KHR_vulkan_glsl.txt` extension.
New Extensions:
* `VK_EXT_external_memory_host`
* `VK_EXT_external_memory_dma_buf`
* `VK_EXT_queue_family_foreign`
- add missing `*name` and `*link` and `code`
- change where wrong macro was used
- swap `*name` and `*link` where appropriate
- correct misspelled names
- that sort of thing...
* Bump API patch number and header version number to 65 for this update.
Github Issues:
* Replaced inaccurate "`pixel`" with "`texel`" or "`compressed texel
block`" as appropriate in the <<sparsememory, Sparse Resources>> chapter
(public issue 86).
* Attempt to clarify security/integrity guarantees in the
<<fundamentals-errors, Errors>> section (public issue 147).
* Update the <<memory-device,Device Memory>> section with clarifications
and markup fixes (public pull request 194).
* Fix typo VkDeviceCreateInfo -> slink:VkDebugMarkerObjectNameInfoEXT in
sample code for `VK_EXT_debug_marker` extension (public pull request
227).
* Clarified slink:VkFramebufferCreateInfo language regarding concurrent
use of attachment resources during a render pass instance (public issue
299).
* Added overlap rules for destination regions in <<copies,copy commands>>.
Also unified the sparse and non-sparse source-destination overlap rules,
since the non-sparse rules were technically inaccurate in the face of
aliasing in flink:vkBindMemory2 - the new rules are true regardless
(public issue 317).
* Clarified the <<features-features-samplerAnisotropy,
pname:samplerAnisotropy feature>> to only affect the
slink:VkSamplerCreateInfo::pname:anisotropyEnable value, and that
pname:maxAnisotropy is ignored when pname:anisotropyEnable is VK_FALSE
(public issue 503).
* Clarify pointer valid usage statements to use "`valid pointer to valid
_object_`" terminology and update the
<<fundamentals-validusage-pointers,Valid Usage for Pointers>> section
accordingly (public pull request 547).
* Some operations that use integer coordinates can also accept a LOD to
sample from. Add a description of that selection and the validity
conditions in the new <<textures-integer-coordinate-operations, Integer
Texel Coordinate Operations>> section (public issue 548).
* Update stext:VkImageSubresource* valid usage statements (public pull
request 550).
* Added text tying ename:VK_OUT_OF_POOL_MEMORY error for
flink:vkAllocateDescriptorSets to the number of descriptor types in the
allocating pool. Removed redundant "`length`" text about number of
descriptors returned (public issue 582).
* Update slink:VkSwapchainCreateInfoKHR descriptions (public pull request
585).
* Update slink:VkPipelineViewportWScalingStateCreateInfoNV and related
structures' valid usage statements (public pull request 587).
* Change some dates to conform to ISO 8601 as specified in the style guide
(public pull request 601).
* Fix some math markup problems and be more consistent in use of asciidoc
math markup (public pull request 602).
Internal Issues:
* Clarified that attribute reads from incomplete vertex buffer elements
are considered out of bounds accesses, in the
slink:VkPhysicalDeviceFeatures and flink:vkCmdBindVertexBuffers.txt
sections (internal issue 842).
Other Issues:
New Extensions:
- fixes rest of #416 (`VkImageSubresourceLayers`)
- migrate `VkImageSubresource` VUs where the state is known
- Simplify `VkImageSubresource` (`*count` always > 0)
1) Make explicit there is a <=> relationship between `DEVICE_LOCAL` heap
and `DEVICE_LOCAL` memory type
2) Make >4GB runtime error report mandatory. Otherwise it basically says
"do not pass >= 4GB, because possible undefined behavior".
3) Removed `VUID-vkAllocateMemory-device-00636`. Behavior is
deterministic returning `VK_ERROR_TOO_MANY_OBJECTS`
4) Moved `allocationSize` VU (depends on non-local state).
5) Changed `allocationSize`. Not sure what the original means, so
improvized a new one saying alloc size must be <= the whole size of the
heap.
6) Added VU restricting `memoryTypeIndex` to only the memory types of
the device.
1) Random grammar and formatting
2) Make example in first paragraph more
straightforward with elementary
Vulkan primitives (the original also
seemed factually wrong in places;
e.g. does UBO really have to be in
"on-device" memory?)
3) Removed unnecessary brandishing of obscure math
describing the memory
type list order. Tried something equally formal,
but more readable.
4) Made a note into a Note
5) Updated example.
Function names seem to be lower-case in the spec.
Hopefully made it bit
more readable. Turned the acompanying note into
the example content and
inline comments.
6) Removed redundant `VkDeviceMemory` intro
7) Break
out specifying language out of a Note
8) More straightforward description of `memoryTypeIndex`
* Bump API patch number and header version number to 64 for this update.
Github Issues:
* Add chapter name to the PDF page footer (public pull request 458).
* Fix several mistaken references to the nonexistent etext:VK_DEVICE_LOST
status to etext:VK_ERROR_DEVICE_LOST (public pull request 502).
* Fix description of the tlink:PFN_vkDebugReportCallbackEXT debug report
callback function pointer to match the validation layer behavior (public
issue 534).
* Document experimental KHX extensions and alternate vendor author IDs
also ending in X in more detail in the <<extensions, Layers &
Extensions>> appendix, the extensions section of the style guide, and
the registry schema description document (public issues 536, 580).
* Fix references to ptext:pDepthStencil to properly refer to
pname:pDepthStencilState or pname:pRasterizationState as appropriate in
the slink:VkGraphicsPipelineCreateInfo description (public issue 542).
* Fix wrong parameter name in slink:VkPipelineMultisampleStateCreateInfo
valid usage (public pull request 571).
Internal Issues:
* Update the style guide to describe how to write LaTeX math expressions
in table cells (internal issue 908).
* Define how framebuffer-local dependencies work between subpasses with
the same or different numbers of samples, in the
slink:VkSubpassDescription and <<synchronization-framebuffer-regions,
Framebuffer Region Dependencies>> sections. This clarifies which samples
in an input attachment you are allowed to access after a
framebuffer-local dependency (internal issue 915).
* Specify which storage classes can have an initializer in the
<<spirvenv-module-validation, Validation Rules within a Module>> section
(internal issue 1023).
* Use "LOD" consistently for "level-of-detail", to eliminate spelling
inconsistencies. The term is already standardized in the Glossary
(internal issue 1027).
Other Issues:
* Fix false positives in Makefile dependencies when rules fail, by
deleting partially-made targets.
New Extensions:
* `VK_AMD_shader_info`
Jon Leech
Petr Kraus
Jon Leech
Lei Zhang