* This only needs to be different from `this` in the case of image views when
using descriptor buffers, so automatically set it to this by default and
overwrite only in that case.
* This is almost completely worthless as it seems at least NV and amdvlk both
actually crash the GPU on this instruction, meaning there's no way to get it
to the shader debugger. But on other drivers like radv, or maybe if this is
fixed in future, this will be useful.
* For this reason it also can't be tested automatically.
* This prevents us from adding non-compute states such as PIXEL_SHADER_RESOURCE
from the CPU last-known state when transitioning resources before an indirect
patch on a command buffer.
VK_EXT_fragment_density_map2 and VK_QCOM_fragment_density_map_offset depend on VK_EXT_fragment_density_map, so if RD disables it due to lack of VkPhysicalDeviceFragmentDensityMapFeaturesEXT::fragmentDensityMapNonSubsampledImages support (common on Mali) it needs to disable the others as well.
* We shouldn't require 'pure virtual' functions in CaptureViewer implementations
in python, so detect when the derived class methods point to the base class
pass-throughs, and skip them in that case.
* Unfortunately the new upcoming debian has made the really poor decision to
actively *delete* the pcre package, breaking any programs depending on it even
at build time. As far as I can see it's still available in most other common
distributions.
* Users could easily build it themselves but would have to install it system
wide for it to be picked up. This kind of dependency absolutely should not be
something the build system has to set up itself but when distributions make
poor choices we have little choice but to adapt somehow.
* Without this, image views created off the swapchain images would destroy the
actual underlying resource info when the view is destroyed, thinking that it
has its own unique copy.
baldurk