mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
0e3ceb7574
* Update release number to 117.
Github Issues:
* Add ename:VK_STENCIL_FACE_FRONT_AND_BACK for naming consistency, and
alias the old ename:VK_STENCIL_FRONT_AND_BACK for backwards
compatibility (public issue 991).
* Fix minor issues with valid usage statements for
flink:vkCreateFramebuffer, slink:VkFramebufferCreateInfo, and
slink:VkRenderPassBeginInfo when the `<<VK_KHR_imageless_framebuffer>>`
extension is enabled (public issue 998).
* Clarify the subpass dependency requirement in the
<<renderpass-layout-transitions>> section to eliminate the need for a
subpass dependency for either the same or different layouts as long as
they're both read-only (relates to
https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/948).
Internal Issues:
* Document that <<extendingvulkan-compatibility-promotion, backwards
compatibility aliases are not promoted>> as part of promoting an
extension (internal issue 1677).
* Update VK_ANDROID_native_buffer extension to spec version 8 (internal
issue 1753).
* Add missing section to the <<VK_KHR_shader_controls_v4_incompatibility,
VK_KHR_shader_float_controls>> extension appendix describing
the reason for the breaking API change in version 4 of the extension,
and correct the version to 4 in `vk.xml` (internal merge request
3275).
* Add valid usage statements to slink:VkAccelerationStructureInfoNV
requiring the ename:VK_BUFFER_USAGE_RAY_TRACING_BIT_NV usage flag for
buffers used in acceleration structure building.
New Extensions:
* `<<VK_EXT_line_rasterization>>`
* `<<VK_EXT_texture_compression_astc_hdr>>`
* `<<VK_EXT_index_type_uint8>>`
= 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.