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
{{ message }}
This repository has been archived by the owner on Aug 1, 2019. It is now read-only.
The D3D12 debug layer currently fires a lot of warnings about there not being default clear values. This is a feature that enhances the performance of clearing by setting it up front.
I have noticed that Vulkan apparently has the same warning / feature. It is less clear to me whether Metal does this.
I am opening an issue to consider adding this feature to NXT since it maps pretty directly to a hardware feature and multiple backends can support it.
The text was updated successfully, but these errors were encountered:
Thanks for raising this, default clear values will be important for performance, especially if we decide that the Web facing API has to act as if all resources are set to 0 when allocated.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The D3D12 debug layer currently fires a lot of warnings about there not being default clear values. This is a feature that enhances the performance of clearing by setting it up front.
I have noticed that Vulkan apparently has the same warning / feature. It is less clear to me whether Metal does this.
I am opening an issue to consider adding this feature to NXT since it maps pretty directly to a hardware feature and multiple backends can support it.
The text was updated successfully, but these errors were encountered: