1,913
edits
Game crash: Difference between revisions
m
A RAM editor, a file replacement tool along several custom file creators, a backup launcher, firmware spoofing, rudimentary homebrew, and potentially a boottime IOSU exploit. Yeah at this point there is no "lack of developed hacks for the Wii U".
EndGenuity (talk | contribs) m (A RAM editor, a file replacement tool along several custom file creators, a backup launcher, firmware spoofing, rudimentary homebrew, and potentially a boottime IOSU exploit. Yeah at this point there is no "lack of developed hacks for the Wii U".) |
|||
| Line 6: | Line 6: | ||
==In the ''{{B|Super Smash Bros.|series}}'' series== | ==In the ''{{B|Super Smash Bros.|series}}'' series== | ||
As with any other game, crashes can occur in the ''Super Smash Bros.'' games. It | As with any other game, crashes can occur in the ''Super Smash Bros.'' games. It is very rare for crashes to occur from normal ingame play, though [[glitch]]es and [[hack]]s can cause them. | ||
===In ''[[Super Smash Bros.]]''=== | ===In ''[[Super Smash Bros.]]''=== | ||
| Line 14: | Line 14: | ||
Unlike the Nintendo 64, the [[Nintendo GameCube]] was a disc-based system that was notoriously durable and could effectively keep inserted games in place. As such, freezes in ''Melee'' from a connection disruption were rare. When crashes do occur in ''Melee'', the game will completely freeze and cease all response to any input, though any ingame music playing when the crash occurred could keep on playing. | Unlike the Nintendo 64, the [[Nintendo GameCube]] was a disc-based system that was notoriously durable and could effectively keep inserted games in place. As such, freezes in ''Melee'' from a connection disruption were rare. When crashes do occur in ''Melee'', the game will completely freeze and cease all response to any input, though any ingame music playing when the crash occurred could keep on playing. | ||
While ''Melee'' can occasionally lag the GameCube in certain circumstances, it is never CPU-intensive enough in normal play to crash the system. However, "black holes" created from the [[black hole glitch]] can strain the system to an exorbitant amount, heavily lagging the game when they | While ''Melee'' can occasionally lag the GameCube in certain circumstances, it is never CPU-intensive enough in normal play to crash the system. However, "black holes" created from the [[black hole glitch]] can strain the system to an exorbitant amount, heavily lagging the game when they are in play. If players create more than one black hole, or create a more intensive black hole (such as putting more [[Turnip]]s in it or using multiple [[PK Fire]]s on it), they heavily risk crashing the game, and will inevitably do so if they keep on making more black holes or keep putting more stuff into one. | ||
A couple of other glitches can also cause ''Melee'' to crash. Playing as {{SSBM|Master Hand}} through the [[Name Entry glitch]] is notorious for causing crashes through many scenarios, as since he was not supposed to be playable, he lacks many of the assets other playable characters require (such as a [[victory pose]], which results in the game invariably crashing if Master Hand wins a [[Vs. match]]). Potentially due to how {{SSBM|Zelda}} technically takes up two character slots (one with her, the other with {{SSBM|Sheik}} ready to be switched to), Master Hand will also crash the game if used in any Vs. match involving her. Another lesser-known glitch capable of crashing the game is the [[Shadow glitch]]; the Shadow glitch allowed players to catch the mini-[[Shadow Ball]]s thrown during {{SSBM|Mewtwo}}'s [[forward throw]] as if they were an [[item]], and if a player who caught one threw it without it being immediately caught by another player, it would crash the game. However, since the glitch was discovered early on, it only exists in [[Version 1.0]] of ''Melee'', as it was fixed in subsequent versions. | A couple of other glitches can also cause ''Melee'' to crash. Playing as {{SSBM|Master Hand}} through the [[Name Entry glitch]] is notorious for causing crashes through many scenarios, as since he was not supposed to be playable, he lacks many of the assets other playable characters require (such as a [[victory pose]], which results in the game invariably crashing if Master Hand wins a [[Vs. match]]). Potentially due to how {{SSBM|Zelda}} technically takes up two character slots (one with her, the other with {{SSBM|Sheik}} ready to be switched to), Master Hand will also crash the game if used in any Vs. match involving her. Another lesser-known glitch capable of crashing the game is the [[Shadow glitch]]; the Shadow glitch allowed players to catch the mini-[[Shadow Ball]]s thrown during {{SSBM|Mewtwo}}'s [[forward throw]] as if they were an [[item]], and if a player who caught one threw it without it being immediately caught by another player, it would crash the game. However, since the glitch was discovered early on, it only exists in [[Version 1.0]] of ''Melee'', as it was fixed in subsequent versions. | ||
| Line 27: | Line 27: | ||
Like in ''Melee'', a few glitches are capable of causing crashes. The most notorious such glitch in ''Brawl'' is the grab-break glitch with {{SSBB|Yoshi}}, where if a player grabbed by Yoshi manages to break out of the grab before going into Yoshi's mouth, as soon as the player breaks out of the grab, the game will instantly crash (likely due to Yoshi still trying to access "the grabbed opponent", or the programming not knowing what to do if his grab is broken at that time). The glitch's infamy is from the fact that unlike other game-crashing glitches, it can occur in any match involving Yoshi without any outside elements, and through normal play instead of through a complicated and unnatural procedure that wouldn't be done by a player not trying to intentionally cause the glitch; thus it has the potential to crash the game in the middle of a [[tournament]] match without intentional invoking, resulting in either disrupting an ongoing match or forcing one of the players to be disqualified to no fault of their own (and in the potential ban of Yoshi from competitive play). However, since the time between Yoshi's grab connecting and going into Yoshi's mouth is so small, it can only occur at extremely low damages and only with exorbitant [[mash]]ing skills, thus it doesn't actually occur in normal play and is a virtual nonfactor in tournaments. Another glitch capable of causing a crash is the [[Chain Jacket glitch]]; the game will invariably crash if {{SSBB|Sheik}} performs the glitch without having used a prior move. While this can occur in any match involving Sheik, a Sheik player would have to be intentionally invoking it to crash the game through it, thus the only tournament consequence of it would be the forced forfeit of the Sheik player causing it. | Like in ''Melee'', a few glitches are capable of causing crashes. The most notorious such glitch in ''Brawl'' is the grab-break glitch with {{SSBB|Yoshi}}, where if a player grabbed by Yoshi manages to break out of the grab before going into Yoshi's mouth, as soon as the player breaks out of the grab, the game will instantly crash (likely due to Yoshi still trying to access "the grabbed opponent", or the programming not knowing what to do if his grab is broken at that time). The glitch's infamy is from the fact that unlike other game-crashing glitches, it can occur in any match involving Yoshi without any outside elements, and through normal play instead of through a complicated and unnatural procedure that wouldn't be done by a player not trying to intentionally cause the glitch; thus it has the potential to crash the game in the middle of a [[tournament]] match without intentional invoking, resulting in either disrupting an ongoing match or forcing one of the players to be disqualified to no fault of their own (and in the potential ban of Yoshi from competitive play). However, since the time between Yoshi's grab connecting and going into Yoshi's mouth is so small, it can only occur at extremely low damages and only with exorbitant [[mash]]ing skills, thus it doesn't actually occur in normal play and is a virtual nonfactor in tournaments. Another glitch capable of causing a crash is the [[Chain Jacket glitch]]; the game will invariably crash if {{SSBB|Sheik}} performs the glitch without having used a prior move. While this can occur in any match involving Sheik, a Sheik player would have to be intentionally invoking it to crash the game through it, thus the only tournament consequence of it would be the forced forfeit of the Sheik player causing it. | ||
Another means of causing crashes in ''Brawl'' is the disc itself being damaged. Several players with damaged discs have been permanently unable to access certain characters and stages as the Wii could no longer read them off of the disc; this results in any matches on the disc involving the afflicted characters or stages instantly crashing the game (or even crashing the game if the afflicted characters and stages are even hovered over on the select screens). A damaged disc could only have one specific character unable to be read anymore, or up to a significant portion of ''Brawl''{{'}}s cast and stages being completely inaccessible. When this occurs, the afflicted player has to get a new ''Brawl'' disc, have the disc repaired, or use the file replacement hack to simply load the default files through the SD card instead, though proper handling of the disc will prevent it from happening in the first place. Playing the game from its image file (such as with WODE Jukebox) prevents many of these problems, as it | Another means of causing crashes in ''Brawl'' is the disc itself being damaged. Several players with damaged discs have been permanently unable to access certain characters and stages as the Wii could no longer read them off of the disc; this results in any matches on the disc involving the afflicted characters or stages instantly crashing the game (or even crashing the game if the afflicted characters and stages are even hovered over on the select screens). A damaged disc could only have one specific character unable to be read anymore, or up to a significant portion of ''Brawl''{{'}}s cast and stages being completely inaccessible. When this occurs, the afflicted player has to get a new ''Brawl'' disc, have the disc repaired, or use the file replacement hack to simply load the default files through the SD card instead, though proper handling of the disc will prevent it from happening in the first place. Playing the game from its image file (such as with WODE Jukebox) prevents many of these problems, as it does not read from a physical disc. | ||
===In ''[[Super Smash Bros. 4]]''=== | ===In ''[[Super Smash Bros. 4]]''=== | ||
| Line 34: | Line 34: | ||
{{For3ds}}, similar to ''Smash 64'', can crash if the connection between the game card and the Nintendo 3DS is disrupted, as well as if the connection between the 3DS and its [[SD card]] is disrupted; compared to the Nintendo 64, however, these connections are more resilient, and under most circumstances, the 3DS will reboot into its Home Menu if this connection is lost. For digital copies of the game, crashes can occur if the data saved onto the 3DS's SD card is corrupted; in this case, an online service offered by Nintendo allows the player to verify the integrity of the game's data and redownload the appropriate files to replace corrupted data. The 3DS version has also been reported to [http://smashboards.com/threads/has-anyone-had-the-3ds-crash-during-smash-run.377247 occasionally crash] in [[Smash Run]]; some 3DS consoles also [http://smashboards.com/threads/updated-daily-partial-fix-an-error-has-occurred-forcing-the-software-to-close.370907 have problems] running the game, with the fix focusing on [http://www.reddit.com/r/smashbros/comments/2kvamu/update_on_ssb4_crashing_physical_copy_not_digital replacing the console itself]. | {{For3ds}}, similar to ''Smash 64'', can crash if the connection between the game card and the Nintendo 3DS is disrupted, as well as if the connection between the 3DS and its [[SD card]] is disrupted; compared to the Nintendo 64, however, these connections are more resilient, and under most circumstances, the 3DS will reboot into its Home Menu if this connection is lost. For digital copies of the game, crashes can occur if the data saved onto the 3DS's SD card is corrupted; in this case, an online service offered by Nintendo allows the player to verify the integrity of the game's data and redownload the appropriate files to replace corrupted data. The 3DS version has also been reported to [http://smashboards.com/threads/has-anyone-had-the-3ds-crash-during-smash-run.377247 occasionally crash] in [[Smash Run]]; some 3DS consoles also [http://smashboards.com/threads/updated-daily-partial-fix-an-error-has-occurred-forcing-the-software-to-close.370907 have problems] running the game, with the fix focusing on [http://www.reddit.com/r/smashbros/comments/2kvamu/update_on_ssb4_crashing_physical_copy_not_digital replacing the console itself]. | ||
{{Forwiiu}}, similar to ''Brawl'', can crash if the disc becomes scratched, with the Wii U's lens being unable to read data critical for the game; no known circumvention method for this is available, due to the lack of | {{Forwiiu}}, similar to ''Brawl'', can crash if the disc becomes scratched, with the Wii U's lens being unable to read data critical for the game; no known circumvention method for this is available, due to the current lack of accessible hacks for the Wii U. Like ''Brawl'', game crashes can be detected by the console. If this happens, a loud buzzing sound is emitted for around 5 seconds. Afterwards, the player will have to turn off the Wii U. | ||
[[Category:Glitches (SSB)]] | [[Category:Glitches (SSB)]] | ||