Crash: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Removing note about the pyramid, crash is easily reproducible in WDW along with HMC) |
||
Line 16: | Line 16: | ||
* Going out of bounds in a room with a painting | * Going out of bounds in a room with a painting | ||
* Being pushed off of a hangable ceiling while in the idle hanging action | * Being pushed off of a hangable ceiling while in the idle hanging action | ||
* Sound glitch | * Sound glitch (J only) | ||
* Moving the camera immediately when entering VCutM | * Moving the camera immediately when entering VCutM |
Revision as of 17:57, 25 March 2019
A Crash, Freeze, or Hardlock is what happens when Super Mario 64's code encounters an error, such as a division-by-zero, that causes the game to stop running and rendering frames. The audio may still play. This is in contrast to a softlock, where the game does still run but is stuck in an indefinite state or a loop where no controller input can change it.
Ways to crash the game
- Exceed the object limit
- Have too many objects at once on the screen
- Send the camera into a PU on N64
- Walking at PU speed for only a portion of the 4 quarter steps on a frame
- Moving at PU speed with no joystick input for all 4 quarter steps on a frame
- Moving at PU speed directly into a wall
- Bully Knockback dividing-by-zero
- Failed Bully/Bob-omb angle double-to-int conversion
- Deleting a non-existent file on the File Select Screen. (Go to "Copy" right when you get to the file select, then press "Score", press on any file without save data, go to Erase, and click on yes.)
- Moving a shadow above surface 12 while it's over OOB
- Killing a Monty Mole remotely
- Killing an uninitialized Monty Mole
- Going out of bounds in a room with a painting
- Being pushed off of a hangable ceiling while in the idle hanging action
- Sound glitch (J only)
- Moving the camera immediately when entering VCutM