Repository navigation
Releases
KytyPS5-Frank v0.4
Fourth test build. Experimental, no support promised.
Built for Marvel's Wolverine (PPSA03671, 01.001.005). Tested only on an RTX 5090 Laptop (Core Ultra 9 275HX, 64 GB).
Frame rate (RTX 5090 Laptop, Performance mode)
| Scene (RTX 5090 Laptop, Performance mode) | Typical FPS | Lowest 1-second average |
|---|---|---|
| Title screen (with a save) | 21–25 | 21 |
| Opening cinematic, first shot | 49–53 | 49 |
| Opening cinematic, the rest | 28–38 | 9 (at scene cuts) |
| First gameplay, Trask Outpost (jungle at night, rain) | 18–21 | 10 |
Measured with v0.4 on the test laptop (new game, first start with the shipped shader list). The jungle gameplay is the limit right now: the emulator's GPU thread is at its limit there, and that is what the next versions go after.
Target is still 60 FPS in Performance mode.
New in v0.4
Shader compile stutter: mostly gone, even on a first play
- The download includes a shader list for Wolverine (
_ShaderList, recorded while playing plus shaders predicted from the game files; it contains shader code taken from the game). At the first start the emulator builds everything in it before the title screen ("Preparing pipelines"). The first launch takes a long time (about 45–50 minutes on the test laptop) and writes a large cache next to the emulator; if it's interrupted it continues where it stopped, and Play.bat restarts it after a crash. - In a 10-minute cold run of the opening and the first gameplay, 7 shaders still compiled during play (it was 875 in a 40-minute session before this list), each taking a few milliseconds. A restart compiled nothing. The first play can still stutter a little in places the list doesn't cover, and it gets smoother the more you play: each shader is compiled once and kept.
- The shipped list is its own read-only file (
list.bin); your own recordings go toledger.binand are never overwritten by an update. - Recordings made by older builds are converted at startup instead of being thrown away.
- Pipelines are built from graphics pipeline libraries (
VK_EXT_graphics_pipeline_library): one piece per shader stage, compiled ahead and linked in microseconds when a draw needs a new combination. The pieces a shader needs are prepared ahead of its first draw. Optimized versions are built in the background and swapped in. - Compute pipelines and the particle pipelines are built before play too.
- Fewer shader variants: state that used to create a new shader (viewport, colour export mapping, buffer formats and strides, texture class, 2D vs array vs cube vs 3D textures) is now passed per draw.
- First start options in Play.bat: wait for everything (default), a shorter wait (the driver part finishes in the background), or no wait (stutters).
Picture and window
- Correct aspect ratio: the game's 16:9 picture keeps its shape, with black bars on other screens, instead of being stretched (
KYTY_KEEP_ASPECT=0stretches it again). - Full screen: F11 or Alt+Enter switches to borderless full screen (no title bar, no taskbar); Play.bat has an option to always start in full screen.
- The "Shaders ready" box shows on the title screen and disappears 30 seconds after the startup (
KYTY_READY_PANEL_SECONDS).
Faster
- Multi-draw packets are replayed as one host draw again; a diagnostic switch had been silently turning this off.
- GPU readbacks run on the copy engine instead of sharing the graphics queue (about +15%).
- Barriers merged between back-to-back draws and dispatches.
- Lazy release of read pages, exact per-draw work, batched syncs of tracked bindings (a few % each).
- Faster range checks in busy areas (one function went from 27% to 1% of the GPU thread).
- 3-second stalls fixed: the window title update waited on the main thread while it slept.
- Push constants raised to 256 bytes on cards that offer it.
Fixed
- The "device lost" crash every 20–40 minutes (the known issue in v0.3; 6 of 6 long unattended runs clean since). A bindless texture slot could be reused while the GPU still read the old image. Slots now wait for the GPU before they change.
- Holes (hex-shaped gaps) in Wolverine's skin. Wave32 compute and mesh shaders now treat EXEC/VCC branches as uniform across the wave, like the hardware.
- Flickering decals, dirt and cracks in every environment. The indirect multi-draw call left out the draw index, so 4 decals of a packet read the same record.
- Textures and enemies turning into black silhouettes after ~25 minutes (bindless slots ran out). Slot reuse is on, and a double-free it exposed is fixed.
- Exploded, half-black character bodies.
- Crash in the upgrade menu (a stencil buffer taken for a colour image).
- Crash after ~45 minutes of play: the game touched memory a queued map hadn't reached yet.
- Game stopped at "Reached end of initial game content installed" (PS5 PlayGo files weren't recognized).
- Texture gathers with an explicit mip level read level 0.
DS_READ/WRITE_ADDTID_B32ignored the instruction offset.- Memory: textures are trimmed at 85% of your card's budget instead of running out; freed GPU memory is capped while it waits to be reused.
- Rare multi-pass depth mismatches (position output is now invariant).
- Out-of-range reads in the shader decoder on corrupt code.
- Log spam: the video-out mode line is printed only when the mode changes.
Diagnostics (off unless asked for): GPU-fault reports name the driver's address map, the last draws and their bindings; in-emulator pixel and buffer probes; shader creation log; frame-floor statistics; KYTY_HITCH_COST_MS names where the time of a long frame went.
Known issues
- Short hitches (100–250 ms) when a new area or a lot of new content appears, also on a restart. They come from the emulator's GPU thread being at its limit, not from shader compiles; next on the list.
- Tested only on Wolverine and an NVIDIA RTX 5090 Laptop. Nothing new for AMD in this version.
- Caches are per GPU and driver: a driver update or a different GPU means a new first-launch warm-up.
- The first launch writes a large cache (about 25 GB on the test laptop). Set the NVIDIA shader cache size to Unlimited (NVIDIA Control Panel > Manage 3D settings). Delete the v0.3 cache folders (
_ShaderCache,_PipelineCache) before the first start. - A rare GPU hang in a chain of compute shaders is still open (seen once in a 16-minute session).
- Cards with 16 GB or less will run with texture trimming much of the time (the jungle gameplay uses 15–17 GB here).
- Occasional freeze in some scene changes (reported in v0.3): not seen in the v0.4 test runs, not confirmed fixed. Restarting gets past it.
- The blue scent trail in the sewer area still doesn't draw.
- Red squares instead of some particles: still worked around (since v0.2), root cause open.
- Still below 60 FPS in gameplay.
How to run
- Unzip
KytyPS5-Frank-v0.4-win64.zip. If you used v0.3, delete its_ShaderCacheand_PipelineCachefolders. - Open
Play.bat, setGAMEto your game folder (the one witheboot.bin). - Double-click
Play.batand let the first start finish "Preparing pipelines".
Needs: 64-bit Windows 10/11, a CPU with AVX2 (Intel Haswell from 2013 or AMD Zen, and newer), a Vulkan 1.3 GPU with a recent driver, and plenty of free disk space for the shader cache.
You need your own legally dumped copy of the game. No game files are included apart from the shader list described above. Keyboard and controller mapping, full screen and settings are in README.txt and in the README, along with status, known issues and how to help.
KytyPS5-Frank v0.3
Third test build. Experimental, no support promised.
New:
- Faster, most of all when turning the camera. On the test laptop (RTX 5090 Laptop), spinning the camera on the first rooftop went from about 13 FPS to about 25, and the drops to single digits while turning are gone. Standing still went from about 16–20 to 19–23 FPS, depending on the area.
- Freeze when loading some saves fixed (the sewer area). The NVIDIA driver never finishes compiling one shader there; the game now skips it instead of freezing. Side effect: the blue scent trail in that area doesn't show yet.
- Safety net for one kind of GPU hang. A broken compute job that would run forever is now skipped instead of stopping the GPU.
- Video memory plan follows your card's own VRAM instead of assuming 16 GB, which should help cards with less.
- One more "unsupported depth" stop fixed (write-only depth targets).
Needs: 64-bit Windows 10/11, a CPU with AVX2 (Intel Haswell from 2013 or AMD Zen, and newer), a Vulkan 1.3 GPU with a recent driver.
How to run: unzip, open Play.bat in a text editor, set GAME to the folder of your own legally dumped game (the one with eboot.bin), then double-click Play.bat. No games or system files are included.
Tested only with Marvel's Wolverine on an RTX 5090 Laptop. Status, known issues and how to help are in the README.
KytyPS5-Frank v0.2
Second test build. Experimental, no support promised.
New:
- Red squares and streaks instead of particles fixed (title screen, rain, embers).
- AMD: black window fixed (presents with Fifo instead of Mailbox on AMD GPUs).
- Depth-to-color copies (from upstream KytyPS5). May fix the "unsupported depth register state" stop some AMD users hit at the Sony logo. If you still hit it, please send your
kyty_log.txt: it now names the exact setting. - One cause of the GPU hang ~20 s into gameplay fixed. Another rare GPU crash is still open.
Needs: 64-bit Windows 10/11, a CPU with AVX2 (Intel Haswell from 2013 or AMD Zen, and newer), a Vulkan 1.3 GPU with a recent driver.
How to run: unzip, open Play.bat in a text editor, set GAME to the folder of your own legally dumped game (the one with eboot.bin), then double-click Play.bat. No games or system files are included.
Tested only with Marvel's Wolverine on an RTX 5090 Laptop. Status, known issues and how to help are in the README.
KytyPS5-Frank v0.1
First test build. Experimental, no support promised.
Needs: 64-bit Windows 10/11, a CPU with AVX2 (Intel Haswell from 2013 or AMD Zen, and newer), a Vulkan 1.3 GPU with a recent driver.
How to run: unzip, open Play.bat in a text editor, set GAME to the folder of your own legally dumped game (the one with eboot.bin), then double-click Play.bat. No games or system files are included.
Tested only with Marvel's Wolverine on an RTX 5090 Laptop. Status, known issues and how to help are in the README.