* When we detect a new version of Android and a 64-bit device where the 32-bit
version of RenderDoc fails to install completely, ignore this and don't warn
the user about it.
* Prefer vendor-neutral extension aliases for enums over vendor-specific.
* When disassembling opcodes with optional parameters, only include the
parameters when present.
* Descriptor heap tier limits are not very useful as even tier 3 might be as
limited as tier 2. Previously expanding a small amount was safe but newer NV
drivers or systems seem to have stricter limits than before.
* When we're sourcing from our own texture we don't want to bring in any
typecast to unorm/uint/etc from the original texture's view. This already
happens for the main display but we also need to do that for the thumbnail
context.
This adds the next step toward D3D12 pixel history, which is mostly
the generic action callback that is used for other replays later
(similar to how Vulkan pixel history operates).
This adds some of the D3D12 pixel history framework, with creation
of resources that will be needed during pixel history, and a helper
function and shader to copy pixels from MSAA resources.
Fixes rare problem of current draw not displaying when switching from Stencil overlay to None overlay and the current draw uses the stencil buffer contents
* Worst case this is just as invalid as an application, if it uses a totally
bogus VA. However in D3D12 it is apparently valid to refer to VAs out of
bounds of any resource as long as it's within bounds of an underlying heap. To
handle this without serialising VAs as Heap+offset we instead just allow the
address lookup to run out of bounds and pick the next lowest buffer. If the
offset is greater than the buffer size then we're probably no worse than the
application.
In replay/entry_points.cpp RENDERDOC_RunFunctionalTests(..), it uses a simple char-replacement algorithm for finding the Python modules depending on the Python minor version.
Unfortunately that mechanism relies on there being only a single character to replace which doesn't work once we reach double figures.
* If we only garbage collect after a successful create, applications which
deliberately leak state objects and only free them when they see a failed
create will not have a change to garbage collect.
baldurk