Re: [PATCH v4 0/1] MR632: vkd3d: Implement d3d12_command_list_OMSetDepthBounds()

[Giovanni Mascellani (＠giomasce)]

> We probably should, but I think we're also allowed to just clamp to [0, 1]. It's not immediately clear to me whether a corresponding caps bit exists for this in d3d12.

If, as it seems, there isn't one, then I think `DepthBoundsTestSupported` should be intended as advertising support for an unrestricted range, so shouldn't be set unless we're able to uphold to that promise (i.e., `VK_EXT_depth_range_unrestricted` is available). Why is clamping to [0, 1] a good solution? The application is likely to misrender if we change the requested parameters under its feet.