mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-22 20:32:19 +00:00
features.txt: Fix latexmath syntax
Using "latexmath[...]" instead of "latexmath:[...]" causes the entire line of text to simply vanish.
This commit is contained in:
parent
6cb766ac79
commit
961010879b
@ -917,14 +917,14 @@ properties of the physical device:
|
||||
* [[features-limits-subTexelPrecisionBits]] pname:subTexelPrecisionBits is
|
||||
the number of bits of precision in the division along an axis of an
|
||||
image used for minification and magnification filters.
|
||||
latexmath[$2^\mathit{subTexelPrecisionBits}$] is the actual number of
|
||||
latexmath:[$2^\mathit{subTexelPrecisionBits}$] is the actual number of
|
||||
divisions along each axis of the image represented. The filtering
|
||||
hardware will snap to these locations when computing the filtered
|
||||
results.
|
||||
* [[features-limits-mipmapPrecisionBits]] pname:mipmapPrecisionBits is the
|
||||
number of bits of division that the LOD calculation for mipmap fetching
|
||||
get snapped to when determining the contribution from each miplevel to
|
||||
the mip filtered results. latexmath[$2^\mathit{mipmapPrecisionBits}$] is
|
||||
the mip filtered results. latexmath:[$2^\mathit{mipmapPrecisionBits}$] is
|
||||
the actual number of divisions.
|
||||
+
|
||||
--
|
||||
@ -952,7 +952,7 @@ different equations in the spec).
|
||||
the code:Bias operand of image sampling operations in shader modules (or
|
||||
0 if no code:Bias operand is provided to an image sampling operation)
|
||||
are clamped to the range
|
||||
latexmath[$[-\mathit{maxSamplerLodBias},+\mathit{maxSamplerLodBias}]$].
|
||||
latexmath:[$[-\mathit{maxSamplerLodBias},+\mathit{maxSamplerLodBias}]$].
|
||||
See <<samplers-mipLodBias>>.
|
||||
* [[features-limits-maxSamplerAnisotropy]] pname:maxSamplerAnisotropy is
|
||||
the maximum degree of sampler anisotropy. The maximum degree of
|
||||
@ -972,7 +972,7 @@ different equations in the spec).
|
||||
<<vertexpostproc-viewport,Controlling the Viewport>>.
|
||||
* [[features-limits-viewportboundsrange]] pname:viewportBoundsRange[2] is
|
||||
the viewport bounds range
|
||||
latexmath[$[\mathit{minimum},\mathit{maximum}]$]. See
|
||||
latexmath:[$[\mathit{minimum},\mathit{maximum}]$]. See
|
||||
<<vertexpostproc-viewport,Controlling the Viewport>>.
|
||||
* [[features-limits-viewportSubPixelBits]] pname:viewportSubPixelBits is
|
||||
the number of bits of subpixel precision for viewport bounds. The
|
||||
@ -1126,11 +1126,11 @@ different equations in the spec).
|
||||
least 2, and levels must: be spread evenly over the range, with at least
|
||||
one level at 1.0, and another at 0.0. See <<devsandqueues-priority>>.
|
||||
* [[features-limits-pointSizeRange]] pname:pointSizeRange[2] is the range
|
||||
latexmath[$[\mathit{minimum},\mathit{maximum}]$] of supported sizes for
|
||||
latexmath:[$[\mathit{minimum},\mathit{maximum}]$] of supported sizes for
|
||||
points. Values written to variables decorated with the code:PointSize
|
||||
built-in decoration are clamped to this range.
|
||||
* [[features-limits-lineWidthRange]] pname:lineWidthRange[2] is the range
|
||||
latexmath[$[\mathit{minimum},\mathit{maximum}]$] of supported widths for
|
||||
latexmath:[$[\mathit{minimum},\mathit{maximum}]$] of supported widths for
|
||||
lines. Values specified by the pname:lineWidth member of the
|
||||
sname:VkPipelineRasterizationStateCreateInfo or the pname:lineWidth
|
||||
parameter to fname:vkCmdSetLineWidth are clamped to this range.
|
||||
|
Loading…
x
Reference in New Issue
Block a user