Closed ZheksOne closed 2 years ago
Missing build that introduced the regression to be labeled as a regression
Maybe setting "Accurate PPU 128 Reservations" on Debug tab to anything other than "Disabled" will help like in other cases ?
Maybe setting "Accurate PPU 128 Reservations" on Debug tab to anything other than "Disabled" will help like in other cases ?
Thanks for the suggestion mate but does not work unfortunately.
One more try - in addition to above set "Driver wake-up Delay" to 600 us on advanced tab (or experiment with different values).
One more try - in addition to above set "Driver wake-up Delay" to 600 us on advanced tab (or experiment with different values).
Nope...thanks
The memory issue happened in the build 0.0.11-10791-190822c2
In v-0.0.11-10790-d000d648 boot and run as inteded.
That'd be PR #8663
unmapped memory error also happen in others games and look how the emulator in few seconds try to allocate more of 1 GB RAM being that not had need to do it. Ultimate Marvel VS Capcom 3 selecting an stage with few details and even not moving both players characters randomly the game crash with "unmapped memory" or "trying to allocate 1 GB and was possible only 200 MB" (the values are example because the "trying value" is 5 times the current allocated). Is how if the emulator try to allocate memory not need because of wrong code.
This issue appears to be present again. Seems to be happening in Guilty Gear Xrd Sign version 1.04
I don't think it ever left since I reported this?
I starting to wonder if the issue could be related to timing since the emulator is trying to read unmapped memory which could imply that something could be happening before it is supposed to.
I had the same issue, the problem was solved by simulating a psn network. You can see the orange warnings where the matchmaking threw an error.
Please test with https://github.com/RPCS3/rpcs3/pull/11887
The Guilty Gear Xrd-titles fail to start anymore on latest revisions on default config with an "unmapped memory"-error. I unfortunately don't know from which revision this started but I'd say a few weeks. The compatibility guide also mentions it as playable. Sometimes it does starts once after reinstalling firmware I believe but then the 2nd time it fails with this error again, even after removing all caches.
Happens on for instance BLUS31588 and NPUB31555
MMy specs:
I hope I filled this in correctly, thank you. RPCS3.log