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

Final Fantasy XIII: Game crash at chapter 9 video sequence [PPU Recompiler] #8911

Open
Shoegzer opened this issue Sep 16, 2020 · 13 comments
Open

Comments

@Shoegzer
Copy link

Final Fantasy XIII [MRTC00003] crashes at the video sequence near the beginning of chapter 9, with the following message:

·F 0:02:10.180219 {PPU[0x1000000] Thread (main_thread) [0x006ca214]} VM: Access violation reading location 0x1f (unmapped memory)

To recreate, start the game from the attached save, then walk the character (Lightning) to the far end of the hallway, talk to the man on the left to advance to the video sequence. The video sequence will play for roughly 5-10 minutes (you can skip through with the start button) but eventually the screen will go black and will not proceed further.

Note that changing PPU Decoder to Interpreter (fast) resolves this issue, so a temporary workaround would be to switch to the interpreter until the next game save, then switch back to the recompiler.

Tested with commit 9ff0b46, though this has been occurring before this time as it was reported on 2019/12/23, here.

Test system is intel i7-7820HK, Nvidia GTX-1070M with drvier 440.100, linux mint 20, kernel 5.4, self-compiled with gcc 9.3.0.

RPCS3.log
FF13_Save.zip

@GitArUs
Copy link
Contributor

GitArUs commented Dec 2, 2020

@Shoegzer I can't reproduce it when using current master (I mean the game does not crash).
This issue looks exactly like #8860, which still happens for me.

@Shoegzer
Copy link
Author

Shoegzer commented Dec 2, 2020

Interesting, I'm tempted to close this as it's been several months since I reported this issue and there have been many fixes since then. I hesitate because it's been a long-standing issue according to the game compatibility thread. Another person reporting success would tip the scales to closure.

@GitArUs
Copy link
Contributor

GitArUs commented Dec 6, 2020

Don't close this. Maybe I am just lucky that the game does not crash for me in that particular moment. However it crashes randomly later in chapter 9 with similar messages in the log. The location is "Palamecia - Bridge Access", the last area before boss fight. Crashes happen from time to time after battles (just before battle score should appear) or even during loading a savegame. For me the game crashes only in that particular area, and never before or after (I'm near end of chapter 10 now).
Log says either "violation reading location" or "violation writing location" (or both). Attaching examples of logs and the savegame. Crashes in logs _1 and _2 were during load, in _3 after battle.
RPCS3_logs.tar.gz
(Edit - Wrong save file was attached previously)
Save-49.tar.gz

@GitArUs
Copy link
Contributor

GitArUs commented Dec 31, 2020

Crash can be avoided by setiing "Accurate PPU 128 Reservations" on Debug tab to anything other than "Disabled". Tried with "Always enabled", 1 and 14.

@FinishedFragment
Copy link

Tested with fe17c83, still freezing. Did not try the debug tab option yet but it magically worked after skipping the cutscene once for some reason.

@MSuih
Copy link
Member

MSuih commented Aug 5, 2021

Is this still an issue? We've gotten claims from people that they haven't encountered any noteworthy issues when playing through the game?

@Shoegzer
Copy link
Author

Shoegzer commented Aug 5, 2021

Thanks for the reminder @MSuih. Can those people comment here as to what settings they used? I hope they realize it only starts to manifest late in the game, beginning with the chapter 9 cutscene noted above. I'm not entirely sure if this issue persists myself as I don't have the game anymore, but hopefully they can test against the save file I posted above.

Also, I would think both this issue and #8860 should be given the same treatment i.e. remain open or close. I didn't test "Accurate PPU 128 Reservations" ot "Driver wake-up Delay" with XIII-1 and while it does seem promising as a workaround, it's not really a "fix" per se as mentioned in the thread.

@GitArUs
Copy link
Contributor

GitArUs commented Aug 5, 2021

I have tried it moment ago. It still crashes. And now I can even reproduce the crash described by @Shoegzer (at the end of cutscene sequence). Does not happen every time, but still happens. "Accurate PPU 128 Reservations" does not help in this case, but it do helps in the second place I mentioned above.
Edit:
Forgot about "Driver wakeup delay". Together with "Accurate PPU 128 Reservations" it eliminates the crash or at least makes it happen much less often. So it do looks like this one and #8860 are the same issue.

@YuriNator557
Copy link

Attempted to replicate recently on build v0.0.17-12611-f745971c with all default settings, crash is still replicable but it took multiple attempts to have it crash during the video sequence (7 in my case).

@neonoafs
Copy link

I have tried it moment ago. It still crashes. And now I can even reproduce the crash described by @Shoegzer (at the end of cutscene sequence). Does not happen every time, but still happens. "Accurate PPU 128 Reservations" does not help in this case, but it do helps in the second place I mentioned above. Edit: Forgot about "Driver wakeup delay". Together with "Accurate PPU 128 Reservations" it eliminates the crash or at least makes it happen much less often. So it do looks like this one and #8860 are the same issue.

Im playing FFXIII [MRTC00003] and I can confirm that this solves the problem. I'm using the latest build till now 0.0.20-13239-bb65e679 Alpha

@Behodar
Copy link

Behodar commented May 28, 2022

I can confirm that the game still crashes at the point mentioned in the first post under the current build (0.0.22-13655-5ad4b624), so the underlying issue is still present.

There is no "Interpreter (fast)" option for PPU Decoder in this build, however setting it to "Interpreter (static)" resolves the issue (I usually have it on "Recompiler (LLVM)"). I'm not sure where to find the "Accurate PPU 128 Reservations" option listed above.

  • SYS: RPCS3 v0.0.22-13655-5ad4b624 Alpha | master
  • SYS: Intel(R) Core(TM) i9-10910 CPU @ 3.60GHz | 20 Threads | 16.00 GiB RAM | TSC: 3.600GHz | AVX+ | FMA3
  • SYS: Operating system: macOS, Version: 12.4.0
  • SYS: Current Time: 2022-05-28T17:14:03
  • RSX: Found vulkan-compatible GPU: 'AMD Radeon Pro 5700 XT' running on driver 0.2.894
  • SYS: Firmware version: 4.88

@whitezombie2000
Copy link

whitezombie2000 commented Feb 25, 2023

I can confirm these issues with the latest build 0.0.26-14743. I am using Vulkan with the default setting. The only options I turned on were under the GPU menu Additional Settings, VSync, Multithreaded RSX, and Asynchronous Texture Streaming. I am not using the 60fps patch.

Specs
Lenovo Legion 5
Windows 11 Pro 22H2 OS Build 19045.2604
AMD Ryzen 5 5600H
GeForce RTX 3050 Ti
32GB DDR4-3200

Cutscene Error at Chapter 9: The Sanctum Skyfleet: The Lindblum - Airship Hangar

Load the save Chapter_9_The_Sanctum_SkyFleet from the zip, talk to Rygdea to initiate the cutscene. Sometimes the cutscene will not crash. It crashed once after three attempts and then it crashed twice after three more attempts. See the file FFXIII_Chapter_9_Cutscene_Error1.txt from the zip for the full log.

Error
F {PPU[0x1000000] Thread (main_thread) [0x0071cc38]} VM: Access violation reading location 0x426c20c4 (unmapped memory)

Battle Crash Error at Chapter 9: Luck Be a Lady: The Palamecia - Bridge Access

Load the save file Chapter_9_Luck_Be_A_Lady1 from the zip. Proceed to fight some enemies and it will eventually crash at the end of a battle. See the log files FFXIII_Chapter_9_Battle_End_Error1.txt and FFXIII_Chapter_9_Battle_End_Error2.txt for the full log. As noted above by GitArUs, I enabled the Debug menu, I set Accurate PPU 128 Reservations to 1, and the crashes do not occur. I fought enemies for an hour with no issue when this is enabled.

Error 1
E VM: Access violation writing location 0xffdead00 (unmapped memory)
E VM: Access violation reading location 0x480 (unmapped memory)

Error 2
E VM: Access violation reading location 0x180 (unmapped memory)

Save Load Error at Chapter 9: Luck Be a Lady: The Palamecia - Bridge Access

Load the save Chapter_9_Luck_Be_A_Lady2 from the zip. It will crash most of the time and freeze when at the loading screen. See the three files FFXIII_Chapter_9_Loading_Save_Error1.txt, FFXIII_Chapter_9_Loading_Save_Error2.txt, and FFXIII_Chapter_9_Loading_Save_Error3.txt for the full log. As noted above by GitArUs, I enabled the Debug menu, I set Accurate PPU 128 Reservations to 1, and the crashes do not occur when loading the save.

Error 1
E VM: Access violation writing location 0xffdead00 (unmapped memory)
E VM: Access violation reading location 0x0 (unmapped memory)
E VM: Access violation reading location 0x50 (unmapped memory) x2

Error 2
E VM: Access violation writing location 0xffdead00 (unmapped memory)
E VM: Access violation reading location 0x0 (unmapped memory)

Error 3
E VM: Access violation reading location 0x50 (unmapped memory)

FFXIII_Logs_and_Saves.zip

@Jonathan44062
Copy link

I'm going to give my save fiile, where I'm at chapter 9, that's where the game crashes, that will help us to check that when it's fixed, confirm us.
The game serial is MRTC00003
https://www.mediafire.com/file/2lv42dsgq3wrzof/MRTC00003-00%25282%2529.rar/file

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

No branches or pull requests

9 participants