Tools that run on your own data

PM4 command decoder GPU

The CPU records work for the PS5 GPU — it fills a ring buffer with PM4 packets and the command processor eats them. Every draw, every register write, every fence is one of these. Paste dwords from a command-buffer dump, or encode a packet from scratch and watch the bit layout fall out.

Module inspector Guest

Sony modules are ELF files that a normal ELF reader refuses to load: the type is ET_SCE_* and the import/export machinery lives in a proprietary PT_OS_DYNLIBDATA segment instead of the standard place. Drop one of your own modules in and see exactly what the runtime linker sees.

Log triage Host

A failing run produces thousands of lines and maybe five that matter. This groups them by what they mean for you — unresolved imports are work you could pick up, unknown packets point at the GPU decoder, errors read best from the bottom. Point it at the log from a title that does not boot and you have a to-do list.

Module & library id encoder Guest

Symbol names in a PS5 module look like pt2fEBBpEJk#A#A. Those trailing tokens are 16-bit module and library ids squeezed into a 64-symbol alphabet. This is the emulator's encoder, transcribed exactly — drag the slider and watch which branch the value takes.

Appendix · C++ primer tools

The three ideas the C++ appendix keeps returning to, as tools: what the compiler does to a struct, what the JIT writes into a machine-code stub, and what a crash log is actually telling you. No artifacts needed — each one demos itself.

Struct layout lab C++

Padding is the difference between the size you guess and the size the compiler produces. Build a struct, watch the alignment padding appear byte by byte, flip #pragma pack(1) and watch it vanish — then assert the exact size the way static_assert(sizeof(...)) does in memory.h.

Machine-code patch calculator C++

The emulator writes its own import stubs, and every relative jump or call needs a displacement computed by hand: target − rip, stored little-endian. Give it a rip and a target and watch the exact bytes jit.h would write — including when the target is too far away.

Crash-log reader C++

Guest code runs natively, so a game crash is a real host exception — and the emulator writes a forensic dump about it. Paste one in and it becomes a page: what faulted, on which register, called from where. The faulting address is a symptom; the stack trace at the bottom is the cause.

Appendix · shaders

Inspect supported input-ISA encodings, summarize compiler artifacts, and unpack buffer and sampler descriptors. These readers expose evidence; they do not compile or execute shaders.

RDNA2 ISA word decoder GPU

A shader is just 32-bit words until something decodes them. Inspect base scalar/vector ALU encodings and their literal words using fields from ShaderDecoder.cpp. Extended, modifier and memory families stop with a scope message. This is a field inspector, not a complete disassembler.

Shader artifact reader GPU

With --graphics-debug-dump true, the pinned renderer saves input ISA as _Shaders/original/*.bin and generated SPIR-V as _Shaders/*.spv. Shader logging adds decoded ISA and IR to the run log. Import a decoded excerpt, binary artifact, or externally produced .spvasm to inspect its structure.

Buffer & sampler descriptor decoder GPU

Every buffer_load and every image_sample reads its parameters from a descriptor in the shader resource table. Give a V# (buffer) or an S# (sampler) its four dwords and read back the address, stride, count, format — or the filtering rules — using shaderBindings.h. A T# is an eight-dword image descriptor and is outside this tool’s scope.

Don't have artifacts yet?

From your KytyPS5 checkout, use a title configured for your build. Substitute your executable path if it differs from this example; see Building, linking & debugging:

.\_Build\windows-prod\kyty_emulator.exe --game "<your title>" `
  --printf-direction File --printf-output-file _kyty.txt `
  --redzone --command-buffer-dump true --graphics-debug-dump true `
  --shader-log-direction File --shader-log-folder _Shaders

Paths are relative to the emulator’s working directory. Shaders are saved when those paths execute; a failed or cached run may not produce every artifact. Command-buffer dumps and _kyty.txt can be inspected above. Use spirv-dis input.spv -o output.spvasm if SPIRV-Tools is installed. Each reader states its limits; files remain local to your browser.