-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[BUG]: Regression - Guilty Gear XX ACPR - Freeze at the logo #6290
Comments
Can you create a blockdump of the game using v1.7.2837 or older to get past the hang (doesn't have to be too far past), then upload that? Then it can be looked at. Maybe @Goatman13 might be interested in looking at it. |
Of course, here it is : Guilty Gear XX Accent Core Plus (Japan) (2022-05-31 10-21-11).zip |
Thanks |
Game work fine when there is more than 32 bits available here: pcsx2/pcsx2/IPU/mpeg2lib/Mpeg.cpp Line 1226 in 0b2536d
Literally ensuring that buffer have at least 33 bits is enough for stream to play correctly. I didn't fully figured out why, and i can't do much before weekend. Game spams tens of 00 between startcodes, so probably something get lost when there is less than 33 bits available and game start skipping 0 bytes. I don't know how this worked before v1.7.2838. |
oh hmm, you might need to split the function up, if it has to exit out in order to wait for a DMA or something, it's going to get out of sorts of where it needs to return in that loop, so it may need a ipu_cmd.pos[1] setting up for that case. |
This should be fixed with #6313 Looks like it was a DMA/Command timing problem |
Describe the Bug
The game freezes at the Arc System Works logo before the opening starts.
It does that in SW/HW since v1.7.2838
Reproduction Steps
Start the game
Expected Behavior
Opening should starts
PCSX2 Revision
v1.7.2847
Operating System
Windows 11
If Linux - Specify Distro
No response
CPU
Ryzen 5600x
GPU
AMD 6800
GS Settings
No response
Emulation Settings
No response
GS Window Screenshots
Logs & Dumps
snaps.zip
The text was updated successfully, but these errors were encountered: