-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 X/X-2 HD [BLES01880]: Mem access violation during bossfight #5080
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Upload TTY as well, the log indicates stuff is being written to TTY.log too |
Here are the logfiles for a 720p play, crashes at the exact same place. Address is slightly different |
Likely fixed in the past few days. Retest. |
@kd-11: Tested with latest master ed8aa77, this was not fixed. Crashes at the exact same place. I have previously cleared all possible caches.
Log files are attached. |
Still occuring on latest master. |
I signed up to make this report. Bug and crash still exist in the 7470-43b75ccf build, can be reproduced consistently and without fail. Always occurs at Yunalesca's first transition after losing 24000 HP. Note that I'm using the NA release, BLUS-31211. System specs are a 2600K Intel CPU, 980ti card, 16gb of ram, Windows 7 64bit. My system is patched and drivers are up to date. Crash occurs regardless of settings. I have tried a large variety of settings including up what what is arguably the most "safe mode" with precise decoders, 1 SPU and compile thread(s), Vulkan renderer, default res, and no scaling. The error is same as others reported, MEM: Access violation at xxxxxxx, however the exact address is different. I have tried this with a fresh install of RPCS3 so cache should not be a factor, and always restart the program after making any changes to settings or after any crashes. |
One quick addition. I went back to an older build, 7022-3d8223fcc, and the same problem exists. The error is the same MEM access violation at the same address. Edit - Did some more research. Tried about twenty different builds from the latest 7480 today all the way back to a 0.0.3.6 from Oct of 2017 I found on EmuCR. All produce the same crash, but the exact memory address is varies depending on build date. Also realized I should have posted the log files, apologies for that. The log files below are from the 7480-11681f02 build. |
Finally reached this stage in my playthrough of FFX HD [BLUS31211] and I can confirm that the bug still occurs in ad10eb3. The game is otherwise emulated flawlessly, so it would be really nice to get a fix for this issue. System specs (Mageia 7 x86_64):
I'd be happy to provide logs and save files, though I believe the ones in OP might still be relevant. If anyone can advise on how to get more debugging information around the crash, I can do some testing. |
Reproduced the issue anyway on b9130dd to be thorough. As for others, the crash is due to a memory access violation:
Steps to reproduce:
When it crashes, the game is paused in the debugger, and pressing Play will make the same memory access violation happen again. When I tried, pressing Play several times in a row allowed the game's animation to proceed further by a few frames, until it was fully stuck (at least no visual progress anymore after ~300 presses, FPS at 0.06). |
Huh, still occurring. @Nekotekina @kd-11 can you make a patreon donation with a specific request, e.g. to investigate this specific bug? At the one year anniversary of this bug I'd be happy to give you money for this to be fixed. |
Not directly, you can't post bounty through patreon. |
Upload log with latest master. |
Sorry for the delay, my laptop was in repair. I think my logs are similar to @jorgensond's, but uploading nevertheless: 0.0.6-8395 1b140c8 Would it be useful to take a capture at the moment of the access violation issue? |
Can you retest with this build? It's a hack but the answer may lead me to a proper fix. |
I tried that Windows build through WINE but the initial PPU compilation was taking ages, so in the end I compiled it from source (current master fcc75c8) + the two patches from https://github.com/elad335/rpcs3/commits/sys_prx It stalls at the same event. There seems to be one instruction more in the call stack. |
English only, as other people need to understand what you write |
sorry hello good morning how are you |
No, no one has figured out a way around it yet and the problem still exists in the latest builds of RPCS3, If you're already at the final boss, I'd suggest just watching the ending on YouTube. No point in waiting for a fix if you've already got this far in the game, it could take awhile before a dev looks into it. |
@akien-mga still issue? |
Reupload log if it is. |
I tried but
(no window appears) I tested |
If you read the thread, you would see that Eladash looked into it back in March this year, however sadly he wasn't successful. RPCS3 is open-source, anyone who wants to is free to investigate the issue and fix it. RPCS3 is in Alpha, looking into game specific issues when there is a slew of major general things to work on is going to be a low priority. There is also 554 issues open right now, and a lot more not reported on GitHub. Not to mention when changes are made sometimes there is a regression. Be patient, and update the issue every 4-6 months to ensure devs know it is actually still broken other wise they might be wary of even looking at it. |
just want to highlight this for visibility, still an issue on version 0.0.15-12048-f64a7bb8. I'm having issues getting the logs, as it appears they're not being saved somewhere. I'll try and get a copy from the Console next time I try this out. |
Hi all! Bumping that as of 0.0.17-12573-8c3a4c26, also running into the freeze after the first transformation. Logs also disappear, RPCS3 fully crashes after I try to close the game |
Hi all! Bumping that as of 0.0.17-12660-f44e50b9, persisting issue relating to a freeze. I've notived that the memory access address changes between version releases. Not a strong software developer, so unsure if that is a useful observation. Mem address is 0x2e0cb80 playing on Linux build. screenshot below, the log appears to have not been updated in a long time - could be something wrong with it found in ~/.config/rpcs3/RPCS3.log.gz sudo gunzip results in unexpected end of file |
Maybe we should ban sceeenshots of main window, anyways if you want to update an issue upload the log file. |
A lot of persons have uploaded the log file myself included
…On Tue, Aug 24, 2021, 8:59 PM Eladash ***@***.***> wrote:
Maybe we should ban sceeenshots of main window, anyways if you want to
update an issue upload the log file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5080 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVI4V3GDWAL7L24WBIF3L3T6RE6RANCNFSM4FTGNF3A>
.
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&utm_campaign=notification-email>
.
|
The last log file is from a year ago |
On Wed, Aug 25, 2021 at 11:18 AM Ani ***@***.***> wrote:
The last log file is from a year ago
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5080 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVI4V6O4PZPDLMKOSQDD3TT6UJWFANCNFSM4FTGNF3A>
.
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&utm_campaign=notification-email>
.
Yes and I believe there where other uploads before all with the same memory
access violation error
|
Not the point. why are you bumping an issue without an updated log file |
The last time I tried playing was a few months ago and it was the same so ignored it will run it later and upload a updated log file |
Original reporter from 3 years ago here, I've gathered new logs against 4e139ee, see: RPCS3 also crashes after the access violation has occurred, the stop-button is pressed and the OK button of this dialog is clicked. But the logs were retrievable in their |
Are any of you available on discord? Github is really annoying to debug something with anyone. Not today though but for later. |
Yes, I've joined the rpcs3 discord server and shot you a message there. |
Hey guys i have the same issue, does anyone figured out a way to bypass it ? Maybe a save post fight on the thread might just do it for now, if any can be found. And of course if someone have the knowledge and time to fix it i would love to end my story :) Good luck |
Add me to the list of folks who has run up against this wall of a bug. Sad that the problem has stayed unresolved 4 years after it was first reported. |
Has anyone had any luck resolving this issue? Playing on steamdeck, just ran into this problem. Literally the only issue I have had running it, but obviously I am stuck. Please help |
Why would you retest it on master build when ELAD opened a pull request a few hours ago when a fix that needs testing? See #12921 |
I thought it was already pushed to the master build. I'm sorry, I don't fully understand how to test if it is still in pull request status. I would love to test if someone can give me a hand |
Go to the PR |
Thanks for the help! Was able to load up the PR 12921 Build. Successfully made it passed the phase 1 part of the battle! Thanks so much! I will also post directly on the PR #12921 to confirm working. |
Was able to get past the boss fight. However, trying to save and "overwrite" the old save results in another crash. I will attach logs. Edit: I will try to create a new save, instead of overwriting, and see if it fails or not. Edit 2: Seems to have work to create a new save, instead of overwriting. Not sure what was going on there, but seems fine this way. |
"Then download the artifact and extract the zip ontop of your current rpcs3 folder" I downloaded the artifact and extracted the zip file inside, to my rpcs3 folder. When booting up the game, no pop-up message occurred and the game still hung upon defeating the first form of the boss. What am I doing wrong? |
There is another .7z file titled rpcs3-v0.0.25-.......u get the rest. unzip that into the rpcs3 folder. Then you should get the message |
Nice - the fix works! Thanks Elad! You're the man! Finally we can get past that damn Yunalesca now! |
Hi guys! amazing you fixed the issue!!! i've been following this issue since years waiting for a solution :D |
I've been watching this issue for too long...I maxed the Sphere Grid, made some Break Damage Limit Weapons, I did everything I could think of waiting for this moment. 140 hours of Gameplay, most of it stuck at this boss lol. I can confirm in the related PR this issue appears resolved!! We may have FFX HD finally be fully playable after so long! thank you Elad, this really means a lot to me. It's my favourite game. |
On another note, the FMVs are now emulated perfectly. Previously they had been choppy and glitchy. Good job! |
Problem:
Final Fantasy X HD remaster can't be played through because of a fatal error during a boss fight. This error always occurs reproducably.
During the second-last boss fight of the game with Yunalesca, once you defeat her first-stage (24,000HP), the game crashes at the place where the transformation sequence into her second form should play.
Related messages for that address
Settings:
This bug must have existed for a long time, because I've started that playthrough at the beginning of the year and that bug already stopped me, and it's still there.
Attached are the RPCS3 logs and the savefile for easy reproduction.
RPCS3.log.gz
BLES01880SAVEDIR--------------1.zip
The text was updated successfully, but these errors were encountered: