Metal Gear Solid: Peace Walker

[TheDax]

PW 2 isn't killable, even with infinite ammo. It's one of the longest running unresolved bugs in PPSSPP. Anyway, yes, there's a code somewhere in this thread. Try searching for mech kill or something like that.

[AlphaKennyTime]

Thanks for helping me finally get past that boss, TheDax. I almost turned back to my old psp to try to get past it. Post 99 has the cheat.

[dsnoir]

I got stuck at that boss battle and got really frustrated, but finally felt relieved again thanks to that cheat.

However I got crashed at the loading screen after killing Peace Walker in the next mission, anyone got the same thing as me?

[AlphaKennyTime]

Only use that cheat for that one mission. Turn it off after you're past that part or you'll run into problems. I turned it on for some other AI fight in spec ops to see if it worked with any mech and I took down that flying AI but as soon as I entered the pod my game froze at a black screen. Looks like the cheat only works in the PW2 fight.

[dsnoir]

(08-19-2014 08:40 PM)AlphaKennyTime Wrote:  Only use that cheat for that one mission. Turn it off after you're past that part or you'll run into problems. I turned it on for some other AI fight in spec ops to see if it worked with any mech and I took down that flying AI but as soon as I entered the pod my game froze at a black screen. Looks like the cheat only works in the PW2 fight.

Nice, luckily I didn't overwrite my save. Thanks!

[Nightquaker]

I'm using version 0.9.9-84 64bit and the loading problem I mentioned is freakin' infuriating. Almost on every loading screen, game freezes for about 10 seconds. Issue is quite common, but appears randomly in different builds. Some builds have it, some not. It's really annoying. Also, Peace Walker battle 2 bug is still there.

[Zinx777]

Gonna be fixed soon...
https://github.com/hrydgard/ppsspp/pull/6762

[Nightquaker]

(08-22-2014 08:57 AM)Zinx777 Wrote:  Gonna be fixed soon...
https://github.com/hrydgard/ppsspp/pull/6762

WOAH! Great news! :3

Though, I noticed that on a screenshot with fixed Peace Walker, emulator is revision 59 and on revision 65 that came out already, fix is not implemented. Though, the emulator on screenshot is running a japanese version of the game.

[LunaMoo]

@Nightquaker that's because to test new changes, people apply commits to their local repos which doesn't really have to be updated, the fix was merged today with v0.9.9.1-72-gb7da82e, so this and any version above should have it.

[Agent13]

Wow! PW battle battle 2 is beatable in v0.9.9.1-72 version! I finish this mission finally without cheats!
Thanks for the great fix!

[draas]

are the panels in some cutscenes still missing?

[[Unknown]]

(08-23-2014 10:15 AM)LunaMoo Wrote:  @Nightquaker that's because to test new changes, people apply commits to their local repos which doesn't really have to be updated, the fix was merged today with v0.9.9.1-72-gb7da82e, so this and any version above should have it.

Well, and also because git is not linear.

Suppose the following happens:

Alan grabs the latest git build (v0.9.9.1-92-gd4ec7d8)
Bob grabs the latest git build (v0.9.9.1-92-gd4ec7d8)
Charlie grabs the latest git build (v0.9.9.1-92-gd4ec7d8)

Alan adds a commit to his version which fixes all bloom issues.
Bob adds a commit to his version which fixes all network issues.
Charlie adds a commit to his version that makes PPSSPP delete all your data off your hard drive on startup.

Each of their versions will be v0.9.9.1-93. If you say "network fixed, WOW, use v0.9.9.1-93", then people might grab Charlie's build and have a bad day.

However, they will each have a different commit hash. v0.9.9.1-93-g123456. That last part says *which* 93rd commit since v0.9.9.1 it is.

When they get merged into master, they will remain named -93 each (even on the buildbot download page) since they are all 93 commits away from v0.9.9.1. But the merge commits will be higher numbers.

Git is not linear. Multiple people can work simultaneously.

-[Unknown]

[Nightquaker]

(08-23-2014 02:59 PM)[Unknown] Wrote:  

(08-23-2014 10:15 AM)LunaMoo Wrote:  @Nightquaker that's because to test new changes, people apply commits to their local repos which doesn't really have to be updated, the fix was merged today with v0.9.9.1-72-gb7da82e, so this and any version above should have it.

Well, and also because git is not linear.

Suppose the following happens:

Alan grabs the latest git build (v0.9.9.1-92-gd4ec7d8)
Bob grabs the latest git build (v0.9.9.1-92-gd4ec7d8)
Charlie grabs the latest git build (v0.9.9.1-92-gd4ec7d8)

Alan adds a commit to his version which fixes all bloom issues.
Bob adds a commit to his version which fixes all network issues.
Charlie adds a commit to his version that makes PPSSPP delete all your data off your hard drive on startup.

Each of their versions will be v0.9.9.1-93. If you say "network fixed, WOW, use v0.9.9.1-93", then people might grab Charlie's build and have a bad day.

However, they will each have a different commit hash. v0.9.9.1-93-g123456. That last part says *which* 93rd commit since v0.9.9.1 it is.

When they get merged into master, they will remain named -93 each (even on the buildbot download page) since they are all 93 commits away from v0.9.9.1. But the merge commits will be higher numbers.

Git is not linear. Multiple people can work simultaneously.

-[Unknown]

Thank you for the fix, Unknown! Can game be moved to [playable] now? :3

[[Unknown]]

I think so. I don't actually have it, so I can't confirm that it's fully playable, but it ought to be now.

I think there are still other issues, although it'd be good to know if this might've resolved any others.

-[Unknown]

[TheDax]

As far as I know, the only unbeatable mission was that pesky boss battle, so it should be safe to move it to playable.