KytyPlus est un fork de KytyPS5, lui-même dérivé du projet original Kyty. Il reprend son émulation de la PlayStation 5 tout en ajoutant plusieurs améliorations, notamment le support expérimental des jeux PS4 via shadPS4, le FSR 1.0, un cache Vulkan permettant de conserver les pipelines compilés et différentes optimisations destinées aux GPU intégrés (iGPU). Il permet également l’installation des fichiers PKG depuis son interface et propose une gestion unifiée des jeux PS4 et PS5. Le projet est encore en développement et de nombreux jeux peuvent rencontrer des plantages, des écrans noirs ou des problèmes graphiques.
Les changements:
Astro Bot now boots, and controllers work properly in the launcher again.
Astro Bot (PPSA21567)
– Boots through to the title prompt. A shader descriptor read on an unbound handle was being treated as a live host pointer and faulted, killing the game before it could render. Unbound reads are now zero-filled, matching the existing policy for out-of-range offsets, so the game compiles its shaders and reaches « Press Any Button ».
– Game artwork restored. Icons were being overwritten by a generic file icon after the real artwork was applied, so titles showed a name and serial but no art.
– Launcher options restored. Seven options were lost in the upstream merge — `–hdr`, `–hide-cursor`, `–tessellation`, `–network-connected`, `–trophy-notifications`, `–sync-raw-image-buffers` and `–skip-notice-screen`. Their absence is what made the launcher refuse to start games at all.
Controllers
– Gamepads can be mapped in Settings → Controls. The dialog was never handed the launcher’s controller poller, so it always read « No controller connected » and the Gamepad tab could not capture a press. Keyboard and mouse were unaffected, which made this look like a controller-support problem rather than a wiring one.
– Controller detection no longer dies permanently after launching a game once. The poller was suspended when a game started and never resumed, so every later launch in the same session saw no pad. Suspension now follows the emulator process state, which also covers the image- and package-launch paths that previously skipped it entirely.
Known issues
– Astro Bot reaches in game but is not yet playable: frame rate is far from real-time, and the game still exits on its own after a little.