When doing history on depth targts, for ClearDepthStencil events, generate the DepthStencilView dimension from the depth target resource description instead of using the ResourceUsage view member.
Don't early ignore events by using the ResourceUsage view parameter, test the event for any modification.
* The address is 64-byte aligned so shifted by 6, and the range 16-byte aligned
so shifted by 4.
* The max UBO range is still 64k so 13 bits is 1 more than needed to represent
all ranges.
* This would generally only come up with gl_PerVertex, and was hidden before
because gl_Position is the first member. It likely would also reproduce if a
user had a struct output from the mesh shader.
* This doesn't trigger a rebuild if nothing else has changed, but it does mean
these files can't be customised without going through the build process as
they'll be overwritten on any rebuild. It looks like IfDifferent doesn't work
properly or maybe isn't available on all msbuild versions.
* Remove use of newer STL classes like std::filesystem, std::variant and
std::optional.
* Do not use inline variables - the only instance is also static constexpr
* Explicitly initialise std::array variables with type and size (also add extra
{}s to appease an old clang warning)
* Work around old libstdc++ bug with move assignment and non-assignable
allocators
* Remove redundant constexpr that warns on older compilers
* Remove use of declaration-inside-if statements
Use the cached Texture Description for all other Textures which matches the behaviour of GetTextureData()
When saving a texture when a custom visualisation shader is in use:
- fixes a crash when saving as HDR or EXT
- fixes incorrect image saved to DDS
The Vulkan specification allows to have uninitialized fields in
VkDescriptorImageInfo based on descriptor type. Such fields should not
be touched by the implementation (which includes drivers, validation
layers and tools).
FillInputVariable : can be called from any thread but the input variable data must be marked as read only
Made the input variable data containers private with a writable accessor
Mark the input variable data as read only just before calling BeginDebug
* It's impossible to distinguish a separate TEXCOORD0 and TEXCOORD1 from an
array at TEXCOORD0. However making this an array by that same logic is fine.
We can't make an array though if there is another element in between they must
be contiguous.
* If immutable samplers are used the sampler parameter of a descriptor update
could be garbage. Checked for elsewhere but not handled in descriptor update
template unwrap.
Jake Turner