RPCS3
Freezing Screen Bug in Call of Duty Black Ops 2 on RPCS3
Quick summary
When I'm playing Call of Duty Black Ops 2 using RPCS3, the game simply freezes and the following message appears in the log: 2 F {PPU[0x100000a] Thread (hang detect) [0x00463064]} VM: Access violation writing location 0x17 (unmapped memory). I'm using the most recent version of the emulator. How can I solve this problem?
Details
When I'm playing, even with good screen speed, in local mode with 3 players at a certain point the game simply freezes and the emulator and I have to restart the game. I've tried several configurations but none seem to work.
Attach a log file
Attach capture files for visual issues
No response
System configuration
=== System Information ===
Operating System: Windows 10 (10.0.19045) (AMD64) Processor: Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz
- Frequency: 2112.00 MHz
- Physical Cores: 6
- Threads: 6 RAM: 63.93 GB Video Card: NVIDIA GeForce RTX 3060
Other details
No response
I got this same error when testing a 4 player splitscreen match. I changed RSX Fifo accuracy to Atomic and tested again. It lasted a whole match without crashing. I dont know if it is a permanent fix or just luck, but you could try that and see if it fixes your issue
I got this same error when testing a 4 player splitscreen match. I changed RSX Fifo accuracy to Atomic and tested again. It lasted a whole match without crashing. I dont know if it is a permanent fix or just luck, but you could try that and see if it fixes your issue
If I'm not mistaken, I've already tried this. But I'll see if it works. I've tested a lot of settings. It could be some conflict in the game.
@OscarZarcoG if you don't stop posting AI slop in our issue tracker you will be banned from our repository.
@AniLeo Fix the bugs
It's an open source project - fix it yourself. You don't contribute, you're not entitled to anything. We fix the issues we want to with our free time. If you're just going to cosplay a developer by posting random ChatGPT generated slop, I don't know what you're doing here in the first place.
@AniLeo it was just an example code, it could have helped, it helped me, sorry, it will not be repeated.
@ProfAllanIFBA did you apply the wiki settings (RSX Fifo accuracy to Atomic) reported by @gamrXerus as fixing the issue?
@ProfAllanIFBA did you apply the wiki settings (RSX Fifo accuracy to Atomic) reported by @gamrXerus as fixing the issue?
As someone experiencing the same issue, putting the settings to atomic does not fix the issue
