You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The game can go further when using higher clocks scale on 14879, but after updating the RPCS3 (#13672), the game freezes when using higher clock scales.
Details
14879 Build manage to reach the menu when using 65% clocks scale.
However on a 14881 Build, the game randomly freezes during the intro when using 65%.
I can go ingame when using 50% clocks scale on a 14879 Build.
Sadly for 14881 Build, the game crashes when trying to exit the menus after using 50%.
Quick summary
The game can go further when using higher clocks scale on 14879, but after updating the RPCS3 (#13672), the game freezes when using higher clock scales.
Details
14879 Build manage to reach the menu when using 65% clocks scale.

However on a 14881 Build, the game randomly freezes during the intro when using 65%.

I can go ingame when using 50% clocks scale on a 14879 Build.

Sadly for 14881 Build, the game crashes when trying to exit the menus after using 50%.

Build with regression
v0.0.27-14881-39d17a94
Attach two log files
14879:
RPCS3.log.gz
RPCS3.log.gz
14881:
RPCS3.log.gz
RPCS3.log.gz
Attach capture files for visual issues
No response
System configuration
AMD Ryzen 9 5900X 12-Core Processor | 24 Threads | 15.89 GiB RAM | RTX 3080 driver 531.61.0.0 | Windows 10 Pro 22H2
Other details
No response
The text was updated successfully, but these errors were encountered: