[Regression] Frequent Freezing (Device Lost) Ratchet & Clank Future: A Crack in Time
Quick summary
Hi, the frequent freezing with R&C games is a known issue but I found Ratchet & Clank Future: A Crack in Time to be perfectly stable on my system with the Canary Freeze Fix patch enabled. It worked perfectly fine on 0.0.37-18022 build (the last one before Windows builds were temporarily discontinued) but updating to 0.0.37-18146 (or anything after Windows builds resumed) makes the game with the exact same settings prone to freezing again. I know patches are not allowed but given how there were some recent changes to how patches work (which was a fix for a Sonic game) I wonder if this could be related to the issue (causing the Freeze Fix to break).
Symptoms: The game will freeze with Device Lost error after very short time. Potentially Freeze Fix patch no longer works. Build with regressions: 0.0.37-18146 or earlier - can not confirm which introduced the regression as number of builds was unavailable on Windows. Settings: All default except for Freeze Fix patch that as far as I know is / was the only way to get through game without frequent crashes. System: 5080 mobile, intel 255hx, windows 11
Log attached. What I found strange was the "D:\a\rpcs3\rpcs3\rpcs3..." file path - I do NOT have a D: drive on my system.
Details
·F 0:20:01.137130 {RSX [0x1b1af08]} SIG: Thread terminated due to fatal error: Assertion Failed! Vulkan API call failed with unrecoverable error: Device lost (Driver crashed with unspecified error or stopped responding and recovered) (VK_ERROR_DEVICE_LOST) ---------------- EXTRA INFORMATION -------------------- Device Fault Information: Fault Summary:
Address Fault Information:
- Fault at address 0x200bced10 caused by instruction_pointer_fault
- Fault at address 0x56827a000 caused by access_read
(in file D:\a\rpcs3\rpcs3\rpcs3\Emu\RSX\VK\VKQueryPool.cpp:48[:4], in function 'bool vk::query_pool_manager::poke_query(vk::query_pool_manager::query_slot_info &,uint,uint)') (in file D:\a\rpcs3\rpcs3\rpcs3\Emu\RSX\VK\vkutils\shared.cpp:205[:24], in function 'void vk::die_with_error()') ·W 0:20:01.142007 {RSX [0x1b1af08]} SYS: Emulation has been frozen! You can either use debugger tools to inspect current emulation state or terminate it. ·! 0:20:01.150532 {rsx::thread} SIG: Thread time: 562.468750s (1613.909446Gc); Faults: 791 [rsx:790, spu:0]; [soft:0 hard:0]; Switches:[vol:0 unvol:0]; Wait:[547.737s, spur:0] ·W 0:20:01.158227 SYS: CPU Thread 'rsx::thread' terminated abnormally!
Build with regression
0.0.37-18146
Attach two log files
Attach capture files for visual issues
No response
System configuration
No response
Other details
No response
you can also retrieve and test the builds marked as not available. Simply move on the related PR and:
- click on the
View detailsto expand the builds panel (see first screenshot) - click on
RPCS3 Windows' Detailslink to open the Windows build panel - expand
Upload artifacts (7z)and then click on the link onArtifact download URL:to download the build (see second screenshot)
For your issue I would try to test kd-11's builds (possibly #17327) first and eventually some of elad's builds.
Below some screenshots:
Hi @digant73 I tried to follow your procedure but I'm getting this "The logs for this run have expired and are no longer available.", looks like the windows builds can no longer be accessed.
try latest builds. They fixed some crashes with device-lost
Needs retesting. A CDL log would be a great help but is non-trivial to capture for beginners and I've never been able to reproduce this hang. Maybe @digant73 can help here?
unfortunately I don't have that game
I attempted to re-test on the latest build and was not able to reproduce this crash anymore. Game seems stable even without the Freeze Fix patch. I only played about 1 hour so it's possible I simply got lucky but when I was experiencing this problem it never took longer than 30 minutes to manifest.
thanks for reply. Please don't forget to close this issue when you are sure it is no longer present
I played the game for a bit using the latest build, and it seems to be stable with the freeze patch.