Skip to content
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

[BLUS31152] Atelier Ayesha crash on swapping party members #6117

Open
HerrHulaHoop opened this issue Jun 21, 2019 · 8 comments
Open

[BLUS31152] Atelier Ayesha crash on swapping party members #6117

HerrHulaHoop opened this issue Jun 21, 2019 · 8 comments
Labels

Comments

@HerrHulaHoop
Copy link

For the most part, this game runs flawlessly. However, it does tend to crash randomly every now and then, keeping it from being playable. However, I found that the game will almost always crash when you try to swap one team member for another. This is the error that I get:
MEM: Access violation writing location 0xcd1518

I'll attach the log and savefile for anyone who wants to take a look at the this.
Log
Savefile

Steps to recreate the crash:

  1. Extract and copy the savefile to dev_hdd0\home\00000001\savedata
  2. Launch the game and load into the save
  3. Once ingame, press Start and select Hill Plaza
  4. Once you're at the location, move left till you see a wizard girl (Wilbell)
  5. Interact with Wilbell and recruit her by replacing one of your existing party members

Hopefully fixing this crash fixes or reduces the random crashes as well.

@AniLeo AniLeo added the Bug label Jun 25, 2019
@HerrHulaHoop
Copy link
Author

HerrHulaHoop commented Jul 26, 2019

Two new logs for the same issue. The reason I'm attaching two logs is that I got different errors for the same crash:

  1. First time, the game crashed at the same point but the emulator didn't. So the log showed an entirely new error of Unimplemented syscall syscall_988 -> CELL_OK. Not sure if it matters but my base resolution was set as 1920x1080 (the resolution is supported by the game).

  2. For the second run, the emulator crashed along with the game at the same point. This log showed MEM: Access violation reading location 0x0. This time I had set resolution to 1280x720.

Ayesha logs

Edit: Ignore the info on resolutions. Both crashes happen even on default resolution.
Also, noticed that the game seems to write to TTY log occasionally. Not sure how useful it is but attaching it all the same.

Ayesha TTY logs

@digitaldude555
Copy link

Still an issue.

@HerrHulaHoop
Copy link
Author

HerrHulaHoop commented Oct 29, 2020

Still an issue. Didn't happen immediately on the first switch but happened on the second. It's an improvement that could be down to my system upgrade.

Log
Log with access violation

@HerrHulaHoop
Copy link
Author

Still occurs. First time the game just closed itself abruptly without an error. Second time it froze on ·F 0:00:45.901887 {PPU[0x1000000] Thread (main_thread) [0x00570cbc]} VM: Access violation reading location 0x0 (unmapped memory) [type=u32]

Run 1: Log
Run 2: Log

@HerrHulaHoop
Copy link
Author

Still an issue - Log

@Megamouse
Copy link
Contributor

Please try again

@HerrHulaHoop
Copy link
Author

HerrHulaHoop commented Feb 5, 2023

Issue still occurs - Log

At this point, I should probably nuke all my saves and game data and start over fresh to see if there isn't an issue with the game or save data.

@HerrHulaHoop
Copy link
Author

Issue still occurs - Log

·F 0:01:08.626829 {PPU[0x1000000] Thread (main_thread) [0x0059f5dc]} VM: Access violation reading location 0x8 (unmapped memory)

Would be great if someone else could try this out and see if it happens to them as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants