It might be true that this feature should technically not be required, but since there's no way to determine the exact UAV format accurately at compile time, I don't really see how to work around that without ruining performance at draw time.
Just assuming that a UAV with a float return type is R32_FLOAT when a load instruction is used sounds like an incorrect assumption.
09151f36168bad2630a3c642a8f4401a65e87ed5 should work on GPUs which do not support this capability as long as the application does not use typed loads for any other format than those three.
Nothing extracted yet.
DXVK requires
StorageImageReadWithoutFormatfor feature 11_0 support. It shouldn't be required. Only the following 3 formats require the UAV typed load support in the 11_0 feature level:R32_UINT,R32_SINT,R32_FLOAT.