"MEM: Access violation" on [BLES01102] - Ar Tonelico Qoga - RPCS3 v0.0.16-12251-cacb852a

[RaulDJ]

As I think this issue always happened with this game in some way or another, I'm reporting it now:

The game randomly crashes with a memory access violation error when doing almost anything. In my case, I'm just alternating between two different maps on the same "level".

This is the save file so anyone can reproduce it: just walk to the left until the map changes, and then walk to the right until it changes again. Do this a couple of times and sooner or later you'll get the memory access error, it always happens: Savedata.zip

This is the emulator log. Additionally, the emulator kills itself when you try stopping the emulation after getting the error:

Log from v0.0.5-7576 Alpha [2018-12-11]: RPCS3.zip

Log from v0.0.16-12251-cacb852a: https://github.com/RPCS3/rpcs3/issues/5418#issuecomment-841271500

[hypostock]

how do you manage the artificial Shaking gesture? what program that you use? thanks … On Tue, Sep 28, 2021 at 9:30 PM hypostock @.***> wrote: I barely managed to haggle my way through the bad ending and complete the game by saving in places where I set my PPU to fast and SPU to ASMJIT and then alternatively switch back to LLVM on both and alternating between OpenGL and Vulkan. Need an artificial Shaking gesture to work through the purge otherwise the myu boss battle is impossible to finish — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5418 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATTSM2E3USU2OJJCZDNMQ6DUEHGSBANCNFSM4GKC2YIA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

btw This person has completed the DS4 full functionality with artificial shaking gesture as well as shaking gesture recorded from the gyroscope via an android phone

https://github.com/r57zone/DualShock4-emulator

you might want to check and try this one out... just tested AT3 with purge and it works after a bit of effort and adjustment

[hypostock]

Today , i played till i reached the are where you have to go to KU in the tower district.. a new form of memory error as appeared. Instead of showing unmapped memory its giving read only memory now

[RaulDJ]

Today , i played till i reached the are where you have to go to KU in the tower district.. a new form of memory error as appeared. Instead of showing unmapped memory its giving read only memory now

Were you able to save the log? Maybe it would be interesting to have it here too.

[alxproject]

for me, still the same error U_u RPCS3 v0.0.18-12948-2af2db2c RPCS.log.zip

[alxproject]

hello, new version, same error U_u RPCS3 v0.0.19-12978-1a0392bf RPCS3.log.zip

[alxproject]

Hi, same error RPCS3.v0.0.21-13412-72b2876b RPCS3.v0.0.21-13412-72b2876b.log.gz

[alxproject]

Hi, same error RPCS3 v0.0.23-14034-c51d3b54 RPCS3.log.gz

[Astranabeat]

Will this ever get fix?

Still got random crash but still manage to play it by saving often. Now the game crash every time I go back to starting area. Need money for Dive to progress. Stuck now because go back to grind money was immpossible due to crashing.

I don't know this is relate or not but I never crash until I need to Purge to progress. So I emulate ps3 controller. Now I can purge but the game crash like crazy. If I don't use ps3 emulate controller, the game crash less often but maybe it just placibo so idk. Can't confirm.

[alxproject]

Hi, testing again, same error RPSC3 v0.0.27-14813-fe51c7b9 RPCS3.log.gz

[Lev-ku]

Still crashes mainly while changing areas, initiating battles, and consistently when crafting items. [RPCS3 v0.0.28-15215-073b723c] (1650ti, i5-10300H, 8 GB's Ram, Windows 10, GeForce Drivers Version: 536.23) RPCS3.zip

[rspretty]

Changing RSX FIFO Accuracy to "Ordered and Atomic" increased stability.

[al0xf]

Take a look at this old thread that predates the emulator: https://gamefaqs.gamespot.com/boards/976762-ar-tonelico-qoga-knell-of-ar-ciel/58515483

Crashes on loading screens, when crafting items, at the start of battle etc. Sound familiar? Also from my own experience it crashed a few times during a full playthrough on a real PS3.

So the game itself is just buggy and unstable, and small timing inaccuracies in the emulator exacerbate it. Adjusting different settings in the emulator will affect timings and stability in one way or another for different people, but that's all you're doing, playing with timings (or in more technical terms, the game likely contains race conditions and other concurrency issues)

The emulator would need to run this game at some performance level exactly relative to a real PS3 for it to "only" crash a few times during a full playthrough probably.

I think someone with a lot of time, patience, and knowledge could probably make a patch or two and just fix the game itself. Since the crashes are not truly random and always happens at loading screens and such it should be easier to identify. Maybe something crude like adding a few thread sleeps here and there is enough. Otherwise I think this game will remain unplayable for many more years to come...

[AstralPhnx]

Take a look at this old thread that predates the emulator: https://gamefaqs.gamespot.com/boards/976762-ar-tonelico-qoga-knell-of-ar-ciel/58515483

Crashes on loading screens, when crafting items, at the start of battle etc. Sound familiar? Also from my own experience it crashed a few times during a full playthrough on a real PS3.

So the game itself is just buggy and unstable, and small timing inaccuracies in the emulator exacerbate it. Adjusting different settings in the emulator will affect timings and stability in one way or another for different people, but that's all you're doing, playing with timings (or in more technical terms, the game likely contains race conditions and other concurrency issues)

The emulator would need to run this game at some performance level exactly relative to a real PS3 for it to "only" crash a few times during a full playthrough probably.

I think someone with a lot of time, patience, and knowledge could probably make a patch or two and just fix the game itself. Since the crashes are not truly random and always happens at loading screens and such it should be easier to identify. Maybe something crude like adding a few thread sleeps here and there is enough. Otherwise I think this game will remain unplayable for many more years to come...

As it stands, I recently did a full playthrough on actual PS3 hardware and didn't experience a single crash whatsoever in my 55 hour playthrough, so I don't think this is an entirely accurate assessment to make. I'd argue those crashes are probably due to people playing the game in a PS3 that was already not in the best internal shape potentially exasperating the errors.

Either way, it seems accuracy is the name of the game here. Worth noting is the game installs about 5 gigs of data to the internal hard drive upon first launch which may or may not be related as I'm not sure how exactly it uses that 5 gigs of drive data to accelerate loading etc.

In general, I have to wonder how much of this could be solved by a setting that say, simulates data throughput of an actual PS3 Blu-Ray drive, similar to OpenPS2Loader's Mode 1 which emulates the speed of an actual PS2 DVD drive when running games off the HDD and fixes A LOT of issues.

[AstralPhnx]

Also for those looking at this thread, after running some personal tests I've found decent stability with the following settings

PPU Decoder: Interpreter (Static)

SPU Decoder: Recompiler (LLVM) (this seems to be what makes or breaks the battle music, interpreter breaks it but Recompiler seems to make it work without any noticeable stability issues)

Advanced Menu:

Enable Accurate RSX Reservation Access and Accurate SPU DMA

Set RSX FIFO Accuracy to "Ordered and Atomic"

Set Driver Wake-Up Delay to "100μs".

This provides an overall playable framerate, not as good as an actual PS3, but absolutely playable at native 720p on my rig (Ryzen 5 3600, 32GB Ram and an RX 7800 XT) with greatly minimized crashing

[al0xf]

Take a look at this old thread that predates the emulator: https://gamefaqs.gamespot.com/boards/976762-ar-tonelico-qoga-knell-of-ar-ciel/58515483 Crashes on loading screens, when crafting items, at the start of battle etc. Sound familiar? Also from my own experience it crashed a few times during a full playthrough on a real PS3. So the game itself is just buggy and unstable, and small timing inaccuracies in the emulator exacerbate it. Adjusting different settings in the emulator will affect timings and stability in one way or another for different people, but that's all you're doing, playing with timings (or in more technical terms, the game likely contains race conditions and other concurrency issues) The emulator would need to run this game at some performance level exactly relative to a real PS3 for it to "only" crash a few times during a full playthrough probably. I think someone with a lot of time, patience, and knowledge could probably make a patch or two and just fix the game itself. Since the crashes are not truly random and always happens at loading screens and such it should be easier to identify. Maybe something crude like adding a few thread sleeps here and there is enough. Otherwise I think this game will remain unplayable for many more years to come...

As it stands, I recently did a full playthrough on actual PS3 hardware and didn't experience a single crash whatsoever in my 55 hour playthrough, so I don't think this is an entirely accurate assessment to make. I'd argue those crashes are probably due to people playing the game in a PS3 that was already not in the best internal shape potentially exasperating the errors.

Either way, it seems accuracy is the name of the game here. Worth noting is the game installs about 5 gigs of data to the internal hard drive upon first launch which may or may not be related as I'm not sure how exactly it uses that 5 gigs of drive data to accelerate loading etc.

In general, I have to wonder how much of this could be solved by a setting that say, simulates data throughput of an actual PS3 Blu-Ray drive, similar to OpenPS2Loader's Mode 1 which emulates the speed of an actual PS2 DVD drive when running games off the HDD and fixes A LOT of issues.

This is a good point. I think my PS3 is in good shape, but it is upgraded with an SSD which the entire ripped game resides on. But even with an HDD I would imagine there is maybe some difference between an old 20 GB model and a "modern" 500 GB one... It is known that an SSD upgrade improves loading times a little in some games, which indicates that the PS3 OS does not necessarily "lock things in" so to speak.

Maybe one could roughly simulate slower PS3 I/O by putting rpcs3 and the game files on a slow USB 2.0 HDD or flash drive and see if it makes any difference.

[2565904536]

Also for those looking at this thread, after running some personal tests I've found decent stability with the following settings

PPU Decoder: Interpreter (Static)

SPU Decoder: Recompiler (LLVM) (this seems to be what makes or breaks the battle music, interpreter breaks it but Recompiler seems to make it work without any noticeable stability issues)

Advanced Menu:

Enable Accurate RSX Reservation Access and Accurate SPU DMA

Set RSX FIFO Accuracy to "Ordered and Atomic"

Set Driver Wake-Up Delay to "100μs".

This provides an overall playable framerate, not as good as an actual PS3, but absolutely playable at native 720p on my rig (Ryzen 5 3600, 32GB Ram and an RX 7800 XT) with greatly minimized crashing

Set Thread Scheduler to RPCS3 Scheduler works better