Out of Bounds - Revision history

UNHchabo: /* Origin Effects */ shown in the 3% tutorial

2022-01-20T22:28:54Z

‎Origin Effects: shown in the 3% tutorial

UNHchabo: /* Mapping Out of Bounds */ sd2snes gets initialized to a fixed value, and consoles vary due to differences between each cell in DRAM

2021-11-06T18:15:23Z

‎Mapping Out of Bounds: sd2snes gets initialized to a fixed value, and consoles vary due to differences between each cell in DRAM

UNHchabo: /* Mapping Out of Bounds */ Video comparison for higan patterns

2020-03-02T01:14:56Z

‎Mapping Out of Bounds: Video comparison for higan patterns

UNHchabo: /* Mapping Out of Bounds */ higan/bsnes ram data

2020-03-01T00:48:08Z

‎Mapping Out of Bounds: higan/bsnes ram data

UNHchabo: /* Practical Guide */ Link to article on DRAM remanence

2020-02-19T09:43:01Z

‎Practical Guide: Link to article on DRAM remanence

UNHchabo: Explanation and video for randomized start data

2020-02-16T23:07:39Z

Explanation and video for randomized start data

UNHchabo: Linking to categories that use OOB

2019-12-31T02:00:32Z

Linking to categories that use OOB

UNHchabo: Effects at x=0 -- summary of a conversation with sniq

2019-11-20T15:34:05Z

Effects at x=0 -- summary of a conversation with sniq

UNHchabo: Added practical guide for OOB navigation

2019-09-22T08:03:58Z

Added practical guide for OOB navigation

UNHchabo: Turn external link syntax into internal link syntax

2019-09-15T08:05:54Z

Turn external link syntax into internal link syntax

@@ Line 16: / Line 16: @@
 When Samus' X position is close to 0, she will have strange properties with the blocks she's touching. This is because of the collision oscillator, and the fact that she's touching blocks at both positive and negative coordinates. Every second frame will have a solid collision, and every other frame will have a non-solid collision.
-Sometimes a door transition can even be encountered here without a door block; this will be one of the non-solid collisions, and the current best guess is that this is due to the room's repeating geometry, so this collision happens against a block that's at the far right side of the room.
+Sometimes a door transition can even be encountered here without a door block, as seen in the [[3%]] tutorial; this will be one of the non-solid collisions, and the current best guess is that this is due to the room's repeating geometry, so this collision happens against a block that's at the far right side of the room.
 == Practical Guide ==

@@ Line 34: / Line 34: @@
 To figure out a particular out of bounds route, you will typically want to use a Hitbox Viewer, and figure out a combination of visual cues, audio cues, rhythmic cues such as a metronome or the [[Power Beam]] auto-fire, and [[Normalized Movement]], to navigate where you need to go.
-Normally lsnes and Snes9x use fixed data to initialize ram at startup, but a real console might have some data left over from a previous boot, [https://en.wikipedia.org/wiki/Dynamic_random-access_memory#Security due to the nature of DRAM]. If we instead set lsnes to randomize the ram data on startup, that gives us a bit more of a worst case scenario, showing the areas of Out of Bounds that might contain unexpected garbage blocks during actual runs.
+Normally lsnes and Snes9x use fixed data to initialize ram at startup ([https://github.com/MiSTer-devel/SNES_MiSTer/issues/184 as does sd2snes]), but a real console+cartridge might have some data left over from a previous boot, [https://en.wikipedia.org/wiki/Dynamic_random-access_memory#Security due to the nature of DRAM]. It will also contain different values between individual examples of consoles, since each DRAM cell will have a specific value that it will trend towards when it's powered off.
 {{#ev:youtube|_n0oRdQUpzo}}

← Older revision		Revision as of 01:14, 2 March 2020
Line 39:		Line 39:

	higan and bsnes have a different RAM initialization method that partially randomizes the data in a way that's designed to more closely resemble actual console behavior. There's no hitbox viewer available for these emulators, but you can either port the initialization method into lsnes, or you can use Cheat Engine to paste the higan tilemap RAM data into lsnes' memory.		higan and bsnes have a different RAM initialization method that partially randomizes the data in a way that's designed to more closely resemble actual console behavior. There's no hitbox viewer available for these emulators, but you can either port the initialization method into lsnes, or you can use Cheat Engine to paste the higan tilemap RAM data into lsnes' memory.
		+
		+	For instance, this video shows a comparison of the last OOB navigation in 0%, using the lsnes initialization pattern, as well as four patterns taken from higan:
		+
		+	{{#ev:youtube\|zvThbcMloDY}}

← Older revision		Revision as of 00:48, 1 March 2020
Line 37:		Line 37:

	{{#ev:youtube\|_n0oRdQUpzo}}		{{#ev:youtube\|_n0oRdQUpzo}}
		+
		+	higan and bsnes have a different RAM initialization method that partially randomizes the data in a way that's designed to more closely resemble actual console behavior. There's no hitbox viewer available for these emulators, but you can either port the initialization method into lsnes, or you can use Cheat Engine to paste the higan tilemap RAM data into lsnes' memory.

@@ Line 27: / Line 27: @@
 Slope blocks have strange properties out of bounds, and may cause Samus to fall partially through them to the block below, or to "bounce" on them.
 Use of the X-Ray Scope once you're far enough away from the original room can change memory values, and can change the room geometry.
@@ Line 34: / Line 32: @@
 === Mapping Out of Bounds ===
-Normally lsnes and Snes9x use fixed data to initialize ram at startup, but a real console generally has different patterns that might be in the ram at startup. If we instead set lsnes to randomize the ram data on startup, that gives us a bit more of a worst case scenario, showing the areas of Out of Bounds that might contain garbage blocks during actual runs.
+To figure out a particular out of bounds route, you will typically want to use a Hitbox Viewer, and figure out a combination of visual cues, audio cues, rhythmic cues such as a metronome or the [[Power Beam]] auto-fire, and [[Normalized Movement]], to navigate where you need to go.
 {{#ev:youtube|_n0oRdQUpzo}}

← Older revision		Revision as of 23:07, 16 February 2020
Line 31:		Line 31:

	Use of the X-Ray Scope once you're far enough away from the original room can change memory values, and can change the room geometry.		Use of the X-Ray Scope once you're far enough away from the original room can change memory values, and can change the room geometry.
		+
		+	=== Mapping Out of Bounds ===
		+
		+	Normally lsnes and Snes9x use fixed data to initialize ram at startup, but a real console generally has different patterns that might be in the ram at startup. If we instead set lsnes to randomize the ram data on startup, that gives us a bit more of a worst case scenario, showing the areas of Out of Bounds that might contain garbage blocks during actual runs.
		+
		+	{{#ev:youtube\|_n0oRdQUpzo}}

← Older revision		Revision as of 02:00, 31 December 2019
Line 19:		Line 19:

	== Practical Guide ==		== Practical Guide ==
		+
		+	While most categories ban the use of OoB, there are categories that allow it, and take advantage of OoB movement, such as [[Any% Glitched]], [[Any% GT Code]], and Low% Glitched categories ([[0%]], [[4%]], and [[12%]]).

	The layout of the Out of Bounds area can be typically normalized by resetting, or by entering a larger room than the one you plan on going Out of Bounds in.		The layout of the Out of Bounds area can be typically normalized by resetting, or by entering a larger room than the one you plan on going Out of Bounds in.

← Older revision		Revision as of 15:34, 20 November 2019
Line 11:		Line 11:

	For more information also see this post http://tasvideos.org/forum/viewtopic.php?p=433442&highlight=#433442 and the bottom part of this post: http://tasvideos.org/forum/viewtopic.php?p=418314&highlight=#418314		For more information also see this post http://tasvideos.org/forum/viewtopic.php?p=433442&highlight=#433442 and the bottom part of this post: http://tasvideos.org/forum/viewtopic.php?p=418314&highlight=#418314
		+
		+	== Origin Effects ==
		+
		+	When Samus' X position is close to 0, she will have strange properties with the blocks she's touching. This is because of the collision oscillator, and the fact that she's touching blocks at both positive and negative coordinates. Every second frame will have a solid collision, and every other frame will have a non-solid collision.
		+
		+	Sometimes a door transition can even be encountered here without a door block; this will be one of the non-solid collisions, and the current best guess is that this is due to the room's repeating geometry, so this collision happens against a block that's at the far right side of the room.

	== Practical Guide ==		== Practical Guide ==

← Older revision		Revision as of 08:03, 22 September 2019
Line 11:		Line 11:

	For more information also see this post http://tasvideos.org/forum/viewtopic.php?p=433442&highlight=#433442 and the bottom part of this post: http://tasvideos.org/forum/viewtopic.php?p=418314&highlight=#418314		For more information also see this post http://tasvideos.org/forum/viewtopic.php?p=433442&highlight=#433442 and the bottom part of this post: http://tasvideos.org/forum/viewtopic.php?p=418314&highlight=#418314
		+
		+	== Practical Guide ==
		+
		+	The layout of the Out of Bounds area can be typically normalized by resetting, or by entering a larger room than the one you plan on going Out of Bounds in.
		+
		+	There are various types of blocks that Samus will interact with while she's moving out of bounds, including door transition blocks, spike blocks, blocks that will crash the game, and slope blocks. Less commonly, there are blocks that allow for other functions like memory corruption.
		+
		+	Slope blocks have strange properties out of bounds, and may cause Samus to fall partially through them to the block below, or to "bounce" on them.
		+
		+	To figure out a particular out of bounds route, you will typically want to use a Hitbox Viewer, and figure out a combination of visual cues, audio cues, rhythmic cues such as a metronome or the [[Power Beam]] auto-fire, and [[Normalized Movement]], to navigate where you need to go.
		+
		+	Use of the X-Ray Scope once you're far enough away from the original room can change memory values, and can change the room geometry.

@@ Line 2: / Line 2: @@
 Out of Bounds (abbreviated OoB) is a rule applied to Super Metroid categories, typically preventing the use of Out of Bounds (e.g. no OoB) in a run.
-Out of Bounds is defined as whenever Samus' hitbox leaves the regular boundaries of the room (via [[X-Ray Climb]], [[Doorskip]], or any other glitch) and causes the map to shift into a black area that is not marked in the game and is not tracked.  The map on the HUD consequently stops blinking when this occurs (which it does not when Samus is located at black inbounds map square tiles such as the easiest to reach black map square tile in the Green Brinstar Fireflea room [https://wiki.supermetroid.run/Green_Brinstar_Fireflea_Room]). In Out of Bounds Samus completely leaves the existing room and is able to exploit junk data left behind from previous rooms.
+Out of Bounds is defined as whenever Samus' hitbox leaves the regular boundaries of the room (via [[X-Ray Climb]], [[Doorskip]], or any other glitch) and causes the map to shift into a black area that is not marked in the game and is not tracked.  The map on the HUD consequently stops blinking when this occurs (which it does not when Samus is located at black inbounds map square tiles such as the easiest to reach black map square tile in the [[Green Brinstar Fireflea Room]]). In Out of Bounds Samus completely leaves the existing room and is able to exploit junk data left behind from previous rooms.
 This does not cover clipping through walls and platforms, as well as an X-Ray Climb that goes through the wall but doesn't leave the room (such as leaving Draygon without Gravity).