Repository navigation
Releases
KytyPS5 Yōtei fork v0.1.6
Game version 2.002 only (1.512 still starts but is not tested). All numbers are from the test PC (Ryzen 7 9800X3D,
RTX 5070 Ti 16 GB, 64 GB RAM) in the game's Performance mode, on replays of the same recorded routes.
This release has two parts: A is the v0.1.6 package prepared on 7.11 (never published on its own), B is
everything added after it.
In short
- Town walk: about 14 fps in v0.1.5 → about 16 fps (part A) → about 19-20 fps now (part B). Riding through the
open world near the inn: about 26-27 fps. (Separate measurements on different days, not one side-by-side run.) - Much shorter starts and loads: the shaders are ready in about 4 s instead of 33-35 s after the first start,
"Continue" loads in about 8-9 s instead of about 15 s. - Fewer hitches: no more 1-3 s freezes while walking, far fewer long frames in the first minutes, shorter freezes
at camera cuts in cutscenes. - Bigger shader hints (11,969 shaders, 16,117 pipelines) and a launcher that walks you through the first start.
Part A – the v0.1.6 package (prepared 7.11)
Performance
- Faster town walk: 13.9 → 15.8 fps (+13%), median frame 68-75 → 60-64 ms, worst 1% of frames 88-103 → 82-86 ms.
Many small savings on the emulator's main GPU thread (texture tables refreshed only where they changed), plus a
compiler profile trained on walking.
Fixes
- The 1-3 second stalls while walking are gone. When the game streamed in new data, a dozen of its threads could
spin on one emulator lock at once, and the thread holding it got no CPU time. Waiting threads now back off. - Much better on PCs where reading back from the graphics card is slow. On one tester's i9-12900K + RTX 5090,
reading GPU results back over PCIe ran at ~19 MB/s (about 60× slower than on our test PC) and kept the game near
10 fps. The emulator now times these reads at start and, when they are slow, copies the data through the GPU
instead. The log showsBAR_READS fastorBAR_READS slow;KYTY_BAR_READS=0/=1forces the choice. - No more endless loading spinner on some dumps. The game asks at boot whether the base game is owned; the emulator
now says yes. Thanks to CarRamRod-963 for finding and fixing this. - Missing faces: "Enable readback" (launcher, Graphics & display) is now on by default and is switched on once for
existing settings. Players reported that faces stayed invisible without it. It costs about 2% fps in town; you can
turn it off again.
Launcher and look
- New first steps: import the shader hints, then precompile, then play. Many players skipped the hints and had
hours of stutter. Precompile and Play stay disabled until the hints are imported (Shaders page →
Import hints… →hints\PPSA26344_02.002.000.kyhints), and Play stays disabled until the precompile has
finished. The Play page says which step is next, the Precompile buttons are framed red until the hints' shaders are
ready and green when done, and the help buttons open the player guide at the right page. - New look: shader preparation shows a brush ensō in the top-right corner (also over the loading screen), the
F2 / Shift+F2 panel has brush corners and a brush-stroke frame graph, and the launcher has the brush style. - Shader precompile uses 8 threads by default (was 6).
Part B – added after the v0.1.6 package
Performance
- Town walk about 16 → about 20 fps. The largest step: the graphics card now reads part of the game's per-draw
resource data itself instead of the emulator preparing it for every draw (16.0 → 19.6 fps, +22%, 0 differences in its
checking mode). Smaller measured steps on top: handling of the game's data ring by game frames (+2.4%), no needless
waits on some GPU signals (+1.4%), cheaper resource lookups (+1.5%), a fresh optimisation profile (+3.1%). - Faster in-engine cutscenes. Several of the heaviest cutscene shaders were made cheaper (inlined loads, faster
ray-tracing node lookups, a quicker path for empty format reads): the two largest changes gave about +8.6% and +7.5%
in the second part of the cutscene after the Snake fight. That cutscene now runs at about 11-12 fps in automatic runs
(its heaviest part about 8 fps). - Much faster start. Translated shaders are kept on disk (
_PipelineCache\<title>.reuse, about 416 MB): after the
first start, preparing the shaders takes about 4 s instead of 33-35 s. - Faster "Continue". Loading a save from the main menu takes about 8-9 s instead of about 15 s: the game's graphics
memory is made readable by the card when the game maps it, not later during play. Cost: about 4 GB of pinned system
RAM instead of 1.9 GB (shown as the card's shared memory). - From the main KytyPS5 project: faster kernel semaphores and signal handling (superkeka), a faster GPU page-fault scan
that no longer loses pages past its limit (nmzik).
Fixes
- Fewer hitches in the first minutes of play. Late imports of game memory held the graphics driver for about 50 ms
each and froze the frame; they are now done in larger groups. Frames over 100 ms in the town walk 18 / 11 → 3 / 4, in
the first minute 14 → 5, and fps +5.0%. - Shorter freezes at camera cuts in cutscenes. At a camera cut the game creates and frees about 2,100 small GPU
buffers in one frame; they now share memory blocks instead of each getting its own allocation. The long frames at the
first camera cut of the intro add up to about 1.9-2.8 s instead of about 3.3-3.6 s. About 0.5 s is still left and is
being investigated. - No shader stutter right after starting. At every game start the emulator waits until the prepared shaders are
loaded (the window title shows "preparing shaders N%"; a few seconds after a finished precompile, about 30 s once
after an update). In the town walk afterwards 1 shader was missing instead of 27-40. - Updates keep your shader cache. The caches now depend only on the shader translator's version, not on the whole
emulator file, so later versions that do not change the translator keep the prepared shaders. (This version does
change it: the first start prepares the shaders again once.) - The store of translated shaders may hold up to 4 GB (was 2 GB, which was full and dropped results).
- The GPU clock the game reads through its shaders ran about 25% too fast; it now runs at the right rate (Senaxx).
Shader hints and launcher
- Shader hints: 11,969 shaders and 16,117 pipelines (v0.1.5: 6,880 / 8,001): ours plus a large set a player shared
from far into the game. The precompile takes several minutes (longer on CPUs with fewer cores). - New hints are imported again: the launcher remembers which hints file the first steps were done with; a version
with new hints asks for the import again, so players who did the steps before also get the new shaders. - Default window 1920×1080 for new settings (the game renders at 1080p; a 1280×720 window only made it blurrier).
Saved settings keep their choice. - The performance panel's GPU row works on Windows (it showed "n/a"): it shows how busy the graphics card is with
this game.
Diagnostics
- Texture relocation guard (on by default): after textures are moved to free graphics memory, their old copies are
kept for 10 s and any late use is logged asTEXMOVE_STALE_USE; everyTEXMOVEline has the wall-clock time. No
late use was found in our tests (1,888 moved textures). Cost: no measurable change in fps.KYTY_TEXMOVE_GUARD=0
turns it off. - Diagnostic and measurement tools for developers (off unless enabled).
Known issues
- Checkered, pixelated shadows after a short stutter or a cutscene (issue #11). While a new shader compiles, the
emulator skips the draws that need it for a few frames; an incomplete frame can get into an effect the game carries
from frame to frame. Fix: quit to the main menu and load your save. It is rarer in this version (the shaders are
prepared at the start, the hints cover much more); the proper fix (pipeline libraries) is planned. - Occasional fps drops during play. Sometimes the frame rate drops for a while (for example to about 16 fps near the
end of a town walk); the cause is being investigated. - Graphics memory grows over a long session: watch "Vulkan budget" in Shift+F2; if it gets close to the limit and
the game slows down, save, quit and start again. - Workarounds are still in place (memory read through pointers before it has a buffer, image memory shared by
several images, stencil, colour compression and others): see Known workarounds inREADME-YOTEI.md. - RAM: about 4 GB of RAM is pinned for the card and the shader store holds about 2.2 GB; 32 GB of RAM stays the
recommendation.
When you report a problem: note the time on your screenshot, then Launcher → Advanced → Export bug report, and
attach the zip and the screenshot to an issue.
Thanks to CarRamRod-963, Senaxx, nmzik and superkeka for the changes taken from their work, and to the
player who shared the shader hints.
Download
Download KytyPS5-Yotei-v0.1.6-windows-x64.zip, unpack it into a new folder and copy your _SaveData folder there.
Then follow KytyPS5-Yotei-Player-Guide.pdf: import the hints, let the precompile finish, play.
KytyPS5 Yōtei fork v0.1.5
KytyPS5 Yōtei fork v0.1.5
Game version 2.002 only (1.512 still starts but is not tested).
Highlights
-
The multi-second stutters while walking are gone. When the game streams in new parts of the world, about ten of
its worker threads would hit the same memory-tracking lock in the emulator at once and spin on it. The thread holding
the lock was inside a Windows memory call and could not get CPU time until Windows boosted it, roughly 2.5 seconds,
again and again. Waiting threads now back off instead of spinning. Measured on replays of the same recorded town
walk (Ryzen 7 9800X3D + RTX 5070 Ti, no diagnostics):- average fps while walking: ~10.7 → ~13.1 (+22%);
- stalls longer than 0.5 s: 4–13 per run → 0;
- worst 10-second stretch: 5.5–8 fps → 10.7–12.5 fps;
- open world (night save, 16 min of play): 23.5–24.3 → 25.5 fps, hitches over 1 s 0.47–0.98/min → 0.31/min,
over 2 s 3–8 → 0.
Frame rate is much steadier in town and in the open world; in our play tests cutscenes were smoother too.
-
Texture relocation is on by default. Over a long session the graphics card's memory filled with half-empty blocks
(the "graphics memory grows" known issue of v0.1.4). The emulator now moves textures that are not being written out
of nearly empty memory blocks so whole blocks can be released. This is a first step; the growth is smaller but not
gone, so keep an eye on "Vulkan budget" (Shift+F2) in very long sessions.Please report: texture relocation is new. If you see textures, trees or other objects disappearing,
flickering or turning black, especially after playing for a while or after a cutscene, open an issue with a
screenshot, where it happened and how long you had been playing. -
Fixed a crash with stencil shadows (a copy back into a depth image that had already been deleted).
-
Shader hints for 2.002 extended with the open world: 6,880 shaders and 8,001 pipelines (v0.1.4: 5,417 shaders,
5,865 pipelines, start of the game to the Snake fight). Other areas still compile their shaders the first time you
reach them; if you play further, Launcher → Shaders → Export hints… and send us the file.
Everything since v0.1.4
User-facing:
- Page-manager lock: waiters back off (spin, then yield, then short sleeps) – fixes the walking stutters.
- Texture relocation (
KYTY_TEXMOVE) always on; its switch, check mode and settings removed. - Stencil shadow: no copy back into a deleted depth image (crash fix).
- Shader hints: open-world coverage added (6,880 shaders, 8,001 pipelines).
- README: v0.1.5 hints, texture relocation note.
For developers and testers (all off unless enabled):
KYTY_TEST_PAD_RECORD/KYTY_TEST_PAD_REPLAY: record a play session's pad input and replay it by time from the
start of gameplay, for repeatable measurements while moving.KYTY_TEST_PAD_SCRIPT:SWIPE=gesture on the touch pad (some 2.002 cutscenes wait for a swipe).KYTY_TRACE_PERFno longer runs the memory census (onlyKYTY_TRACE_MEM_CENSUSdoes).- Measurement tools used to find the stutters and to test performance ideas:
KYTY_TRACE_WAIT_SITES,
KYTY_DIAG_SKIP_READBACK,KYTY_DIAG_READS_ASSUME_UNCHANGED,KYTY_DIAG_TABLES_ASSUME_UNCHANGED,
KYTY_DIAG_SKIP_DIRECT_DRAWS,KYTY_DIAG_BIND_REPLAY,KYTY_DIAG_GPU_BURN_AT=draw,KYTY_VMA_BLOCK_MB,
KYTY_TRACE_BLOCK_GROWTH, texture-window counters. - Removed: the memory measurements of the VRAM investigation (per-type census, image sizes, VMA map dumps).
Download
Download KytyPS5-Yotei-v0.1.5-windows-x64.zip, unpack into a new folder and copy your _SaveData there if you want
your saves. The first Play prepares the shaders (a few minutes). Requirements and known issues: README-YOTEI.md
(32 GB RAM recommended).
v0.1.4
KytyPS5 Yōtei fork v0.1.4
From this release on, only game version 2.002 is supported and tested. 1.512 still starts, but it is no longer
tested and no 1.512 shader hints are shipped.
- Volumetric fog, wind trails and fire are drawn on 2.002. The game draws these effects through a combined
tessellation shader whose second half reads values left by the first half; the emulator lost them when splitting
the program. They now show as on the PS5. - No more slowdown in the Snake fight. After the Snake cutscene the frame rate could fall to 5-6 fps and stay
there for minutes (back to 13-17 fps by itself later). The game's largest buffer (523 MB) sat in a kind of graphics
memory the CPU can also reach, and writes into it sometimes ran at bus speed; it now lives in normal graphics memory. - Cutscenes are about 50% faster. The cutscene after the Snake fight: 5.5 → 8.4 fps. The game writes animation
data into memory the graphics card also wrote; the emulator now fetches the card's data for an 8 MB window at once
instead of waiting for the card on each 4 KB page (checked: the same bytes, 0 differences in 4.1 GB). - Shaders are no longer translated again on every start. Some pixel-shader variants were saved without five of
their settings, so every session translated them again (hundreds at each camera cut in cutscenes, stalls of
several seconds). They are saved completely now; the second pass of the same cutscene translates none of them.
Shader hints for 2.002: 5,417 shaders and 5,865 pipelines (v0.1.3: 6,493 shaders, 1,550 pipelines), recorded from
the start of the game to the Snake fight. The shader save format changed in this release, so the older hints could not
be kept. Later areas compile their shaders while you play, with short stutters the first time you reach a new place;
they are saved and the next visit is smooth. If you play further, Launcher → Shaders → Export hints… and send us
the file.
Known issue: graphics memory grows over a long session. Each change of scene, cutscenes most, leaves unused gaps
in the graphics card's memory that the emulator does not reclaim yet (about 12 GB after loading, 13.5-15 GB after
30-60 minutes on a 16 GB card). Near the card's limit the frame rate drops. Watch "Vulkan budget" in the performance
panel (Shift+F2) and restart the game (save, quit, start again) when it gets close to the limit. This is the next
thing we are fixing.
Also slow for now: scenes with a lot of fire (parts of the Snake fight, about 10 fps).
Download KytyPS5-Yotei-v0.1.4-windows-x64.zip, unpack into a new folder and copy your _SaveData there if you want
your saves. The first Play prepares the shaders again (the format changed), a few minutes. Requirements and known
issues: README-YOTEI.md (32 GB RAM recommended).
v0.1.3
KytyPS5 Yōtei fork v0.1.3
- Much less memory pinned for the graphics card. The emulator used to lock ~12 GB of the game's memory in RAM for
the card ("Shared GPU memory" in Task Manager: 13-14 GB) while the card needed only a few hundred MB of it. Now only
the pieces the card actually uses are locked: shared GPU memory drops to ~2 GB, and the emulator takes ~5 GB
less RAM (same cutscene: 33.6 → 28.1 GB on average). This matters most on PCs with 16 GB RAM, where the old
behaviour could crash the game. 32 GB RAM is still recommended: the emulator itself needs ~24-28 GB.- The used pieces are remembered in
_PipelineCache\PPSA26344_<version>.bda_granules, so the next start serves
them from the beginning. In the first session a new place can show something wrong for a single frame when such a
piece is first used.
- The used pieces are remembered in
- Shader hints for 2.002: 6,493 shaders and 1,550 pipelines (v0.1.2: 1,618 shaders, 24 pipelines), from a 2.002
play session (opening scenes). More areas come in the next releases; if you play 2.002, Launcher → Shaders →
Export hints… and send us the file. - Faster first-start shader preparation: the hints import reads only the game's shader packs (~23 GB) instead of
possibly the whole ~200 GB game (2.002: ~3 minutes instead of 30+ on a fast SSD). - "Render at 1080p" is now on by default, on 1.512 and 2.002: the game renders at 1920x1080 also in cutscenes,
where it would go up to 4K (the slowest part of the game in this emulator). You can turn it off on the launcher's
Mods page; the launcher keeps your choice. - Version 1.512: shader hints unchanged (16,960 shaders).
Known on 2.002: volumetric fog and wind trails are not drawn yet (2.002 then also runs faster than 1.512 - that
is the missing effects, not a real gain). We are on it.
Download KytyPS5-Yotei-v0.1.3-windows-x64.zip, unpack into a new folder (copy your _SaveData if you want your
saves). Requirements and known issues: README-YOTEI.md (32 GB RAM recommended).
KytyPS5 Yōtei fork v0.1.2
KytyPS5 Yōtei fork v0.1.2
- Game version 2.002 supported (starts and plays). The first-start shader preparation no longer reads the whole
game when the shader hints don't match your game version (before: up to half an hour on 2.002, it looked hung): the
launcher picks the hints file of your game's version, and a file of another version is refused at once. - Shader hints for 2.002: a first, small list (1,618 shaders; 90% of 2.002's shaders differ from 1.512). It grows
in the next releases from 2.002 play sessions. If you play 2.002, Launcher → Shaders → Export hints… and send us
the file: it helps everyone. - Version 1.512: unchanged (16,960 shaders in its hints).
Download KytyPS5-Yotei-v0.1.2-windows-x64.zip, unpack into a new folder (copy your _SaveData if you want your
saves). Requirements and known issues: see v0.1/v0.1.1 notes and README-YOTEI.md (32 GB RAM recommended).
KytyPS5 Yōtei fork v0.1.1
KytyPS5 Yōtei fork v0.1.1
Fixes from the first day of v0.1:
- AMD GPUs: the emulator no longer stops at start-up with "create bindless descriptor pool failed" (AMD drivers
report a much larger descriptor limit than NVIDIA; the emulator now takes the same amount on every GPU). - Games in a .zar archive: the first-start shader preparation now finds the shaders inside
.zararchives too
(before: "0 of 16960 shaders found"). Folders with non-English characters in their path work as well. - README: 32 GB of RAM is required (16 GB runs out of memory); always start
launcher.exe, not
kyty_emulator.exe, so the shaders get prepared.
Download KytyPS5-Yotei-v0.1.1-windows-x64.zip and unpack it into a new folder; copy your _SaveData folder from
v0.1 if you want to keep your saves. Everything else is as in v0.1 (see its notes and the player guide PDF).
KytyPS5 Yōtei fork v0.1
KytyPS5 Yōtei fork v0.1
The first release of an experimental KytyPS5 fork made for one game only: Ghost of Yōtei (PS5), version 1.512.
No game files are included: you need your own dump of the game.
Download
- KytyPS5-Yotei-v0.1-windows-x64.zip: the launcher, the emulator, the game's shader hints and the licences.
- KytyPS5-Yotei-Player-Guide.pdf: step by step with pictures: unpack, choose the game folder, precompile shaders,
what to do if the game crashes (also inside the zip).
Playing
- Unpack the zip into an empty folder (not under
Program Files). - Start
launcher.exe, choose the folder of your game dump (the one witheboot.binandsce_sys), press PLAY. - The first start prepares the game's shaders from the included hints, then starts the game by itself.
Tested on a Ryzen 7 9800X3D with an RTX 5070 Ti, Windows 11: roughly 13-17 fps in towns and 21-25 fps in the open
world (Performance mode). The Mods page has measured speed-ups, for example the shorter detail distance (LOD 0.4).
Known issues
- Some in-engine cutscenes drop to about 6-7 fps for a minute; the game recovers after them.
- Quality mode flickers; use Performance mode, or the Render at 1080p mod with Quality mode.
- The workarounds still in this build are listed with their reasons in
README-YOTEI.md.
Reporting a problem
Launcher → Advanced → Export bug report, then open an issue here and attach the zip. Never attach game files.
Credits: Kyty by InoriRus, KytyPS5, and the
forks this one learned from (Chenxiao, TheCruZ); see README-YOTEI.md and LICENSES.