Open billhollings opened 2 years ago
It should be theoretically possible to solve this by inserting MTLFence
s everywhere the render pass declares a memory dependency. We need to do this anyway, in order to support MTLHazardTrackingModeUntracked
.
Hmm... Looking at this more closely, I'm now starting to think this is more of a rendering accuracy issue. Only a few pixels in the result are off. I wonder now if this isn't one where we'd need to get a waiver.
Some CTS tests fail with subpass dependencies that depend on late fragment depth testing.
This might be fixable with effort within the implementations.
In the meantime, these use cases can be disabled in CTS and reported as Not Supported, by adding a
VkPhysicalDevicePortabilitySubsetFeaturesKHR:: subpassDependencyLateFragmentTests
capability.This affects 9 CTS tests: