Coder787-source/KytyPlus

KytyPlus is a KytyPS5-based PlayStation 5 emulator for Windows, macOS, and Linux. This repository is a standalone project derived from KytyPS5 (itself based on Kyty), with additional work focused on iGPU optimization, build stability, and a unified PS4/PS5 dispatch (iGPU status: first real-game result achieved; see iGPU status).

KytyPlus has a validated PKG/PFS parser, a strict ELF loader, and working SDL controller mapping. The infrastructure works. The only thing missing is game results.

If you have a decrypted PS4 or PS5 game file (eboot.bin/ELF, or .PKG):

1. Download the latest release.
2. Load your game via the GUI.
3. If it crashes, click the Share Log button in the log viewer or screenshot the log.
4. Submit a new Issue and paste the log(or add the screenshot).

You don't need to be a developer. You just need to have a game file. Every report helps.

Video of Dead Cells booting to the main menu on KytyPlus v1.8 (i7-9700K, RTX 4060 Ti, external HDD). Tested and recorded by @CorpseSlayer — full report and system specs in KytyPlus issue #3.

▶ Watch on YouTube (CC-BY 4.0 — reuse with credit to @CorpseSlayer) ▶ Watch on Google Drive

Footage of a commercial game reaching menu — the project's first confirmed boot-to-menu result. Past-menu state has not been tested.

• KytyPlus is not affiliated with, endorsed by, or connected to Sony Interactive Entertainment, PlayStation, or any Sony subsidiary.
• “PlayStation,” “PS5,” and related marks are trademarks of their respective owners.
• This project is an independent community emulator.

• KytyPlus does not include games, game dumps, or Sony system firmware.
• Use only game files you have obtained legally.
• Do not ask maintainers for piracy links, firmware dumps, or copyrighted sce_module SPRXs.
• Distributing copyrighted dumps or firmware with this software is illegal.

• Provided as-is, without warranty of any kind.
• Builds may break saves, drivers, or performance expectations. Use at your own risk.
• Binary releases must remain accompanied by (or clearly linked to) the corresponding source under GPL-2.0.

Windows, macOS, and Linux. Vulkan 1.3 required (MoltenVK on macOS).

Upstream KytyPS5 can already boot a range of 2D/3D titles (UE4/5, Unity, custom engines). KytyPlus inherits that capability and adds an optimization/tooling layer on top — see the "Features exclusive to KytyPlus" section below for what's genuinely new.

These are not in upstream Kyty or KytyPS5. Each is implemented, compiled, and wired into a real code path. Game-level benefit is not yet validated on real hardware — that is what testers are for.

Fully wired, validated where noted:

• Shader / pipeline disk cache — compiled Vulkan pipelines persist to _Cache/vulkan_pipeline_cache.bin and reload on subsequent launches, skipping work for shaders that haven’t changed. A compatibility check rejects stale caches. (First in the PS5 scene. Game-level benefit unvalidated.)
• FSR 1.0 upscaler — edge-adaptive spatial upscaling (EASU + RCAS), works on all Vulkan GPUs (AMD / NVIDIA / Intel). Configurable via the launcher (method + sharpness); auto-enabled on iGPUs. Falls back to a plain blit if the GPU can’t handle it. (First in the PS5 scene. The upscaler runs; the internal-resolution-reduction / bandwidth-saving half is not yet wired.)
• Configurable present path — present mode (VSync / Mailbox / Immediate), present filter (Nearest / Linear / Cubic), and aspect ratio (Stretch / 16:9 / 4:3 / Integer). (First in the PS5 scene.)
• PKG package parser + full PFS filesystem parser — parses Sony .pkg package files (PS4/PS5 digital games / updates) via --install-pkg, extracts the inner PFS image, then walks the full filesystem (PFS superblock, D32/S32/S64 inodes, directory enumeration, indirect block traversal, PFSC/zlib decompression). (First in the PS5 scene.)
• Install .PKG GUI buttons — "Install Package (.pkg)" buttons in the launcher, so users no longer need the command line to install. Fixes the discoverability gap where users previously couldn't find the install path.
• Unified PS4/PS5 dispatch — auto-detects PS4 vs PS5 from the game ELF and dispatches PS4 titles to an embedded shadPS4 subprocess, reparenting its window into KytyPlus with unified saves.

Wired, validated only as mechanism / spec, not on real games or hardware:

• iGPU auto-optimization — detects integrated GPUs (e.g. Radeon 780M-class) via the Vulkan device type and automatically enables FSR 1.0 + a texture LOD bias to cut bandwidth. force_igpu_mode lets you opt in on a discrete GPU for testing. (First PS5 emulator to focus on iGPU optimization. Game-level benefit unvalidated.)
• UMA heap detection — detects unified-memory architectures (device-local + host-visible + host-coherent). Detection is live; the staging-bypass itself is not yet wired.
• Bandwidth-aware adaptive LOD bias — monitors frame timing and ramps texture LOD bias up under bandwidth pressure / down with headroom, invalidating stale samplers via a generation counter. (First in the PS5 scene. Mechanism self-validatable; game-level benefit unvalidated.)
• MMIO bus + NVMe LLE foundation — a real address-range router for memory-mapped devices (registered in the boot path) plus an NVMe controller rewritten as an MmioDevice talking to the real MMU. (First LLE infrastructure in the PS5 scene. Not yet exercised by games — groundwork, not a working storage path.)
• Extended CPU instruction emulation — software-emulates 15+ x86-64 instructions that fault on hosts lacking them (RDTSC/RDTSCP, CPUID hypervisor leaves, XGETBV/XSETBV, RDMSR/WRMSR, RDPMC/RDPRU/RDPID, CLZERO, WBINVD/INVD, MWAIT, descriptor-table/status-word ops). (Extends upstream’s MONITORX/MWAITX + SSE4a + SHA-NI baseline. Strictly additive, no-regression.)
• EXIT diagnostics — 24 highest-impact unimplemented-path guards upgraded from raw condition strings to descriptive messages, so tester crash logs say what opcode/register/syscall was missing. (No-regression.)
• Config validation — case-insensitive parsing, deprecated names transparently migrated (e.g. Fsr31 → Fsr1), invalid values rejected with a clear log message.

Compatibility is still early. A title that no longer hits one known crash will often hit the next unimplemented feature. Always test with a fresh build and attach logs when reporting.

Help test KytyPlus: share your results or file a compatibility report. Browse existing results in the compatibility list.

Have a question or need help (config, a game not booting)? Open an issue — it's not just for bug reports. I read every one and reply. Questions are welcome, even if it's just "how do I map my controller" or "does this work on my GPU." Better to ask than guess.

This project started on an integrated-GPU machine, so several defaults and allocator choices were made with iGPUs / UMA in mind. That design intent now has a first real result behind it.

Silent Hill 2 Remake (PPSA08709, UE5, PS5-native) — AMD Radeon 840M iGPU (512 MB), Ryzen AI 5 340, shared system memory (15.2 GB), 1280×800 display, windowed at 1166×656. Multi-minute session on a dev build (post-v3.4).

What was observed:

• Rendering correctness: the game's first interactive screen (content-warning / title flow) draws with no visible graphical glitches — crisp text, correct layout, working QR code, no corruption or garbling anywhere in the frame.
• Presentation: the game allocates and renders native 3840×2160 buffers; FSR 1.0 (EASU + RCAS) upscales them into the window correctly. The present path is stable end-to-end.
• Stability: 4,088 frames and ~149,000 GPU submits over a ~4-minute session with zero GPU hangs, zero device losses, zero crashes, ending in a clean exit — no Windows driver reset (TDR) was triggered at any point.
• Performance: ~3.9 FPS. Expected for an early HLE emulator driving a 2024 AAA UE5 title on an entry-level iGPU — the title is not playable yet. This figure is from the warning screen; deeper gameplay is untested and likely heavier.
• Audio / controller input: not evaluated in this session.
• Known visual limitation waiting ahead: one UE5 volumetric (fog) compute pass is currently skipped to contain a GPU hang on this APU — volumetric/fog effects will look wrong in gameplay until that pass is implemented properly. A storage-image atomic feature guard is also active. Both are emulator-side workarounds; no game files are modified.

This is a correctness milestone, not a playability claim: geometry, text, compute and the full present pipeline demonstrably work on shared-memory iGPU hardware; performance is the next frontier. The session was ended manually at the warning screen, so the title could boot farther, but that is untested — nothing in the observed run suggested a wall right behind it. See COMPATIBILITY.md.

If you have an iGPU system (e.g. Radeon 780M, Intel Arc iGPU) and legally obtained game dumps, a boot/menu report with logs and a rig description is still extremely valuable — one data point does not establish a pattern. Please share it in discussions or as a compatibility report.

• GameGaz (大人のためのゲーム講座, JP) — has tracked KytyPlus releases since v1.9:
  • GameGaz Daily 2026.8.16 — KytyPlus v2.7 (iGPU auto-detection, unified PS4/PS5 dispatch)
  • GameGaz Daily 2026.8.3 — KytyPlus v2.0 (enhanced caching)

These links cover the upstream KytyPS5 project (the lineage KytyPlus is derived from), not KytyPlus itself. Listed for context only.

• GameGaz Daily 2026.8.4 — KytyPS5 2026-08-03-e8752ac

Coverage links are external and not affiliated with this project. They are listed for community reference only.

Screenshots below are from the KytyPS5 lineage and illustrate early boot capability — not KytyPlus playability guarantees.

Boot progression on an AMD Radeon 840M (512 MB, shared memory), pure HLE, farthest documented result for this title in the PS5 emulation scene (upstream baseline: crash at boot/splash on discrete GPUs: KytyPS5 #210). Game:Konami Digital Entertainment / Bloober Team � shown here for interoperability documentation only.

Unreal Engine Logo	Bloober Team
Konami Logo	Content-warning screen

Disgaea 6	Dreaming Sarah
Neptunia ReVerse	SILENT HILL: The Short Message
Hellboy Web of Wyrd	Paleo Pines

• Windows 10 (1803+) or Windows 11, 64-bit (Vulkan 1.3)
• CPU: x86-64
• macOS 12+ (Vulkan 1.3 via MoltenVK)
• Linux (Vulkan 1.3)
• GPU: Vulkan 1.3 capable, with current drivers (AMD / NVIDIA / Intel)
• RAM: 16 GB minimum; 32 GB recommended (especially on iGPU / UMA systems)

• A legally obtained dumped game or demo directory, typically containing:
  • eboot.bin (Prospero ELF; sometimes named .elf)
  • Supporting files (sce_sys, data folders, etc. as required by the title)
• KytyPlus expects Prospero / FreeBSD-OSABI ELFs. Generic homebrew SDK ELFs with System V OSABI are often rejected (elf is not valid / EI_OSABI != ELFOSABI_FREEBSD).

Important: Before using KytyPlus, please read our Legal Disclaimer regarding trademarks and the legal acquisition of guest system files.

1. Open the repository Releases page.
2. Download the latest install zip (full _Build/windows/install tree — not a lone .exe).
3. Extract somewhere writable (example: C:\KytyPlus\).
4. Run launcher.exe or kyty_emulator.exe as described in Running.

cl.exe alone is not supported — use clang-cl.

Open an x64 Native Tools / Developer shell for VS 2022, then:

cd C:\path\to\KytyPlus

git submodule update --init --recursive

cmake -S src -B _Build/windows -G Ninja `
  -DCMAKE_BUILD_TYPE=Release `
  -DCMAKE_C_COMPILER=clang-cl `
  -DCMAKE_CXX_COMPILER=clang-cl `
  -DCMAKE_PREFIX_PATH="C:/Qt/6.10.3/msvc2022_64"

cmake --build _Build/windows --target launcher
cmake --install _Build/windows --prefix _Build/windows/install

Replace the Qt path with your installed version. After a successful install you should have:

_Build\windows\install\launcher.exe
_Build\windows\install\kyty_emulator.exe

(plus Qt/runtime DLLs staged next to them)

A CMake Tools setup lives in .vscode:

1. Install CMake Tools and C/C++ extensions.
2. Set CMAKE_PREFIX_PATH in .vscode/settings.json to your Qt path.
3. Set --game in .vscode/launch.json for debugging.
4. Configure/build from an x64 VS developer environment.

Built and tested on macOS 15 with Xcode 26 and Qt 6.10.3 (clang_64). macOS uses MoltenVK to provide Vulkan 1.3; the CI build bundles libMoltenVK.dylib next to the binaries.

cd /path/to/KytyPlus

git submodule update --init --recursive

cmake -S src -B _Build/macos -G Ninja \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_OSX_ARCHITECTURES=x86_64 \
  -DCMAKE_C_COMPILER=clang \
  -DCMAKE_CXX_COMPILER=clang++ \
  -DCMAKE_PREFIX_PATH="$HOME/Qt/6.10.3/macos"

cmake --build _Build/macos --target launcher
cmake --install _Build/macos --prefix _Build/macos/install

To run the built binaries, place libMoltenVK.dylib next to kyty_emulator (or install the Vulkan SDK). After a successful install you should have:

_Build/macos/install/launcher
_Build/macos/install/kyty_emulator

Built and tested on Ubuntu 24.04 with Clang and Qt 6.10.3 (linux_gcc_64). Vulkan 1.3 is provided by your system Mesa/NVIDIA drivers.

sudo apt-get update
sudo apt-get install --no-install-recommends --yes \
  clang lld ninja-build cmake git \
  glslang-tools \
  libgl1-mesa-dev libwayland-dev wayland-protocols \
  libx11-dev libxext-dev libxcursor-dev libxfixes-dev \
  libxi-dev libxrandr-dev libxkbcommon-dev libxss-dev \
  libasound2-dev libpulse-dev libudev-dev libdbus-1-dev

Plus Qt 6 (Widgets, Network, Concurrent), e.g. ~/Qt/6.10.3/gcc_64.

cd /path/to/KytyPlus

git submodule update --init --recursive

cmake -S src -B _Build/linux -G Ninja \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_C_COMPILER=clang \
  -DCMAKE_CXX_COMPILER=clang++ \
  -DCMAKE_PREFIX_PATH="$HOME/Qt/6.10.3/gcc_64"

cmake --build _Build/linux --target launcher
cmake --install _Build/linux --prefix _Build/linux/install

After a successful install you should have:

_Build/linux/install/launcher
_Build/linux/install/kyty_emulator

Qt plugins and shared libraries are staged under _Build/linux/install/lib and found via an $ORIGIN/lib RPATH, so run the binaries from the install prefix directly.

Update GPU drivers before reporting graphics bugs.

.\_Build\windows\install\launcher.exe

1. Open global settings and add a folder that contains your dumped games.
2. The launcher searches recursively for directories with eboot.bin.
3. Select a game and run it.

Game directory (loads /app0/eboot.bin):

.\_Build\windows\install\kyty_emulator.exe --game "D:\Games\MyDump"

Specific ELF / eboot.bin (parent folder becomes /app0):

.\_Build\windows\install\kyty_emulator.exe --game "D:\Games\MyDump\eboot.bin"

.\_Build\windows\install\kyty_emulator.exe --game "D:\Games\MyDump\something.elf"

See all options:

.\_Build\windows\install\kyty_emulator.exe --help

• Keep dumps on a fast local disk; long paths and permission-locked folders cause avoidable pain.
• For bug reports, enable logging as needed and attach the full log, especially the final --- Error --- block and stack trace.
• iGPU / UMA systems: shared memory pressure is normal. Note: KytyPlus has not yet been verified to boot or run on any integrated GPU — iGPU-friendly defaults are by design intent, not confirmed behavior (see iGPU status).

1. Search existing issues first.
2. Include: game title, serial/title ID if known, KytyPlus commit or Release name, GPU/CPU/RAM, OS.
3. Attach the complete log file.
4. Describe exact steps (boot → menu → crash, etc.).

Expect crashes and incomplete features. Actionable reports with logs help more than “doesn’t work.”

• Prefer focused changes that build on Windows with the documented toolchain.
• Open an issue before large redesigns.
• Keep PRs reviewable; include tests when practical.

python -m pip install pre-commit
python -m pre_commit install --install-hooks

Formats staged .cpp, .h, and .inc files under src.

AI tools may be used for research and assistance. Contributors must review, understand, and test everything they submit. Disclose meaningful AI involvement in pull requests. Unverified generated dumps may be closed without review.

PS5 graphics are AMD RDNA 2–based. Useful reference: RDNA 2 ISA Guide (70648).

Renderer target: Vulkan 1.3.

KytyPlus (like KytyPS5) is licensed under the GNU General Public License version 2 (GPL-2.0-only).

• KytyPS5/KytyPS5 — primary upstream this tree is based on
• InoriRus/Kyty — original Kyty project (MIT); see LICENSES/Kyty-MIT.txt
• shadps4-emu/shadPS4 — reference for memory-model understanding and AVPlayer-related work in the lineage

Third-party components remain under their own licenses as included in the tree.

When publishing binaries, comply with GPL-2.0: provide Corresponding Source for the exact build.

Can I run a raw .elf?
Yes, via --game path\to\file.elf, if it is a valid Prospero ELF. Homebrew SDK ELFs with the wrong OSABI are often rejected.

Do I need PS5 firmware?
Not for the intended HLE path. Do not request or redistribute firmware here.

Is game X playable?
Assume no until a tester confirms with a specific build. Prefer “boots / menu / ingame crash” labels over “playable.”

Why not ship only kyty_emulator.exe?
It depends on staged DLLs and data from the install prefix, and GPL requires source availability with binaries.