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

Tales of Graces f [NPUB31133] [BLUS30903], crash on startup #11897

Open
ghost opened this issue Apr 29, 2022 · 5 comments · May be fixed by #11946
Open

Tales of Graces f [NPUB31133] [BLUS30903], crash on startup #11897

ghost opened this issue Apr 29, 2022 · 5 comments · May be fixed by #11946

Comments

@ghost
Copy link

ghost commented Apr 29, 2022

Quick summary

The game simply refuses to boot through the cache building process, be it the HDD or disc version of the game, both ending in the same error (albeit with slightly different error message wording).

Details

(This is running on emulator version 0.0.2.1-13532-8316469c Alpha, latest at the time of writing)
I have seen footage of this game working on older versions of RPCS3 (circa 2020), before I started using the emulator myself, and it seems that SOMETHING must have broken between that and mid-2021, when I first tried to play this game.
Compatibility reports also LIST it as either in-game or playable, but said reports are also from 2020, before compatibility for the game seemingly broke.

Immediately after either generating or loading the shader cache data, the game will IMMEDIATELY hang on a black screen, with a cellGameGetParamString-type error message that was only recently updated to show more detail. This does not crash the entire emulator, but the actual game window itself has to be manually closed and cannot be stopped from RPCS3's menu.

Both versions are being run under all the recommended wiki settings (VBlank rate and the like are correctly set in their custom configuration).
The .rap file on the HDD version shouldn't be missing, as I loaded it into RPCS3 immediately after installing the game itself (and I have tried uninstalling and reinstalling both things multiple times, just to be sure).
Both OpenGL and Vulkan show the same results, so it's unlikely to be caused by either renderer.
My GPU drivers were a couple months behind at first, but updating them (and clearing the cache) did not fix the issue either.
Other games (including Tales of Xillia 1/2 which from what I've read used to have similar issues) have run perfectly on this same system.

The error, as stated, is present in both the DIGITAL [NPUB31133] and DISC [BLUS30903] versions of the same game.

EDIT: I should mention, I have seen one issue on this same github which also mentioned "deadlocking" on several games including this one, but it only referred to disc versions and NOT installed digital versions; that aside, I feel like the recently-updated error log data might shed a bit more light into things.

Please attach RPCS3's log.

RPCS3.log.gz (NPUB31133, HDD version)
RPCS3.log.gz (BLUS30903, Disc version)
(I would also provide screenshots, but as I've said the game simply hangs before it even boots properly so there isn't much to screenshot to begin with)

Please provide your system configuration:

OS: Windows 10 Pro (build 19043.1526)
CPU: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz 2.90 GHz
GPU: NVidia GeForce GTX 970 (Driver version 512.15, latest at the time of writing)
2x 8GB RAM (DDR4)

@realmyrid
Copy link

I'm getting the same issue on my steam deck.
However... the game launches and plays fine on my Win11 desktop. Not sure what the difference would be. I only know enough about Linux to be dangerous with it, so I haven't had any luck getting it to work.
I only have the disc version, if it matters.

@ghost
Copy link
Author

ghost commented May 4, 2022

Okay, update... after fiddling around with settings some more, APPARENTLY it manages to run when launched in "default settings" mode? Though default launch completely prevents me from using any of the other settings that fix other issues with the game, such as VBlank rate for the dynamic framerate the game uses.
So i'm really not sure WHAT it is exactly that's killing the game, but whatever it is it's not documented in the wiki's recommended settings, or any other issue trackers it has. My global settings were never too far from the defaults, I don't think I changed much more than the renderer and the resolution scale.

@Megamouse Megamouse linked a pull request May 5, 2022 that will close this issue
@Wonderwize
Copy link

Looking at your log, I'm getting similar error messages on my Japanese version of Graces f [BLJS10093], which to be fair doesn't seem to be officially supported at all.
The errors seem to be at the same addresses even (0x80010003 and 0x8002cb21).

However, unlike you I can't get it to run at all with the default settings.

@elad335
Copy link
Contributor

elad335 commented May 27, 2023

Test with #13917

@Nyantcha
Copy link

This game is getting an unsual error: F {PPU[0x1000000] Thread (main_thread) [0x0047c0b0]} VM: Access violation reading location 0xc (unmapped memory)

The game used to work just fine but now refuses to even load

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

Successfully merging a pull request may close this issue.

4 participants