FAQ - Revision history

LCDAngel99 at 15:57, 29 March 2026

2026-03-29T15:57:31Z

LCDAngel99: /* Where can I get an SM64 ROM? */

2026-03-29T15:08:40Z

Where can I get an SM64 ROM?

← Older revision		Revision as of 15:08, 29 March 2026
Line 11:		Line 11:
	Most TASes of Super Mario 64 are done on [[Mupen64-rr]]. This is for one main reason: .m64 files can be played back on console, known as [[TASBot#Console Verification\|Console Verification]], whereas bk2 files cannot, due to the way they handle input during lag frames. BizHawk polls inputs on lag frames, as opposed to Mupen64, which does not, and SM64 doesn't either. BK2 files (BizHawk movie files) can still be converted to m64 files, however, so some still use Bizhawk.		Most TASes of Super Mario 64 are done on [[Mupen64-rr]]. This is for one main reason: .m64 files can be played back on console, known as [[TASBot#Console Verification\|Console Verification]], whereas bk2 files cannot, due to the way they handle input during lag frames. BizHawk polls inputs on lag frames, as opposed to Mupen64, which does not, and SM64 doesn't either. BK2 files (BizHawk movie files) can still be converted to m64 files, however, so some still use Bizhawk.
	==Where can I get an SM64 ROM?==		==Where can I get an SM64 ROM?==
	A quick ~~google~~ search can help you with that. Unfortunately we cannot provide links here because of copyright.		A quick Google search can help you with that. Unfortunately we cannot provide links here because of copyright.

	==What different challenges are there?==		==What different challenges are there?==
	As of now, there are 13 challenges that have gained decent popularity, along with many minor ones. Some of the more well-known include:		As of now, there are 13 challenges that have gained decent popularity, along with many minor ones. Some of the more well-known include:

Super Mario Player at 03:23, 22 May 2025

2025-05-22T03:23:32Z

← Older revision		Revision as of 03:23, 22 May 2025
Line 67:		Line 67:
	No. It is a purely visual glitch and has no effect on gameplay.		No. It is a purely visual glitch and has no effect on gameplay.
	==I was doing a BLJ on the endless stairs and warped straight to Wet-Dry World. Is this new?==		==I was doing a BLJ on the endless stairs and warped straight to Wet-Dry World. Is this new?==
	No. You clipped through the ~~wall~~ and went above the painting. The game checks whether or not you entered paintings by checking whether or not you are above floor triangles behind them, even when you are really high up.		No. You clipped through the stairs and went above the painting. The game checks whether or not you entered paintings by checking whether or not you are above floor triangles behind them, even when you are really high up.

	==Mupen==		==Mupen==

Super Mario Player: /* How many A presses are left? */

2025-05-22T03:22:34Z

How many A presses are left?

Aurumaker72: Put mupen-related questions in new category, improve wording, add new info

2024-04-10T13:59:51Z

Put mupen-related questions in new category, improve wording, add new info

← Older revision		Revision as of 13:59, 10 April 2024
Line 60:		Line 60:
	==Why does Mario lose his hat when he dies from going out-of-bounds (OoB)?==		==Why does Mario lose his hat when he dies from going out-of-bounds (OoB)?==
	Mario's default state is, surprisingly, with no hat on, and on each frame it checks whether he's wearing the hat and sets the proper graphics flag. However, when Mario goes OoB, a large portion of the central Mario code stops running, including that check. Hence, Mario doesn't actually lose his hat; he just forgets he's wearing it.		Mario's default state is, surprisingly, with no hat on, and on each frame it checks whether he's wearing the hat and sets the proper graphics flag. However, when Mario goes OoB, a large portion of the central Mario code stops running, including that check. Hence, Mario doesn't actually lose his hat; he just forgets he's wearing it.
	~~==When I record an AVI on mupen, the sound works but the screen is just black. How do I fix this?==~~
	This is a bug that occurs when you use the gl64 video plugin when aero is enabled on your computer. One fix is to use another video plugin, or to disable aero on your computer. The latter is only possible on Windows 7, but unfortunately not on later versions.
	~~==How do you continue off of a TAS you created earlier?==~~
	Play it to where you want to continue, then save a state. Disable read-only mode and reload the state. The file will now start recording inputs from that point, erasing any you had previously made after that point.
	==I just got through the 8 Star Door to Bowser 1 by grabbing onto it with a ledge grab! Is this useful?==		==I just got through the 8 Star Door to Bowser 1 by grabbing onto it with a ledge grab! Is this useful?==
	No. Clipping through the door with a ledge grab is a side effect of the patch in the SM64 Editor program that "improves collision". It is not actually possible in the original game.		No. Clipping through the door with a ledge grab is a side effect of the patch in the SM64 Editor program that "improves collision". It is not actually possible in the original game.
Line 70:		Line 66:
	==I was doing a BLJ on the endless stairs and warped straight to Wet-Dry World. Is this new?==		==I was doing a BLJ on the endless stairs and warped straight to Wet-Dry World. Is this new?==
	No. You clipped through the wall and went above the painting. The game checks whether or not you entered paintings by checking whether or not you are above floor triangles behind them, even when you are really high up.		No. You clipped through the wall and went above the painting. The game checks whether or not you entered paintings by checking whether or not you are above floor triangles behind them, even when you are really high up.
	==Mupen is open, but the Mupen window disappeared and won’t come back, even when I restart. What do I do?==
	This is a glitch that occurs when ~~Mupen~~ is closed while minimized.		== Mupen ==

			=== How do you continue off of a TAS you created earlier? ===

			# Play it to where you want to continue, then save a state.
			# Disable read-only mode and reload the state.
			# The file will now start recording inputs from that point, erasing any you had previously made after that point.

			=== Mupen is open, but the Mupen window disappeared and won’t come back, even when I restart. What do I do? ===
			This is a glitch that occurs on old versions of Mupen when it is closed while minimized.

	To fix it, you must maximize the Mupen window and then drag down the top of the window, which will restore it to a normal window. To maximize the window without it actually being present, you can do one of the following:		To fix it, you must maximize the Mupen window and then drag down the top of the window, which will restore it to a normal window. To maximize the window without it actually being present, you can do one of the following:
Line 78:		Line 83:
	* Hover over the Mupen icon in the task bar, right click on the preview, click maximize		* Hover over the Mupen icon in the task bar, right click on the preview, click maximize
	Deleting Mupen’s config file also works.		Deleting Mupen’s config file also works.
	==Mupen's TAS Input Plugin window doesn't stay focused when clicking on the main emulator window. What do I do?==
	This is a bug that was introduced in Windows 10 Version 1809. Some solutions have been provided using macros, but the easiest solution is to simply click on the joystick area and hold the click outside of the tas input window. When you release the click it should still follow the mouse. Then click on Mupen, and from now until you close the rom, it will behave normally.		=== Recording an AVI on mupen produces a blackscreen with sound. What do I do? ===
			This is a bug that occurs when you use the gl64 video plugin when aero is enabled on your computer. One fix is to use another video plugin, or to disable aero on your computer. The latter is only possible on Windows 7, but unfortunately not on later versions.

			The same bug can manifest when capturing with the "Video" synchronization mode on new versions of Mupen.

			=== Mupen's TAS Input Plugin window doesn't stay focused when clicking on the main emulator window. What do I do? ===
			This is a bug that was introduced in Windows 10 Version 1809, but has been patched in the latest versions of TASInput.

			Some solutions have been provided using macros, but the easiest solution is to simply click on the joystick area and hold the click outside of the tas input window. When you release the click it should still follow the mouse. Then click on Mupen, and from now until you close the rom, it will behave normally.

	[[Category:Help]]		[[Category:Help]]

Icecream17: /* What's the next A press save going to be? */ would bring count from 13 to 12

2023-02-16T00:51:07Z

What's the next A press save going to be?: would bring count from 13 to 12

← Older revision		Revision as of 00:51, 16 February 2023
Line 55:		Line 55:
	Yes; though it is not yet confirmed to be possible, the run is being TASed until [[BitFS]]. This is because we have a good blueprint for how to do BitFS on the N64. There is currently no plan to make a 70 star no A press run on [[Wii VC]] because [[console Verification\|verifying these runs]] is difficult.		Yes; though it is not yet confirmed to be possible, the run is being TASed until [[BitFS]]. This is because we have a good blueprint for how to do BitFS on the N64. There is currently no plan to make a 70 star no A press run on [[Wii VC]] because [[console Verification\|verifying these runs]] is difficult.
	==What's the next A press save going to be?==		==What's the next A press save going to be?==
	Currently, the next A press in line to be saved is Bowser in the Fire Sea on the N64, which would bring the A press count from 14 to 13, using [[Bully Battery]] and a [[Squish Cancel]] combined together~~. This save would bring the A press count down to 13~~.		Currently, the next A press in line to be saved is Bowser in the Fire Sea on the N64, which would bring the A press count from 13 to 12, using [[Bully Battery]] and a [[Squish Cancel]] combined together.
	==How are you decompiling the game?==		==How are you decompiling the game?==
	After we discovered the compiler that Nintendo used for Super Mario 64, we obtained the raw assembly from the ROM, and reverse engineered C code that compiles into it. This was a long and tedious process, but after a couple years, the game has been fully decompiled.		After we discovered the compiler that Nintendo used for Super Mario 64, we obtained the raw assembly from the ROM, and reverse engineered C code that compiles into it. This was a long and tedious process, but after a couple years, the game has been fully decompiled.

Icecream17: /* How many A presses are left? */ 16 -> 13 (also oops on my prev edit thx)

2023-02-16T00:50:27Z

How many A presses are left?: 16 -> 13 (also oops on my prev edit thx)

← Older revision		Revision as of 00:50, 16 February 2023
Line 29:		Line 29:
	See the [[Challenge]] and [[Other Single Button Challenges]] pages for further info on these and others.		See the [[Challenge]] and [[Other Single Button Challenges]] pages for further info on these and others.
	==How many A presses are left?==		==How many A presses are left?==
	An any% run takes 0 A presses when performed on Wii VC. A 120 star run currently takes 16 A presses when performed on the original Japanese N64 version. Here's a table showing these counts on all game versions:		An any% run takes 0 A presses when performed on Wii VC. A 120 star run currently takes 13 A presses when performed on the original Japanese N64 version. Here's a table showing these counts on all game versions:
	{\| class="wikitable" style="text-align: center; width: 200px; height: 200px;"		{\| class="wikitable" style="text-align: center; width: 200px; height: 200px;"
	\|-		\|-

SuperM789: jrb 0.5x

2023-02-16T00:09:07Z

jrb 0.5x

← Older revision		Revision as of 00:09, 16 February 2023
Line 50:		Line 50:
	\|-		\|-
	! 120 Star		! 120 Star
	\| 14 \|\| 17 \|\| 17 \|\| ~~18 \|\| 18~~ \|\| 17 \|\| 16 \|\| 16 \|\| 18 \|\| 17 \|\| 17 \|\| Impossible		\| 13 \|\| 16 \|\| 16 \|\| 17 \|\| 17 \|\| 16 \|\| 15 \|\| 15 \|\| 17 \|\| 16 \|\| 16 \|\| Impossible
	\|}		\|}
	==Is a 70 Star 0 A press run being developed?==		==Is a 70 Star 0 A press run being developed?==

Rosheeki: Undo revision 17557 by Free netflix (talk)

2023-01-14T08:38:24Z

Undo revision 17557 by Free netflix (talk)

Can't load revision 17567

at 08:27, 14 January 2023

2023-01-14T08:27:15Z

best console ever is ps5

Can't load revision 17557

← Older revision		Revision as of 15:57, 29 March 2026
Line 30:		Line 30:
	See the [[Challenge]] and [[Other Single Button Challenges]] pages for further info on these and others.		See the [[Challenge]] and [[Other Single Button Challenges]] pages for further info on these and others.
	==How many A presses are left?==		==How many A presses are left?==
	An ~~any~~% run takes 0 A presses when performed on Wii VC. A 120 star run currently takes 13 A presses when performed on the original Japanese N64 version. Here's a table showing these counts on all game versions:		An Any% run takes 0 A presses when performed on Wii VC. A 120 star run currently takes 13 A presses when performed on the original Japanese N64 version. Here's a table showing these counts on all game versions:
	{\| class="wikitable" style="text-align: center; width: 200px; height: 200px;"		{\| class="wikitable" style="text-align: center; width: 200px; height: 200px;"
	\|-		\|-
Line 87:		Line 87:
	Deleting Mupen’s config file also works.		Deleting Mupen’s config file also works.

	===Recording an AVI on ~~mupen~~ produces a blackscreen with sound. What do I do?===		===Recording an AVI on Mupen produces a blackscreen with sound. What do I do?===
	This is a bug that occurs when you use the gl64 video plugin when aero is enabled on your computer. One fix is to use another video plugin, or to disable aero on your computer. The latter is only possible on Windows 7, but unfortunately not on later versions.		This is a bug that occurs when you use the gl64 video plugin when aero is enabled on your computer. One fix is to use another video plugin, or to disable aero on your computer. The latter is only possible on Windows 7, but unfortunately not on later versions.

Line 93:		Line 93:

	===Mupen's TAS Input Plugin window doesn't stay focused when clicking on the main emulator window. What do I do?===		===Mupen's TAS Input Plugin window doesn't stay focused when clicking on the main emulator window. What do I do?===
	This is a bug that was introduced in Windows 10 Version 1809, but has been patched in the latest versions of ~~TASInput~~.		This is a bug that was introduced in Windows 10 Version 1809, but has been patched in the latest versions of TAS Input.

	Some solutions have been provided using macros, but the easiest solution is to simply click on the joystick area and hold the click outside of the ~~tas input~~ window. When you release the click it should still follow the mouse. Then click on Mupen, and from now until you close the rom, it will behave normally.		Some solutions have been provided using macros, but the easiest solution is to simply click on the joystick area and hold the click outside of the TAS Input window. When you release the click it should still follow the mouse. Then click on Mupen, and from now until you close the rom, it will behave normally.

	[[Category:Help]]		[[Category:Help]]

← Older revision		Revision as of 03:22, 22 May 2025
Line 50:		Line 50:
	\|-		\|-
	! 120 Star		! 120 Star
	\| 13 \|\| 16 \|\| 16 \|\| 17 \|\| 17 \|\| 16 \|\| 15 \|\| 15 \|\| 17 \|\| 16 \|\| 16 \|\| Impossible		\| 13 \|\| 16 \|\| 16 \|\| 16 \|\| 16 \|\| 15 \|\| 15 \|\| 15 \|\| 16 \|\| 16 \|\| 16 \|\| Impossible
	\|}		\|}
	==Is a 70 Star 0 A press run being developed?==

			== Is a 70 Star 0 A press run being developed?==
	Yes; though it is not yet confirmed to be possible, the run is being TASed until [[BitFS]]. This is because we have a good blueprint for how to do BitFS on the N64. There is currently no plan to make a 70 star no A press run on [[Wii VC]] because [[console Verification\|verifying these runs]] is difficult.		Yes; though it is not yet confirmed to be possible, the run is being TASed until [[BitFS]]. This is because we have a good blueprint for how to do BitFS on the N64. There is currently no plan to make a 70 star no A press run on [[Wii VC]] because [[console Verification\|verifying these runs]] is difficult.
	==What's the next A press save going to be?==		==What's the next A press save going to be?==
Line 67:		Line 69:
	No. You clipped through the wall and went above the painting. The game checks whether or not you entered paintings by checking whether or not you are above floor triangles behind them, even when you are really high up.		No. You clipped through the wall and went above the painting. The game checks whether or not you entered paintings by checking whether or not you are above floor triangles behind them, even when you are really high up.

	== Mupen ==		==Mupen==

	=== How do you continue off of a TAS you created earlier? ===		===How do you continue off of a TAS you created earlier?===

	# Play it to where you want to continue, then save a state.		#Play it to where you want to continue, then save a state.
	# Disable read-only mode and reload the state.		#Disable read-only mode and reload the state.
	# The file will now start recording inputs from that point, erasing any you had previously made after that point.		#The file will now start recording inputs from that point, erasing any you had previously made after that point.

	=== Mupen is open, but the Mupen window disappeared and won’t come back, even when I restart. What do I do? ===		===Mupen is open, but the Mupen window disappeared and won’t come back, even when I restart. What do I do?===
	This is a glitch that occurs on old versions of Mupen when it is closed while minimized.		This is a glitch that occurs on old versions of Mupen when it is closed while minimized.

	To fix it, you must maximize the Mupen window and then drag down the top of the window, which will restore it to a normal window. To maximize the window without it actually being present, you can do one of the following:		To fix it, you must maximize the Mupen window and then drag down the top of the window, which will restore it to a normal window. To maximize the window without it actually being present, you can do one of the following:
	* [Windows 7 Only] Open task manager, right click on the Mupen program, click maximize		*[Windows 7 Only] Open task manager, right click on the Mupen program, click maximize
	* Right click on the Mupen icon in the task bar with shift held, click maximize		*Right click on the Mupen icon in the task bar with shift held, click maximize
	* Hover over the Mupen icon in the task bar, right click on the preview, click maximize		*Hover over the Mupen icon in the task bar, right click on the preview, click maximize
	Deleting Mupen’s config file also works.		Deleting Mupen’s config file also works.

	=== Recording an AVI on mupen produces a blackscreen with sound. What do I do? ===		===Recording an AVI on mupen produces a blackscreen with sound. What do I do?===
	This is a bug that occurs when you use the gl64 video plugin when aero is enabled on your computer. One fix is to use another video plugin, or to disable aero on your computer. The latter is only possible on Windows 7, but unfortunately not on later versions.		This is a bug that occurs when you use the gl64 video plugin when aero is enabled on your computer. One fix is to use another video plugin, or to disable aero on your computer. The latter is only possible on Windows 7, but unfortunately not on later versions.

	The same bug can manifest when capturing with the "Video" synchronization mode on new versions of Mupen.		The same bug can manifest when capturing with the "Video" synchronization mode on new versions of Mupen.

	=== Mupen's TAS Input Plugin window doesn't stay focused when clicking on the main emulator window. What do I do? ===		===Mupen's TAS Input Plugin window doesn't stay focused when clicking on the main emulator window. What do I do?===
	This is a bug that was introduced in Windows 10 Version 1809, but has been patched in the latest versions of TASInput.		This is a bug that was introduced in Windows 10 Version 1809, but has been patched in the latest versions of TASInput.