KytyPS5

Windows: missing DLL or platform plugin

1. Extract the complete ZIP again into a new writable directory. Running inside a ZIP preview or copying only launcher.exe leaves its libraries behind.
2. Check that the folder still contains both executables and the packaged Qt libraries; the Windows platform plugin is platforms\qwindows.dll. Do not combine DLLs from two releases.
3. If Windows Security quarantined a file, open Windows Security → Virus & threat protection → Protection history and read the detection name and affected file. Recheck the archive hash before deciding what to do. Do not download a replacement DLL from an unrelated site.
4. Run .\launcher.exe from PowerShell in the extracted folder. A Qt startup error here occurs before game loading; changing the game’s shader settings will not repair it.

Linux: identify a missing host library

In the extracted folder, run:

./launcher
ldd ./launcher
ldd ./plugins/platforms/libqxcb.so

A line ending in not found names a missing host dependency. Use your distribution’s package search to locate that exact shared library, install its native x86_64 package, then repeat the check. If the plugin file itself is missing, re-extract the package first. Qt’s bundled plugins do not replace every Linux system library.

If the error says it cannot connect to a display, run the launcher from your logged-in desktop session rather than a headless SSH shell. If it says Permission denied, check ls -l ./launcher ./kyty_emulator; restore their executable bits with chmod u+x ./launcher ./kyty_emulator only for the verified files. On a noexec volume, move the complete extracted directory to an executable user-owned location.

1. Check the content path, not just the folder name. For the Windows example, run the first command below. True means the executable exists there; False means the selected path or content layout is wrong.
2. Add D:\Games in Global settings, save, then use Refresh game list. For an extra nested folder, locate the real eboot.bin and ensure its containing game directory is below the library root.
3. Use a real directory. The scanner skips symlink directories, so a linked game folder can disappear from discovery even when it opens in a file manager.
4. For a .zar, confirm that its archive root contains eboot.bin. Renaming a ZIP, ISO or PKG to .zar does not convert it.

Test-Path "D:\Games\ExampleGame\eboot.bin" -PathType Leaf

test -r "/games/ExampleGame/eboot.bin" && echo "Readable" || echo "Missing or unreadable"

Replace the example path with yours. On Unix, “Missing or unreadable” means check the filename’s case, mounted volume and your user’s read access. If the direct CLI launch works but discovery does not, return to the parent-root and symlink checks; the emulator can already read the content.

1. Read the error before the game starts. An unsupported API/device or no suitable GPU points to the host driver or device selection; an error naming a particular unsupported feature needs that feature, not just Vulkan 1.3.
2. Update the driver for the GPU you intend to use, then restart the computer if the driver installer requests it. On Linux, update the distribution’s Vulkan driver package appropriate to your GPU.
3. Open Global settings... → Graphics & display → GPU, select that device and Save. Check the title’s custom settings too: a per-game override can retain a different choice.
4. On Windows laptops, if you also set an OS graphics preference, add kyty_emulator.exe in Settings → System → Display → Graphics and choose the intended high-performance GPU. Setting a preference only for launcher.exe does not target the separate game process.
5. Start the same game again. If the same feature rejection remains, keep its exact text with the GPU and driver version. For example, “depth attachment feedback loop is not supported by the host” is the reported Demon’s Souls Windows failure—not a request to increase the window size or install more RAM.

On Mac, preserve the bundled MoltenVK files and distinguish a missing-library startup error from a game-specific unsupported graphics path.

1. Turn on File logging, reproduce the problem once and copy the log before another run. Note whether it stopped before the first screen, in a menu or during a specific scene.
2. If the log says a path/file cannot be opened, use the content-path checks above and confirm the game dump is complete. Do not treat a missing file as a shader problem.
3. If it names shader translation, specialization or an unimplemented instruction, compare the exact title ID, game version and platform with the report notes. A title-specific emulator limitation is not fixed by reinstalling the launcher.
4. If the problem began after an update, run the same content with your retained previous build and its saved settings. Works on the previous build but fails on the new one indicates a regression worth documenting; fails on both calls for checking content and the existing title report.
5. For a host exception or semaphore failure without a clear earlier error, reopen the title with its default settings, then compare the previous build. Preserve the earliest error line and the final exception; the last line alone may be a consequence, not the cause.

A black screen with a running process is not proof that it will eventually load. If there is no useful progress or a repeatable error, close the run and follow the matching branch rather than changing unrelated settings.

Hades: audio and gameplay out of sync

The Windows report dated 27 September, build 421684e, says returning to the game menu and starting again restored sync. Try that within the same build before changing frame pacing. Its 240 setting is not a measured performance result. Open the Hades test context.

Stray: textures turn black after an update

The 18 September Windows report names 1d2f59d as last working and 394e638 as first broken on that machine. Its AMD CPU patch attempt did not resolve the problem. If you retained the earlier build, use the rollback steps to compare the same scene. This does not establish that every later build has the bug. Open the Stray report.

GTA V: Fidelity does not load

The 24 September Linux test, KytyPS5-2026-09-24-2aaf0c9, starts in Performance mode but not Fidelity. If matching that test, choose Performance in the game’s graphics options; Performance RT still had black silhouettes and shimmering lights. Missing text and cutscene crashes remained, so the mode choice is not a complete fix. Compare GTA V platform reports.

For the inspected 29 September Mac build, an ad-hoc signature and no Apple Developer Team identifier were observed. The local Gatekeeper assessment rejected it; that observation alone does not identify malware.

1. Compare the ZIP’s full SHA-256 with the Mac download card and confirm the exact build. Re-download and re-extract if they differ.
2. For an unverified-developer warning on the matching archive, read the message. If you choose to allow this specific app, open System Settings → Privacy & Security after the blocked attempt and use the per-app Open Anyway option if macOS offers it.
3. For a “damaged”, malware or revoked-signature warning, stop instead of applying a blanket bypass. Recheck the original archive and retain the warning text.
4. If the app instead requests Rosetta, use the system’s Rosetta installer; that is a CPU-translation requirement, not the same as Gatekeeper approval.

Do not turn off Gatekeeper globally or recursively remove security attributes from unrelated files. Mac gameplay compatibility remains separate from successful app launch: the selected M3 ASTRO’s PLAYROOM report does not boot.