-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
related (though different region, and issue is not necessarily game-specific): #11586
I want to clarify that while the problem is rare, the emulator behaviour (which is what I want to concentrate the issue on) is still very weird (as confirmed by @hrydgard himself)
ROM
Jackass the Game (Europe).iso
Size: 1,812,494,336 bytes
CRC32: FB133420
MD5: 3A714CB9A2BCF79DB7203273DC5EECC0
SHA1: d03293698b7b112d7c6e010190f97043e32912b0
SHA384: 9c09d296db959ca53b75e8dc70a3155685d7e6514a1bbff1130d27d886a60877a6aeeb49f652dfaf58df0302d3775303
PPSSPP
PPSSPP 1.7.4; settings changed
Seemingly the most stable version for this game:
-
(changed controls, shouldn't affect anything)
-
Rendering backend:
Direct3D 9: colour glitches, texture glitches, image upside down. Unplayable
Direct3D 11: no buffered parts rendered. Unplayable
OpenGL: best rendering backend in avail
Vulnano: (unable to test out) -
Rendering mode (required): Buffered rendering (unbuffered fails on minigames)
PPSSPP 1.8.0;
- The first time tried, for whatever reason the framerate wasn't capped. Not sure why.
- Tried running again, the problem disappeared; not sure why
- Changed the same settings as for 1.7.4 -> seemingly the same in-game behaviour
Now to the game itself.
-
The set-up I test, if I go to Minigames -> Golf Rally. Play it for 10 seconds (whether doing the moves or not), and notice the game's in-game timer looping incorrectly breaking the gameplay. All the music, gameplay, and moves begin looping incorrectly
-
Another side effect is, if you now "exit stunt", the game crashes entirely. If you try exiting before the timers break, you should be able to do so.
"Weird workaround"
As I described,
if you PAUSE the emulation and then resume it, the game kinda rolls out its wheels and stops glitching (including that it allows to exit minigames). How is it even possible?
Turns out I slightly misremembered it. What you really need to do, is go to is,
- Get the game to the specific "bypassable" state (explained below)
- Save state
- Load state
- If did not work out
- Possibly wait ~5 seconds keeping the game running
- Go to 2
Bypassable state
Bypassable state is the state in which the workaround may work out. Found bypassable and non-Bypassable states are:
Non-bypassable
- Pause menu
Bypassable
- "Action", i.e. while the stunt running
- "Injury report" - i.e. score obtained
- "Video footage obtained", i.e. achievements
- End stunt menu
TL:DR
it seems there is a pattern, which is that,
- Music plays -> Bypassable
- Music does not play -> Non-bypassable
Strategy
-
Best strategy is,
- Begin stunt, wait until the timers break
- Fail it
- In the after-stunt menu, perform the workaround
-
The second-best strategy, is not as stable, but useful where early stunt exiting is impossible is
- Begin stunt, wait until the timers break
- (Recommended) set the emulation speed to, say, 20%
- While the stunt running, perform workaround
real time clock sync
aka Game Settings -> More settings -> System -> Emulation -> Force real clock sync (slower, less lag)
make sure you're not using "real time clock sync"
While testing, the parameter is Disabled (unchecked).
Try with it on (just to test out):
Tick, then reset: Nothing changes
Unsolved issues
- Party boy is still unplayable.
Reason is simple: The music, and timers accordingly, reset entirely upon stunt restarting
Workaround:- Begin stunt, wait until the timers break
- With a RAM hacking software, set the score to >750 to pass it
- While the stunt running, Wait another 10 seconds, perform workaround
- If failed, goto 3
- After finishing stunt, save game and forget about stunt thereafter
(Possibly) other stunts of the similar nature may make use of this workaround as well if need be