You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So that the range [0.0f,1.0f] is evenly distributed among uint8_t values, all use of / 255.0f should be / std::nextafter(256.0f, 0.0f) (which will equate to 255.99...f).
DXGI FLOAT and Vulkan UFLOAT and SFLOAT aren't normalized, so source values should be clamped to [0.0f, 1.0f]. Otherwise float values that exceed the range [0, 1] will probably look like noise and maybe a colorful rainbow.
For true representation of non-normalized floating-point components, it may be valuable to support an HDR image format for screenshots and for dump-resources like .hdr (Radiance HDR) format.
The text was updated successfully, but these errors were encountered:
bradgrantham-lunarg
added
P2
A high-priority code maintenance issue or a functional problem that is recoverable or not a crash.
replay
Issue with replay (capture was successful)
labels
Oct 7, 2024
So that the range
[0.0f,1.0f]
is evenly distributed amonguint8_t
values, all use of/ 255.0f
should be/ std::nextafter(256.0f, 0.0f)
(which will equate to 255.99...f).DXGI
FLOAT
and VulkanUFLOAT
andSFLOAT
aren't normalized, so source values should be clamped to[0.0f, 1.0f]
. Otherwise float values that exceed the range [0, 1] will probably look like noise and maybe a colorful rainbow.For true representation of non-normalized floating-point components, it may be valuable to support an HDR image format for screenshots and for dump-resources like
.hdr
(Radiance HDR) format.The text was updated successfully, but these errors were encountered: