KytyPS5
Weekly updates — game progress, recent fixes, and ongoing development.
Development on Discord — KytyPS5 development.
KytyPS5 is a free and open-source PlayStation 5 translation layer written in C++ for Windows
and Linux, with experimental macOS support. It is based on a heavily modified version of
Kyty. The project is in active development, and behavior
can change significantly between builds.
[!IMPORTANT]
KytyPS5 is not affiliated with Sony Interactive Entertainment or PlayStation. The project does
not distribute games or copyrighted system software. Use only game files that you have obtained
legally.
Current Status
Development is currently focused on expanding game compatibility and improving boot reliability.
External low-level emulation modules are neither required nor planned.
Windows and Linux are the primary target platforms and receive the most testing.
macOS support is experimental. The emulator is built for x86-64 and runs on Apple Silicon under
Rosetta 2, with Vulkan provided by MoltenVK. A small number of titles have been verified in-game
on Apple Silicon hardware; see Building on macOS.
Community game test results are available in the
KytyPS5 Compatibility List.
Bugs and Issues
Compatibility, stability, and performance can vary between versions. You may encounter crashes
or graphical glitches, so please include the version you tested when reporting an issue.
Screenshots
Notable Forks
These community forks bring KytyPS5 to other platforms.
- Cosmo/KytyPS5 — Xbox Series X: Direct3D 12 renderer, sleek
controller-first interface, and local multiplayer for up to four players.
Contributing
Testing games and submitting detailed bug reports are useful ways to contribute. Search existing
issues first, then use the Game Emulation Status Report template and attach the complete log file.
Pull requests for general fixes, architectural changes, or refactoring that do not address a concrete bug or launch problem in a specific game will be automatically closed.
Large, unfocused commits or pull requests that bundle unrelated changes without a clear purpose or game-related benefit will also be automatically closed.
Keep each PR focused. Name the affected game, describe the exact problem, and provide evidence showing what the change fixes.
Windows and Linux are the primary target platforms, so changes to shared code should not
introduce regressions on either platform. Changes confined to a platform's own code paths
only need to build on that platform. Because KytyPS5 is still evolving quickly, consider
opening an issue before starting a large change.
Formatting
Set up the clang-format hook after cloning.
Install pre-commit using the method appropriate for your platform:
- Arch Linux / CachyOS:
sudo pacman -S pre-commit
- Other Linux / macOS / Windows:
python -m pip install pre-commit
Then install the Git hook:
python -m pre_commit install --install-hooks
It formats staged .cpp, .h, and .inc files in src.
Developer Information
The PS5 graphics architecture is based on AMD RDNA 2. Use AMD's
RDNA 2 Instruction Set Architecture Reference Guide (document 70648)
as the primary instruction-encoding reference when working on shader decoding and recompilation.
Important areas of the codebase:
The renderer targets Vulkan 1.3. Keep shader changes aligned with both the RDNA 2 ISA semantics and
the Vulkan/SPIR-V validation rules.
Building
System requirements
- Windows 10 version 1803, a current Linux distribution, or macOS on Apple Silicon
- A 64-bit x86 processor (on macOS, an Apple Silicon processor with Rosetta 2)
- A Vulkan 1.3-capable GPU with current drivers (on macOS, Vulkan is provided by the bundled
MoltenVK)
Build requirements (Windows)
- Git
- CMake 3.22.1 or newer
- Ninja
- Visual Studio 2022 or Build Tools 2022 with the Desktop development with C++ workload and
C++ Clang tools for Windows component
- Qt 6 for MSVC 2022 64-bit, including Concurrent, Network, and Widgets
- glslang (
glslang or glslangValidator) on PATH
- Python 3 on
PATH; the bundled SPIRV-Tools runs it at configure time
This is the beginning of the README. Read the rest at the original. Read the full README ↗
