Closed MageKing17 closed 3 months ago
http://forums.pcsx2.net/Thread-Audio-Error-In-Cutscenes
Quite a verbose game. Lots of invalid NAX and SSA logs and even an IOP mem dump!
Did you test this PR? https://github.com/PCSX2/pcsx2/pull/2275
@atomic83GitHub So I somehow missed the notification email back when you asked, but I just tried out the PR you mentioned and it doesn't affect this issue it all.
@MageKing17 Can you retest both your issues on the latest dev build and see if they still occur? Thanks.
Just fired up PCSX2 v1.7.0-dev-767-g2c7f54134
and both this and #1927 are still present.
Can you retest latest dev build with this? There have been some spu2 fixes which may fix the problem. Also if possible post a savestate right before the problem using latest dev build.
Issue still present in PCSX2 v1.7.0-dev-817-gc998a51f7
; attached is a save state at completion of the first mission, immediately before the ending cutscene:
Issue1928.zip
The log contents are largely the same as the pastebin from the original post, except that the IOP memory dump is different.
EDIT: I was trying to be helpful by using a custom-named savestate instead of using slot 0, except that I just realized this means the filename doesn't contain the CRC; for reference, it's 82957819 (SLUS-20293).
Can this be tried again? There was more SPU fixes after this was last tested.
Just ran PCSX2 Nightly - v1.7.2731 Compiled on May 9 2022
, and the issue is unchanged.
Just ran
PCSX2 Nightly - v1.7.2731 Compiled on May 9 2022
, and the issue is unchanged.
v1.7.3043 and it's still an issue unfortunately
A long time ago in the 1.4.0 days I remember seeing the solution posted somewhere on the forums and I've been using it ever since to fix this issue - increasing EE Cyclerate to 130%. Just tested it again on 1.7.3220 and yeah, it still works. Granted it's probably just a workaround and not addressing the root cause, but it works. It unfortunately doesn't fix any of the Starfighter games' other serious issues though.
Just tried this in v1.7.4280 and, for the first time in PCSX2, heard dialogue in an end-of-mission cutscene. It would seem that, at some point in the past few months, this issue got fixed.
I think it did work sometimes, can you repeat completing the mission?
No, this issue wasn't one that only occurred at random; you may be thinking of #1927 (which is unfortunately still present).
oh, maybe you're right, sorry!
Apparently I stand corrected about it happening at random, because when I went back to do a binary search to find which build fixed the issue, it didn't work even on the "known-good" build. I can confirm the 130% EE overclock seems to work reliably, though.
Can this be retested?
Re-tested on latest nightly, no longer an issue.
PCSX2 version:
pcsx2-v1.5.0-dev-2055-g29eed18-windows-x86
PCSX2 options: As far as I can tell, no options affect the issue.
Plugins used:
SPU2-X 20170430234119 2.0.0 [Spu2-X]
The timeout issue occurs even in "No Sound" mode.Description of the issue: Most missions (not training missions, bonus missions, or ones that end in an FMV) have an in-engine cutscene after completion, which contains some dialogue; for some reason, the audio for these cutscenes are glitched and no voices or sound effects play (although, for some reason, you can still hear the sounds of ships' engines... possibly because they're looping sounds?), and the game will seemingly freeze for 15 seconds before the cutscene plays, with PCSX2 logging some errors in the process.
Here is what the log window shows at the end of the first mission: https://pastebin.com/DuAHJJWK
(The
padman: *** VBLANK OVERLAP ***
line doesn't appear to be unique to this situation, but it does get repeatedly logged during the 15 second wait, hence why I included it.)How to reproduce the issue:
Last known version to work: Problem occurs at least as far back as 1.2.1, which is the oldest version I currently have downloaded.
PC specifications: CPU:
AMD 9590-FX
(underclocked to ~4.2 GHz/core, if that matters) GPU:R9 290
OS:Windows 10 64-bit