[Compat]: Game doesn't even boot, but KytyPlus doesn't write _kyty.txt #16

Activity

1. 2mg

   added

   compatibility

   on Oct 13, 2026
2. Coder787-source commented on Oct 14, 2026

   

   Coder787-source

   on Oct 14, 2026

   Owner

   More actions

   Hi @2mg ,

   Thanks for the report and for sharing _launcher_debug.txt. I’ll investigate the Demon's Souls startup issue and try to prepare a patch for v4.4. I’ll update this issue when I have more information or a build for you to test.

   👍React with 👍1Reacted by 2mg
3. Coder787-source commented on Oct 18, 2026

   

   Coder787-source

   on Oct 18, 2026

   Owner

   More actions

   ---

   Hi @2mg — thanks for the detail, and sorry for the slow reply. Two separate things were going on here, and neither was your setup.

   Why there was no log. Two independent causes

   The launcher was passing several options the emulator no longer recognised, so the process exited immediately on unknown option — before any log was written. This is fixed.
   _kyty.txt is only created when that game's printf direction is set to File. A per-game setting overrides the global one, and if it's on Silent the file is never opened at all — which looks identical to "the emulator crashed before logging".

   Also worth checking on your side: the log is written to the emulator's working directory, not the game folder. Your error mentions X:/xxxx/PPSA01341/_kyty.txt — it will instead be _kyty.txt next to kyty_emulator.exe.

   What I'd like to ask. Could you retest on v4.4 and attach the log if it still won't boot?

   In the launcher, select Demon's Souls → Edit game config → Debug tab → set printf direction to File, then Apply.
   Launch the game and wait for it to fail.
   Upload the _kyty.txt from the folder containing kyty_emulator.exe (if it's large, the last few hundred lines are the useful part).

   v4.4 merges a large batch of upstream shader fixes and several loader corrections that plausibly affect this title, so there's a decent chance it behaves differently — but I'd rather know either way. If the log shows a specific failure, that's exactly what I need to chase it down.

   Thanks for reporting it properly, including _launcher_debug.txt — that file is what let us find the unknown option problem.

   ---
4. 2mg commented on Oct 19, 2026

   

   2mg

   on Oct 19, 2026

   Author

   More actions

   3. Hi @2mg — thanks for the detail, and sorry for the slow reply. Two separate things were going on here, and neither was your setup.
   Why there was no log. Two independent causes
   The launcher was passing several options the emulator no longer recognised, so the process exited immediately on unknown option — before any log was written. This is fixed.
   _kyty.txt is only created when that game's printf direction is set to File. A per-game setting overrides the global one, and if it's on Silent the file is never opened at all — which looks identical to "the emulator crashed before logging".
   Also worth checking on your side: the log is written to the emulator's working directory, not the game folder. Your error mentions X:/xxxx/PPSA01341/_kyty.txt — it will instead be _kyty.txt next to kyty_emulator.exe.
   What I'd like to ask. Could you retest on v4.4 and attach the log if it still won't boot?
   In the launcher, select Demon's Souls → Edit game config → Debug tab → set printf direction to File, then Apply.
   Launch the game and wait for it to fail.
   Upload the _kyty.txt from the folder containing kyty_emulator.exe (if it's large, the last few hundred lines are the useful part).
   v4.4 merges a large batch of upstream shader fixes and several loader corrections that plausibly affect this title, so there's a decent chance it behaves differently — but I'd rather know either way. If the log shows a specific failure, that's exactly what I need to chase it down.
   Thanks for reporting it properly, including _launcher_debug.txt — that file is what let us find the unknown option problem.

   _kyty.txt issue is solved with Debug settings as explained.

   Game not booting was due to low available RAM (unsure if page-file is included in this calculation) but the user (me) was not warned about this neither via a popup window or in launcher's GUI (I found out the issue only in _kyty.txt).
5. Coder787-source commented on Oct 21, 2026

   

   Coder787-source

   on Oct 21, 2026

   Last edited by Coder787-source

   Owner

   More actions

   Hi @2mg would you mind testing v5.0 I implemented a plausible fix for this game, however,I can't confirm it went farther, thanks!
6. 2mg commented on Oct 24, 2026

   

   2mg

   on Oct 24, 2026

   Author

   More actions

   Will do it today or tomorrow.

   👍React with 👍1Reacted by Coder787-source
7. 2mg commented on Oct 25, 2026

   

   2mg

   on Oct 25, 2026

   Last edited by 2mg

   Author

   More actions

   Kyty_launcher.exe and launcher.exe triggered the antivirus.

   This wasn't the case so far.
8. Coder787-source commented on Oct 26, 2026

   

   Coder787-source

   on Oct 26, 2026

   Last edited by Coder787-source

   Owner

   More actions

   Hi @2mg would you mind testing the latest release, I didnt get smartscreen using launcher.exe, but it could just be because i approved it in the past, hope this helps fix this issue!
9. 2mg commented on Oct 27, 2026

   

   2mg

   on Oct 27, 2026

   Author

   More actions

   8. Hi @2mg would you mind testing the latest release, I didnt get smartscreen using launcher.exe, but it could just be because i approved it in the past, hope this helps fix this issue!

   I'm not gonna test anything unless you can explain why 0.5.0 triggered the antivirus/Windows defender.

   I don't understand what you approved in the past exactly?
10. Coder787-source commented on Oct 27, 2026

    

    Coder787-source

    on Oct 27, 2026

    Owner

    More actions

    Hi @2mg so I will be honest about the Smartscreen, I unfortunately couldn't figure a fix, and due to recent changes in code, I suspect that some change make SmartScreen flag it, if you want to verify the .exe/.zip yourself, I would suggest you use VirusTotal: https://www.virustotal.com/gui/home/upload
    And also what I meant by approved in the past is I might have approved smartscreen to run this application to run before, so that's what I meant by approved in the past, hope this explanation helps!
11. 2mg commented on Oct 27, 2026

    

    2mg

    on Oct 27, 2026

    Author

    More actions

    Please see #17 (comment) for further problems related to _kyty.txt and game crashes, I will close this ticket and post in that thread.
12. 2mg

    closed this as completedon Oct 27, 2026
13. github-actions

    added a commit that references this issue on Oct 27, 2026

    docs: update compatibility table from #16

    87029ef