the cutting room mirror

SpongeBob SquarePants: Revenge of the Flying Dutchman (GameCube, PlayStation 2)

This article has a talk page!
view on tcrf.net

This page details bugs of SpongeBob SquarePants: Revenge of the Flying Dutchman (GameCube, PlayStation 2).

Both Versions#

Loud Intro Videos#

This game is notorious for the loudness of its intro videos (among other things). This is, at least in part, due to a bug: the game does lower the volume to ~82% for the videos, but it lowers the SFX volume instead of the music volume. As the volume of videos is determined by the music volume, this effectively does nothing, and so the videos play at the default 100% volume, your ears be damned.

The following Action Replay code fixes this bug:

Version

Code

GCN (USA)

0428C934 818C0038

GameCube-Only#

First Letter Tile Cutscene Crash#

Watch on YouTube

If you are in first-person view when the first letter tile cutscene is triggered, the game will softlock and all in-game elements will stop drawing. Other than resetting, your only options at this point are to pause and exit, load a save, or use the hidden level select to reload the game.

The game is pretty erratic in this state: if you instead begin pressing random buttons, the game will soon crash, forcing you to reset the console.

PlayStation 2-Only#

To do:
There appears to be a glitch where certain voice clips of cutscenes occasionally refuse to play making some out of all dialogue impossible to hear in one playthrough. Like the loading glitch below, it may depend on certain disc drive models (probably make sure that your PlayStation Disc Spin is set to "FAST" to mostly avoid this bug?) or BIOS's.

Loading Glitch#

Watch on YouTube

The game has a chance to freeze when entering an area and kick the player to the browser screen, resulting in any unsaved progress being lost, although contrary to popular belief this will not corrupt any save files. This is due to the game soft resetting the console when loading, done to bypass a Sony policy about loading times but which has trouble working on newer PS2 models. This glitch does not happen in emulators.