PS5SX2 build 177 (disc helper 171g) - WHAT TO SEND BACK. Read TEST-177.txt first (what to test and the answers we need). ===================================================================================================================== Send everything by FTP (port 2121) to us only, privately. The logs can hold details of your console (names, IDs, IP addresses). NEVER send steamgriddb.key, webui_token.txt or disc-tiles/steamgriddb-key.txt. UNCHANGED SINCE 175: the disc helper writes NO log files of its own any more (it is the setup that gave the tester no kernel panics). So the four files older notes asked for - /data/PCSX2/disc-tiles/disctile.log, kernel-log.txt, shadowmount-debug.log and /data/PCSX2/logs/disc-auto.log - do not exist unless you made the empty file /data/PCSX2/flags/kp_log BEFORE the console started (restart the console after adding it). That is normal: do not look for them, and do not worry that they are missing. Use kp_log only when we ask for a "logging round". ALWAYS SEND (every report) /data/PCSX2/boot.log, boot.1.log, boot.2.log all three if they exist, even small ones (a restarted app writes a new one). They hold the build tag, the disc read lines ("[disc] 10 s: ..." every 10 seconds while a disc game plays), the start of each game, folders, frame generation, and the game tile lines ("[tile] ...", "game tile marker ...") /data/PCSX2/emulog.txt if a game started /data/PCSX2/logs/payload-init.log the disc helper's own short record (it says "disc payload 171g") Your answers: which helper file, ShadowMount+ version, etaHEN / OnionHEN version, PS5 model + firmware, drive (PS5's own / USB make and model), the game and what you saw ALSO, FOR THE PROBLEM YOU HAD Game tiles (NEW in 177; only with the empty file /data/PCSX2/flags/gametiles): /data/PCSX2/tiles/state.txt and alive.txt, the folder /data/PCSX2/disc-tiles/gametiles/ (removing.txt, next.txt, the .sig files), boot.log, boot.1.log, payload-init.log, a screenshot of the home screen, the words the "Home screen tile" row showed, and the SECONDS from closing PS5SX2 until the tile came (or went) An HD texture pack (NEW in 177: the .7z ones) did not download, unpack or show: boot.log, boot.1.log: every line starting [texpacks] (the 7z ones say "7z:", "7z unpacking:", "7z unpacked", with "needs about N MiB of flexible memory" and "flexible memory free N MiB"), the exact words on the row, the pack's name, the free space on /data, how long the download and the unpack took Back to the menu (L1+R1+Touch) did not return to the shelf, or the console crashed: /data/PCSX2/logs/leave.txt and /data/PCSX2/logs/relaunch.log (flag leavelog makes leave.txt reach the disk after every step: add it first, then try again) Back to the menu (L1+R1+Touch), any problem or just the timing: /data/PCSX2/logs/settings.log (the line "the shelf's first frame is N ms after the press"), leave.txt, relaunch.log (say: game started from the shelf, from a disc tile or from a game tile; with which switch files: menurelaunch, menusettle, leavelog) Frame generation does nothing for a PAL (or any) game: boot.log and boot.1.log from a run with frame generation ON: the lines "[fg] status:" (every 10 s), "[display] swapchain:", "[boot] frame generation:", plus the TV/monitor model and the PS5 Video Output settings (resolution, 120 Hz Output, VRR) A dark spot on a case in the shelf: boot.log, plus which case (the one you left or the one you moved to), how long, and how the case was held A copied game did not start / landed on the home screen at the end of a copy: /data/PCSX2/logs/disc-launch.txt, disc-launch-exec.txt, disc-autostart.txt, disc-refg.txt (whichever exist; do not delete them first), plus boot.log from the line "[disc] done:" on. Say how the disc went in (see TEST-175.txt). A disc tile was missing / did not start / stayed after the disc was out: press the Reload PS2 Disc tile once and wait 30 seconds, then send the files above and say what the pop-up said Kernel panic on a restart: the klog capture of that run if you have one, the time of the restart, and "disc in / game started / disc ejected how", and whether a game tile was installed or a removal was pending (removed, PS5SX2 not closed yet) Stutters: boot.log has the numbers ("[disc] 10 s:" lines). Say where in the game and which flags you had (nodisc32, discblock, ...) LOGGING ROUND (only when we ask for it) 1. Make the empty file /data/PCSX2/flags/kp_log, restart the console, load ShadowMount+ and the helper again, do the test. 2. Send the folder /data/PCSX2/disc-tiles (not steamgriddb-key.txt) and the folder /data/PCSX2/logs. 3. Delete kp_log afterwards and restart the console again (log files are a different setup from the one that gave no kernel panic). IF SOMETHING GOES WRONG (empty files in /data/PCSX2/flags/, no file extension; see TEST-177.txt, TEST-176.txt and TEST-175.txt for the whole list) gametile_off the helper's kill switch for game tiles (wins over gametiles; restart the console after adding it) nogametiles the shelf shows no "Home screen tile" row (wins over gametiles) nodisc32 the PS5's own drive stays at 2.0x discblock the old way of reading the disc (as in build 174) menurelaunch L1+R1+Touch the safe way of 175 (helper program, the home screen shows for a few seconds) texpack_no7z the .7z HD packs are not offered or unpacked (as in 176) nocoverfit / nobackprefetch / nolaunchbox the old covers behaviour / no look-ahead for backs / no LaunchBox art Helper switches (restart the console after a change): kp_log, gamequiet_off, kp_off_quiesce, kp_nowatcher, kp_nodrive, kp_stub9020, gametile_off, gametile_noheal, gametile_nohide, gametile_norefresh; the disctile_* switches of 171 are unchanged.