Allocate the code and block LUTs as one block on system initialize, covering
at least 8MB of RAM, and EXP1 only when a PIO device is enabled.
Reallocate when a state changes the RAM size or the PIO device changes.
Fixes it getting lost when restarting with a normal state, or getting
disconnected from the actual file when there is no media and we are just
running ps-exe.
Register an ID3D12InfoQueue1 message callback when the debug device is
enabled, so that validation messages end up in the log, similar to the
Vulkan debug messenger. Useful for users without a debugger attached, and
for the regression tester.
Also drop break-on-error/warning, breakpoints can be placed in the
callback instead.
When allocating behind the GPU, the full space up to the GPU position was
handed out. If a caller committed all of it (e.g. vertex batches that fill
the mapped space), the offset would equal the GPU position, which the
allocator interprets as the GPU having caught up, and subsequent
allocations would overwrite data still referenced by the current command
list. Reserve one byte, matching the Vulkan stream buffer.
Fixes corruption in Jumping Flash in the regression tester, where command
lists can span hundreds of frames due to presentation being skipped.
This is a hack to provide a better experience, because users like to
report this as a "bug" when it is in fact console behaviour.
It is disabled in safe mode.
Some games never initialise the SPU's reverb on startup, they only clear
the reverb master enable bit in SPUCNT. The shell's reverb configuration,
work area and output volume are left in place, and with the master enable
clear the reverb unit stops writing to its buffer but still reads it and
mixes it into the output. Whatever was in the buffer when the game took
over loops for the rest of the session.
This also happens on console. How loud the echo is depends on how far the
shell's reverb had decayed before the game cleared the enable bit, i.e.
how long the BIOS takes to read the executable, so faster CD-ROM read and
seek speeds make it worse. It will also be less apparent on older consoles
with more drive wear. It does not happen with fast boot, as the shell
never runs and the SPU is still in its power-on state.
The new option and ResetSPUOnGameStart trait reset the SPU when the game's
entry point is reached, which gives the same SPU state as a fast boot.