* Sometimes fxc gives an error about this -
error X4576: Non system-generated input signature parameter () cannot appear after a system generated value.
* There doesn't seem to be a documented way to know how/when this is important,
but unfortunately in some cases SV values can take up registers and affect
register packing so we can't always omit them. Here for primitive ID as long
as it was previously declared mid-inputs, we allow it to be declared there as
normal to preserve interface matching.
* If the overall preview widget doesn't resize but the thumbnail does because
the preview text label has changed in size, we should emit a resize event so
the thumbnail can be redrawn.
* This avoids unnecessary remapping in the case of unknown queue flag bits or
properties, e.g. if two queues look like transfer queues because one has a new
bit. If the user picks the second 'transfer' queue we shouldn't try to remap
it to the first 'transfer' queue.
* This is only relevant when using a custom shader since otherwise nothing is
'updated', though could also affect overlays potentially. If we don't then the
custom shader texture may not have been re-rendered before we fetch the
histogram data and we'll get stale information.
Errors related to collecting NVIDIA hardware counters are now shown in the
"Errors and Warnings" window of the Renderdoc UI. Previously, these errors were
only visible in stderr. This includes errors for device compatibility, resource
availability, and insufficient privileges.
* These were previously hidden by default since they generate a fair amount of
noise in the disassembly which is not neccessarily directly useful.
* The problem is that DebugValues are steppable and so will generate an
instruction in the debugging, but without a disassembly line you can have two
different 'instructions' on the same disassembly line but with different
source lines:
> DebugLine 100
> DebugValue ...
> DebugLine 101
> OpSomething ...
In this case the DebugValue and OpSomething will both have the same disassembly line, but different source lines. This means it is impossible to reliably place a disassembly breakpoint and know which instruction to stop on, and produces some odd effects when stepping in asm (it will step to the DebugValue then the OpSomething and not visibly move).
* Overall the reduction in readability is worth this fix, especially considering
that when debug info is present is exactly when people are least likely to be
using the disassembly at all.
baldurk