FAQ: Difference between revisions

511 bytes added ,  10 September 2018
no edit summary
No edit summary
No edit summary
Line 7: Line 7:
==Why Mupen over Bizhawk?==
==Why Mupen over Bizhawk?==


Most TASes of Super Mario 64 are done on [[Mupen64]]. This is for two reasons, one, the M64 file can be played back on console, known as [[TASBot#Console Verification|Console Verification]] and two, Bizhawk polls inputs on lag frames as opposed to Mupen64, which doesn't. BK2 files (Bizhawk movie files) can still be converted to M64 files however.
Most TASes of Super Mario 64 are done on [[Mupen64]]. This is for one reason only - 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 for many it comes down to personal preference.


==What is STROOP?==
==What is STROOP?==
Line 17: Line 17:
Mupen (otherwise known as Mupen64) is an emulator used for N64 games and Super Mario 64 that is most commonly used for TASing
Mupen (otherwise known as Mupen64) is an emulator used for N64 games and Super Mario 64 that is most commonly used for TASing


==Where can I get a 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.


==How many Challenges do we have?==
==What different challenges are there?==


As of right now, we currently have 11 challenges.
As of now, there are 10 challenges that have gained some popularity, along with many minor ones. Some of the more well-known include:


*[[UBER Challenge]]
*The [[UBER Challenge]]
*[[Pacifist Challenge]]
*The [[Pacifist Challenge]]
*[[A Button Challenge]]
*The [[A Button Challenge]]
*[[Coinless Challenge]]
*The [[Coinless Challenge]]
*[[Capless/Cannonless Challenge]]
*The [[Capless/Cannonless Challenge]]
*[[CCC Challenge]]
*The [[CCC Challenge]]
*[[No Buttons Allowed Challenge|No Buttons Allowed/Buttonless Challenge]]
*The [[ABZ Button Challenge]]
*[[ABZ Button Challenge]]
*The [[Low Doors Challenge]]
*[[Low Doors Challenge]]
*The [[No Joystick Allowed Challenge]]
*[[No Joystick Allowed Challenge]]
*[[The Floor is Lava Challenge]]
*[[The Floor is Lava Challenge]]


==How many A presses are left?==
==How many A presses are left?==


An any% run takes 0 A presses, performed on Wii VC. A 120 star run takes 23 A presses, performed on N64 JP original version. Here's a table showing these counts on all game versions:
An any% run takes 0 A presses, performed on Wii VC. A 120 star run currently takes 23 A presses, 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 68: Line 67:
No.
No.


A WiiVC TAS is not being developed because there is no way to console verify a TAS on WiiVC at the moment and even if there was, WiiVC polls inputs on lag frames, meaning that the TAS would become desynced over time.
A WiiVC TAS is not being developed because there is no way to console verify a TAS on WiiVC at the moment, and even if there was, WiiVC polls inputs on lag frames, meaning that the TAS would become desynced over time; and. as was previously mentioned, 70 Star is not currently possible 0x on any N64 version.


==What's the next A press save going to be?==
==What's the next A press save going to be?==
Line 76: Line 75:
==How are you decompiling the game?==
==How are you decompiling the game?==


Essentially, we've figured out the compiler that Nintendo used for Super Mario 64 and then we get the raw assembly from the rom, and see what C code compiles into that. This is a long and tedious process but many prominent members of the community have made excellent progress so far.
After we discovered the compiler that Nintendo used for Super Mario 64, we obtained the raw assembly from the rom, and are reverse engineering C code that compiles into it. This is a long and tedious process, but many prominent members of the community have made excellent progress so far.


==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)?==


The default hat state is to not wear a hat, and each frame it checks if he's wearing a hat and sets that graphics flag. But when Mario goes OOB, most mario code doesn't execute, including that check. So 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?==
==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 glN64 video plugin when aero is enabled on your computer. One fix is to use another video plugin. Another fix is to disable aero on your computer, which is only possible on Windows 7, not Windows 8/10.
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 Windows 8 or 10.


==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. Then make sure read-only is disabled and load the state
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.