-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call of Duty: Black Ops II [BLUS31011] Game freezes randomly #13602
Comments
If it's consistent on your system you can install SDK and capture a log with debug output enabled. |
When booting BLUS31011 updated to 1.19 the game crashes at the press start screen if using 100% default configuration. |
I'm unable to reproduce on RTX 3050. The debug output also has no information about any violation that could cause a crash. |
I have an idea - try this build: https://cirrus-ci.com/task/5489746785337344 |
We just have to wait for nvidia to implement VK_EXT_device_fault then. AMD already ships that extension, basically whenever the driver crashes it should give some more information to us about why it did so. Until then I think it's not very useful to keep fighting the NVIDIA driver. |
Try with #13875 |
Getting something similar here, though not quite the same. The game doesn't crash at the start screen on default settings, but rather freezes ingame after a while (between 3-15 minutes), usually in the "zombies" mode. Using default settings except for Approximate ZCull accuracy and Ordered&Atomic RSX FIFO accuracy. Note though, the "device lost" message isn't thrown to the log file. The log below is quite large as it took about 15 minutes of play to trigger the freeze. OS: Linux Mint 21.1 / kernel 5.15 |
Update: Gave this a closer look. As I mentioned I don't see the
This is soon followed by other entries that seem to reflect a problem, for example:
Failed attempts to resolve include:
Note that I cannot test OpenGL as rpcs3 hangs during the initial shader build process (though this happens with all titles, not just this one). |
Issue not occurring on RPCS3 v0.0.29-15463-edf4f7ea Alpha |
Still freezing here unfortunately, after several single-player zombie mode games. Tested against commit edf4f7e with new cache and default configuration as well. Please re-open.
Log: RPCS3.log.zip |
Looks like when I tried today. Reinstall your game update files and try again. |
Thanks for reopening. I tried what you suggested but it still froze. Update path was from 1.00 > 1.09 > 1.19, was that yours? Log: RPCS3.log.zip |
Test with #14657 (if its merged when you're reading this, just test latest RPCS3 build instead) |
Thanks, still freezes after 5-15 minutes after going ingame in testing a build with #14657. Again I do not see New log in case it helps: RPCS3.log.zip |
Yea freezes for me as well. |
Well I can certainly create a new issue for this, as this one's title may be misleading assuming the fatal device error isn't a cause of freezing any more. With regards to zcull accuracy, I've tested using precise and approximate and freezing occurs with either (though perhaps not as frequent with approximate). Play in zombie survival mode, specifically starting in the bus station, and you should see the same thing? |
Does the driver still crash @Darkhost1999 ? |
RPCS3.log.gz
|
Well, the log doesn't show any RSX crashing though. The only difference between precise and approximate is that precise makes the RSX code run slowly through the same steps. |
Freezing still occurs with ZCULL accuracy set to approximate, unfortunately. Other settings for this test: RSX FIFO accuracy was set to Atomic and Driver Wake-Up Delay at 280. Tested against the latest commit 6bb0106. I don't believe there's any way to prevent this title from freezing, I've tried many different settings. Here's a log from it freezing after about 30 minutes of play in zombie mode, single player: RPCS3.log.zip |
Thanks for confirming. In that case, this likely has nothing to do with RSX anymore. |
Sure thing. Looking at the logs you'll see the same |
Update: Actually scratch that, I've adjusted just about every setting exposed to at least reduce freezing occurrences (same for several others like #16393 above and #16087), but all these titles eventually freeze regardless. |
I have settings I've used for the Assassin's Creed series to almost remove all freezing.
There were changes to Accurate RSX Reservation Access since my last full test. And these Call of Duty Black ops games display different reasons for freezing than the games these settings have been tested with. Still worth trying any combination of these settings if desired. |
Thanks @Darkhost1999, that's helpful and I'll try those combinations with some of the other titles. Which AC titles exhibited freezing in your testing? I ask because I tested AC1 to completion and it never froze. It's also important to distinguish between freezing and crashing. The titles above all freeze, while others (such as in #16452) cause RPCS3 to crash entirely. I don't know if your settings would help with crashing issues but I can try them anyway. |
Brotherhood and beyond. |
That's exactly what happens with #16087 (music playing, gameplay frozen), I haven't checked logs for comparative indicators but I'll try the settings there anyway. Also, realizing we're going OT but if you have a chance to document your settings in relevant entries like here I'm sure that would help others in the future. |
|
Ah thanks, I was mostly thinking of the two non-java mode settings but I suppose the important bits are already in there. |
One more question, I noticed you mentioned this setting but I could not find it:
The closest I could find was in the game-specific config file, there's this:
...which seems to be the same as "Accurate PPU Non-Java Mode" though it's greyed-out on this test system for some reason. Is that what you meant? |
Yes, that's it and it's not implemented for PPU LLVM so it needs to be used with PPU Interpreter. |
#13602 (comment)
Old issue
When booting BLUS31011 updated to 1.19 the game crashes at the press start screen if using 100% default configuration. But by changing zcull to approximate or relaxed we can actually play the game. This same fatal error and device lost affects so many of my games that I am glad to have obtained this game and am able to make a replicable debug output log. ``` ·F 0:00:58.200436 {RSX [0x80558bc]} 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) (in file C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\rpcs3\Emu\RSX\VK\VKQueryPool.cpp:45[:4], in function poke_query) (in file C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\rpcs3\Emu\RSX\VK\vkutils\shared.cpp:107[:24], in function die_with_error) ```
Attach a log file
Debug.log
Crash.log
Working-Approximate Zcull Accuracy.log
System configuration
Ryzen 5 3600
GTX 1660 Super
Windows 11
The text was updated successfully, but these errors were encountered: