We can add a feature check, but I think the more interesting question is how to prevent this in the future.
All devices that we're ever reasonably going to run any sort of D3D12 content on at all support sparse, these things are going to get overlooked time and time again unless we have some sort of way to emulate the most barebones min-spec-can't-run-any-actual-games type of Vulkan device in such a way that it blows up in an obvious way if we try to use any unsupported features.
Nothing extracted yet.
The
test_tight_resource_alignmenttest case proceeds to create reserved resources without testingTiledResourcesTier, relying on sparse support in the Vulkan driver that might not be present.Turnip's sparse support relies on relatively new kernel functionality. With not-exactly-latest kernels sparse support is not enabled, and this test ends up crashing on an assert inside Turnip.