github Senaxx/KytyPS5 KytyPS5-2026-11-16-5422223

47 minutes ago

KytyPS5 for Marvel's Wolverine (PPSA03671)

A Wolverine build of KytyPS5, forked from KytyPS5/KytyPS5. Upstream's work is all in it up to 2026-11-12; upstream's 35 newer commits are not in it yet.

Requirements

  • Marvel's Wolverine version 1.05 (01.001.005). Other versions aren't supported.
  • A Vulkan GPU with at least 8 GB of video memory. Tested on NVIDIA. Support for AMD RDNA2 is included but untested here.
  • Start wolverine_launcher.exe, not launcher.exe. It turns on readback, tessellation and red-zone protection for the game, and it precompiles the shaders. Choose the game folder (the one with eboot.bin and sce_sys) and press Play.

How it runs

  • PS5 Pro mode with FSR 3.1 and 2x frame generation is the default. On the Wolverine launcher's Graphics page you can turn frame generation off or upscale with NVIDIA DLSS instead (an RTX card and your own nvngx_dlss.dll; no frame generation with DLSS yet).
  • Shaders are precompiled before you play. The first Play on a new graphics card, driver or hints version builds the shipped shader hints (v31) first, which takes a few minutes. After that, the game compiles far less while you play.

What this build adds to KytyPS5

  • PS5 Pro mode with AMD FSR 3.1 upscaling and 2x frame generation, on by default, with a render-resolution setting.
  • NVIDIA DLSS upscaling as an option.
  • The Wolverine launcher, which sets the game's options and precompiles shaders before the first Play.
  • Shipped shader hints (v31) for version 1.05, and pipelines built ahead of their draws, so far fewer compile stutters in play.
  • Bindless textures: the game's descriptor heap is mirrored into one bindless image heap.
  • Texture streaming into sparse images, tuned buffer and texture caches, and textures freed when video memory runs critically low.
  • A faster renderer: command buffers recorded on their own thread, cheaper draws, and GPU-made draw arguments read without stalls.
  • Less RAM: guest memory is committed on first touch.
  • Audio: ATRAC9 controller sounds (vgmstream's decoder) and multistream Opus.
  • Game hooks for 1.05: render step, physics step, geometry pool and ray-tracing check.
  • AMD RDNA2 support, contributed by Mac.
  • Compute shader derivatives and compute stores through descriptor tables.
  • Safer saves: a save stays intact when the emulator closes in the middle of saving.
  • GPU choice: without a chosen card, the one with the most video memory that has every needed feature.
  • Release builds with profile-guided optimisation, for Windows, Linux and macOS.

Fixed in this release

  • Slow-motion moments (cinematics, takedowns, mortar hits) no longer play slower than the game intends. The game's slow motion is now applied once, not twice.
  • Fixed a crash in the docks chase: the graphics device was lost after about a minute, because a depth image was smaller than the pass drawing into it.
  • Much less slowdown while a smoke trail is in view on the docks path to the lumberyard. Its two effect programs now look up only the textures they use, instead of searching all of them every draw.
  • Fewer out-of-memory stops: saving the shader pipeline cache (every 5 minutes and at exit) no longer needs about 1.2 GB of extra memory.
  • Shader hints v31: more places recorded, so fewer stutters after the precompile.
  • Stability and memory fixes from a code audit:
    • FSR 3.1 frame generation frees replaced contexts and HUD-less images only after the GPU is done with them.
    • An FSR 3.1 or DLSS context that fails to create is tried again on the next frame.
    • The emulator starts a new pool when its pool of shader resource sets fills up, instead of exiting.
    • A new emulator build precompiles again before the first Play.
    • Closing the launcher no longer kills a precompile that is still saving. An interrupted precompile isn't taken as finished.
    • When video memory runs critically low, textures the GPU wrote are saved back and freed.
    • Without a chosen graphics card, the one with the most video memory is used, skipping cards that lack required features.

Known issues

  • The frame rate drops when a fight's effects pile up (for example at the Trask Outpost fight). The cost is the emulator's per-draw setup on its GPU thread, not the graphics card.
  • A fast camera turn can briefly drop the frame rate in some places at the docks.
  • Ray-traced passes are skipped, so glass and indirect light can look wrong.

Don't miss a new KytyPS5 release

NewReleases is sending notifications on new releases.