Pangya Fantasy Golf (ULUS10438):- Non-responsive (or crashes) when pressing the X button at the Success screen after completing a License event since 0.9.6-724-gecdffab

[solarmystic]

(Possibly related to #6057)

Issue is as stated in the title. First responsible commit found via bisecting is ecdffab by @unknownbrackets

Last unaffected commit is 0.9.6-723-g4cec228 4cec228 by @unknownbrackets

Savedata for issue reproduction:-

(rename jpg to 7z and unzip using 7zip)

Issue reproduction:-

a. Start the game using any build from 0.9.6-724-gecdffab onwards with default settings.

b. Load the provided savefile.

c. Head to Pangya Tour Mode, then License, followed by Blue Lagoon and finally Chip-in.

d. Playthrough the short challenge, and when the Results (Success) screen comes up, try pressing the X button.

e. One of two things will happen; you'll either hear the confirmation sound but the game will refuse to proceed onwards (spamming the X button will just produce the ding sound repeatedly but nothing else will happen), or the game (and PPSSPP) will just crash.

A proper debug logfile of the issue could not be obtained; the game/ppsspp would hang with a black screen when attempting to load a save file in order to reproduce the issue when Debug Logging to a file is active, which is probably another issue in itself.

Here's what I managed to get until then:-

(rename jpg to 7z and unzip using 7zip)

The stacktrace obtained from the instances when the game/ppsspp crashed was also rather useless and only pointed to the disassembly.

Caveat:-

1. Happens even when Fast Memory is disabled.

Thanks to Nightquaker and the others in the ppsspp.org forums for the initial discovery of the issue.

[solarmystic]

For those who're interested in issue reproduction but are unable to self-compile PPSSPP, here are some of those older 64bit unmodified Windows builds that I self-compiled for testing/reproductive purposes since the buildbot doesn't carry 0.9.6 git versions anymore.

0.9.6-723-g4cec228 (last working revision) https://www.mediafire.com/?me13xa8tm5y5j3o

0.9.6-724-gecdffab (first faulty revision) https://www.mediafire.com/?l1colcnx8apdj1z

[unknownbrackets]

I don't think builds will help fix this bug, and unfortunately although you've posted a lot of information I doubt this will be fixed any time soon because it lacks sufficient actionable information that can lead to a fix.

Probably the only way to fix this is for someone who has the game or wishes to purchase it to debug it, and create a test based on the behavior that's causing the problem. The "faulty" version fixed other games (NOVA, I think?) as far as I know, and fixed tests. Clearly the previous behavior is incorrect and inarguably faulty.

There are already pretty thorough tests for VPLs including specifically for that change, and the only one not passing is due to differences in the available memory when psplink is running (a bug in our testing system, but not in ppsspp.)

-[Unknown]

[rogerrr]

I have the same problem in PPSSPP for android.

[Saramagrean]

Temporary fix, After start game goto "Options" before play the other mode, Game is not crash or stuck when press "X" (Work on both Android/Windows)

Test clip use PPSSPP v1.6.3 latest build. 😉
https://youtu.be/91-tkHgGKMU

[unknownbrackets]

Has this improved? Some other Pangya issues have been resolved recently.

-[Unknown]

[Saramagrean]

This problem still exist.

[Saramagrean]

Logcat. (v1.9.3-500-ge14bf3bcc)
https://drive.google.com/open?id=1bmBeODmvLNWdzEgJBsXKDU1a896Fp5TN

[Saramagrean]

Can confirm it fixed by #12718 👍

[hrydgard]

Thanks for reporting!