26f0bdbf1e
* Update release number to 72. Github Issues: * Restructure the repository to put the specification `Makefile` and associated spec source material at the top level, `vk.xml` and associated scripts material in `xml/`, and generated include and source files in `include/vulkan/` and `src/ext_loader/`, respectively (public issue 436). * Add missing bullet point markup to flink:vkCmdCopyImage valid usage statement, so it gets a VUID assigned (public issue 627). * Fix broken links in a couple of extension appendices (public pull request 665). * Add the \<platform> tag to the index in section 4.1 of the registry schema documentation, and add the protect= attribute of \<extension> tags to the comments in `registry.rnc` (public issues 673, 678). * Add missing valid usage statements for sparse image interactions to flink:VkImageCreateInfo (public pull request 675). * Fix improper usage and grammar of "`can: not`" (public pull request 681). * Remove duplicate spec language and NOTE on present layout between the flink:vkAcquireNextImageKHR and flink:vkAcquireNextImage2KHR commands (public pull request 685). * Fix some typos and markup issues (public pull request 689; public issues 642, 667, 687). * Fix typo etext:VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_FENCE_FD_BIT -> ename:VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT in the <<external-semaphore-handle-types-compatibility, External semaphore handle types compatibility>> table (public pull request 691). Internal Issues: * Remove the need for the "`noautovalidity`" attribute on extension structures in `vk.xml`. It is now implied by the "`structextends`" attribute instead (internal issue 942). * Replace uses of "`currently bound`" with "`bound`", since "`currently`" is redundant and distracting, and add a corresponding rule to the style guide (internal issue 993). * Fixed subtle issues with the last updates to flink:vkAcquireNextImageKHR language that had resulted in ambiguities (internal issue 1178). * Make it clear that only one query of a given type is allowed at a time by reordering valid usage statements for flink:vkCmdBeginQuery and flink:vkCmdEndQuery, and removing redundant ones (internal issue 1213). * Swapped OL1 and OL3 in `tessparamUL.svg` to match previous version, and fixed where "`(no edge)`" appears (internal issue 1215). Other Issues: * Fixed a minor problem with the valid usage statement extraction script, and corresponding markup in the spec source. New Extensions: * `VK_AMD_shader_core_properties` * `VK_EXT_descriptor_indexing` * `VK_NV_shader_subgroup_partitioned` |
||
---|---|---|
.. | ||
README.adoc | ||
base_image_sample_grid.svg | ||
chromasamples_420_xcosited_ycosited.svg | ||
chromasamples_420_xcosited_ymidpoint.svg | ||
chromasamples_420_xmidpoint_ycosited.svg | ||
chromasamples_420_xmidpoint_ymidpoint.svg | ||
chromasamples_422_cosited.svg | ||
chromasamples_422_midpoint.svg | ||
commandbuffer_lifecycle.svg | ||
fragment_mask.svg | ||
innerquad.svg | ||
innertri.svg | ||
non_strict_lines.svg | ||
pipeline.svg | ||
primitive_topology_line_list.svg | ||
primitive_topology_line_list_with_adjacency.svg | ||
primitive_topology_line_strip.svg | ||
primitive_topology_line_strip_with_adjacency.svg | ||
primitive_topology_point_list.svg | ||
primitive_topology_triangle_fan.svg | ||
primitive_topology_triangle_list.svg | ||
primitive_topology_triangle_list_with_adjacency.svg | ||
primitive_topology_triangle_strip.svg | ||
primitive_topology_triangle_strip_with_adjacency.svg | ||
sparseimage.svg | ||
sparseimage_alignedmipsize.svg | ||
sparseimage_alignedmipsize_singlemiptail.svg | ||
sparseimage_multiaspect.svg | ||
sparseimage_singlemiptail.svg | ||
tessparam.svg | ||
tessparamUL.svg | ||
vulkantexture0.svg | ||
vulkantexture1.svg | ||
vulkantexture2.svg |
README.adoc
= Diagrams Diagrams in this folder have been created with Inkscape, using a restricted color palette (white, black, 50% gray and pure red), one choice of dotted vs. solid lines, and only two text sizes (10 and 12) using the generic "sans serif" font family. Size 10 fonts should only be used for incidental text for labelling in the middle of the diagram as an identifying mark (e.g. an example sample point); prefer size 12 fonts wherever possible. Smaller sizes are unreadable at default zoom, and larger sizes stick out and are jarring within the context of the specification. All diagrams are sized 1:1 so that no additional rescaling is required in the Specification, which would affect the font sizes. If adding any new diagrams, please try to maintain consistency with the rest of these diagrams in order to aid consistency and readability of the Vulkan specification. Inkscape does not need to be used, but is recommended as a powerful free tool for generating vector diagrams, and is known to generate diagrams compatible with the rest of the Vulkan toolchain. If using other tools, please ensure that the diagram renders correctly in popular browsers and in the PDF generation path for the specification. == UTF-8 Characters At the moment, the PDF conversion path only supports the Windows-1252 character set, as we are currently using the standard fonts built into every PDF viewer - such that we don't have to embed a different font. Unfortunately these only support Windows-1252, which is a highly limited character set. As such, characters not in that set will not display properly when present in an SVG, and will fire a warning when building the PDF. Luckily, Inkscape has an "Object to path" function built in, which will convert text to a raw path, allowing these characters to be supported. Please ensure that you build the PDF before submitting any new images, particularly with non-standard characters, in order to catch such errors.