<![CDATA[Hack64 - Super Mario 64]]> (2024)

Note that this only works for SM64 ROM Manager, and not SM64 Editor or Decomp. That said I may probably port this to Decomp and Bowser's Blueprints eventually. (I already ported Boo Key/Door and Sunshine Dive Last year to decomp)
It is also 90% backwards compatible with MOP 1-3 (ROM Manager Versions), minus Purple ! Box and Beta Shells

It includes 6 new objects for SM64:
Name - Is Global? - Model - Behavior
Boo Key - Non-Global - 0x55 - 0x13001744
Boo Door - Global - Works with any door model - 0x13000F14
Red Koopa - Non-Global - Refer to included docs or set to 0 - Koopa Behavior
Red Koopa Shell - Global - Refer to included docs or set to 0 - Koopa Shell Behavior
Purple ! Box - Not Global? - Refer to included docs or set to 0 - ! Box Behavior (Bparam 2 = 4)
Creeper (Aw Man) - Global - Refer to included docs or set to 0 - 0x130022D8

Release Trailer/Download:

I've contacted Pilz to see if he can integrate this into RM as well, so it should work with Global Object Bank soon and what not. If anyone has any ideas for future patches I could make HMU with some ideas, such as a More Collisions Patch or a More Powerups/ ! Blocks Patch, etc, etc.]]>

I want to import the unused star dance and other animations, i want the beta penguin, if anyone here can help me, please reply to me.]]>

You can write a list of GameShark codes in a txt file, and SM64GSW can write each code line by line into aROM file. Alternatively, you can type each code into SM64GSW.

As of version 1.1, Linux x86, Linux x86_64, and Windows 95-Windows 10 builds are available on the officialweb page(which also contains the complete documentation.

]]>

and this project has moved to GitHub.

SM64GSW by Alex Free

==Info==
An open source (3-BSD) console program that can write GameShark/Xploder64 codes directly into a
Super Mario 64 USA ROM.

SM64GSW performs Messiaen64's manual hex editing method written at https://sites.google.com/site/messiaen64...hark-codes in software automatically so you don't
have to hex edit your SM64 ROM manually.

==Requirements==
- The Windows version is a 32-bit binary compatible with Windows 95 and above.
- Windows 95 requires MSVCR.dll (Windows 95 OSR2.5 and above already include it). One way you can get this is by updating Internet Explorer to version 4.0.
- A Super Mario 64 USA ROM in .z64 or .N64 (N64 SDK) format. The .n64 and .v64 formats are not supported.

==Usage==

1) Start SM64GSW in one of 2 different ways.

Command line method:
- Open cmd.exe or command.com.
- Execute the 'sm64gsw' command with your ROM as the argument. For example, the complete command could be
"sm64gsw C:\sm64.z64".

Windows Explorer method:
- Drag your ROM file on top of the sm64gsw.exe file.

2) Select your code input preference at the input selection menu.

SM64GSW can write codes contained in a txt file of your choosing, or you can input them with the keyboard.
In keyboard mode after each code is entered, it will be written to the ROM and you will be asked if you want to enter another code or to exit.
In file mode, you will be prompted to enter the file path (that must not contain spaces!) for a txt file containing codes. The txt file
can contain a code or multiple codes, one code per line. The file 'gs.txt' in this release is an example of this.
You can manually type in the file path, drag and drop the rom into the SM64GSW.exe window, or copy - paste the file path if in cmd.exe.

If SM64GSW tells you 'Attention: At least one code invalidates the internal ROM checksum, run checksum64
on your ROM before playing' you MUST run the 'chksum64' program on the ROM file after writing your codes. You
can do this by dropping your newly modified ROM on top of the chksum64 executable (Chksum64 is written by Andreas Sterbenz).

3) Test the ROM.

==What Codes Work?==

There is an incomplete list of some codes that work in the file named 'known_working_codes.txt' in this release.

Supported RAM range is 80246000-80333000. The 3rd-8th digits of a code must be a hexadecimal value in the
range of 246000-333000 to work.

Not all N64 GameShark/Xploder64 code types are supported. This is due to certain code types not translating
into just hex writes for various reasons, such as codes that:
- Require physical hardware (like a GS button).
- Perform live checks and or dynamic modification.
- Simply not being appliable (Expansion pack releated, non-Super Mario 64 security chip related).

Code types are defined by the first 2 hexadecimal digits of a code. For example, in the level select code
'A032D58C 0001' 'A0' is the code type. For multi-line codes, if any lines contain an incompatible code type
the entire code can not be written into ROM. See the table below for specifics.

Supported codes include 80, A0, F0, 81, A1, and 2A. 80, A0, and F0 must be in the X0XXXXXX-00XX format.

==License==
- This is open source software, released under the 3-Clause BSD license (read license.txt). It **should** compile
and work on other little-endian Operating Systems.

==Changelog==
==Version 1.0.1==
- Fixes a bug which prevented codes from being entered by the keyboard, after an invalid code was entered.

Sorry if this is not the place for this question, but I haven't been able to find anyone who knows.

Also, is there a way to determine whether a ground tile is a slope (determine whether mario can walk on it or if he will slide when stood on)?]]>

This tool will inject a modified version of the Fast3D 2.0D microcode that will block any attempt to write the IM_RD render mode flag into the RDP's othermode variable. Doing this forces the game to use the reduced anti-aliasing mode, which should improve performance on console by 3-4 fps (~10%).

Just simply open up a Super Mario 64 ROM file, and then you can click the "Reduce the AA!" button if the ROM is compatible. Once the button is pressed, it will create a new ROM file with the ".ra" prefixed to the extension. For example,using the rom file "sm64.z64" will generate a new rom called "sm64.ra.z64".

Any SM64 ROM that uses the Fast3D 2.0D microcode is compatible. This includes the Japanese and North American versions of SM64 and any ROM hacks made with those versions.

The compatibility with emulators will mainly depend on what kind of plugin that you use. In theory, high-level emulation plugins like should not have any problems if they assume that this microcode is just regular Fast3D. However, as mentioned in the replies below, some plugins like GlideN64 v4.0 doesn't seem to emulate the microcode correctly.

Also some low-level emulation plugins like angrylion do not like the custom microcode, and may make the game lag even more than before. Which is weird, because the microcode runs fine on real hardware.¯\_(ツ)_/¯

The beginning area of Jolly Roger Bay does lag a significant amount. Going down to a 22 fps minimum in my testing. Injecting the modified microcode makes a significant difference in the feel of the game, with the minimum increased to 25 fps.

My jolly roger bay benchmark starts at the beginning of the level and has Mario swim into the underwater cave. The framerate is bad in the beginning, but gets a lot better when you are deep underwater.

Download: https://github.com/DavidSM64/SM64-Fast3D...r/releases
Source: https://github.com/DavidSM64/SM64-Fast3D-AA-Reducer/

The idea of combining the best parts of sm64 physics with portal mechanics is to enable more unique and interesting variations in rom hacks.With portal objects and physics integrated a lot of new opportunities open up for level design, playing with physics in interesting ways and creating various forms of puzzles.

Only basic rom hacking knowledge is required to use these tools (the tutorial covers everything)

Objects included:

• Sentry Turret
  
• Cube
  
• Light Bridge
  
• Laser Beam
  
• Receptacle Laser
  
• Receptacle Pellet
  
• Reflect Cube
  
• Excursion Funnel
  
• Excursion Funnel Switch
  
• High Energy Pellet
  
• Gel (blue)
  
• Gel (yellow)
  
• Gel (faucet)
  
• Chamber Door
  
• Connected Metal Box
  
• Connected Metal Box (Appearing)
  
• Switch with Hidden Boxes
  

Downloads:
https://mega.nz/#!VkdkWSYT!FeKiVGj75y60H...HmVDfoQvh8]]>

To see all the feature of this engine, see this video:https://youtu.be/A-YfaQpm5-A

This is installed as an asm patch, it will take the rom space from 0x1203800 - 0x12052C0. Included isthe function itself "print string notes", the keyboard used for user input(simply place the entire file at 0x1204FFC)andan HTML file called "special_text_encode". This is a tool to make creating the strings easier since you can encode the cmds along with the text. The asm fileincludes two functions for the user to easily activate the text.

To make the strings, you place cmds inside the actual string. Cmds will be bytes unused by the normal sm64 text encoding and will have some parameters following them (ex. 40 0001 - set text speed to 1 VI per character).

Below is a list of all the cmds included along with some things to keep in mind while using them

The hack64 forum software doesn't seem to support tables, but here's an external markdown doc: https://hackmd.io/opEB-OmxRa26P8h8pA-x7w as well as a decoder: https://gist.github.com/simonlindholm/30...22c291f878

The list of commands should be complete, though some of the descriptions are a bit vague. I could look closer into the code if there's some particular aspect that people are interested in.]]>

The program is still in an early alpha, I'd say, so some things might break especially when working with romhacks. For that I recommend using the CLI, to have a more verbose output on whats wrong. Please feel free to come into the discord for support on running the randomizer on romhacks, or in general when you're having trouble using it.

Current features:

• Object position shuffle*
  
• Spawn position shuffle
  
• Music track shuffle
  
• Warp entry/exit shuffle
  
• Castle Paintings match levels (levels without a painting will show a placeholder)
  
• Dialog/Text shuffle
  
• Coin-color shuffle
  
• Mario's Outfit shuffle
  
• Configurable via CLI or GUI
  
• Extends your ROM automatically
  
• Web Generator
  

Screenshots:

The program includes a simple GUI for Windows/Mac/Linux:

This project has been a lot of fun, so I'm looking forward to having more people on board with suggestions, playtesting and development help. Feel free to join our (relatively empty) discord server for updates and support!

(I posted here instead of in projects because I feel it is more than SM64 specific, considering it works with any SM64 based ROM - Feel free to move, if that was a bad choice)]]>

Super Beginner:

Preface:Introduction to hexidecimal, ram/rom + banks and offsets, quick custom model importing + behavior scripts explanation

Beginner

Part 1:MIPS asm intro, the object struct and how you can use it to control objects

Part 2:floats, branches, jumps, the stack and functions and some example uses

Part 3:The mario struct, interactions and more in depth behaviors

Part 4:Practical examples and explanations

Aside:using the debugger (overview)

Advanced:

Part 5:Collision and Display Lists Introduction

WIP:

• Advanced F3D w/ asm
• The model loading process
  

If you would like to contribute please message me or post in this thread. These tutorials will also be featured on my webiste:https://sites.google.com/view/supermario...authuser=0]]>

Here is my WIP list of the playsound ROM addresses I've found so far:

Playsound Locations (In an arbitrary order):

Mario Screen "Hello!": 0x21F8C2
Mario Screen "Press Start to Play!": 0x21F8DE
Mario Screen Star (Pressing Start): 0x21F91A
Mario Screen "Game Over!": 0x21F992
Title Screen Coin + It's a Me Mario (credit to Kaze): 0x21FA3E
Bowser Laugh when you die: 0x5B5A
Coin (credit to Xeraclom14): 0x6216
Coin (Underwater): 0x6206
Enter Warp Pipe: 0x9056
Exit Warp Pipe (Like in THI): 0x1457A
Enter Warp Hole: 0x9062
Waterfall: 0xAB7FE
Volcano: 0xAB82A
Birds 1: 0xAB8FA
Birds 2: 0xAB90E
Birds 3: 0xAB922
Crickets: 0xAB97A
Sand: 0xAB9CE
1-up Sound: 0xAEC7E
Goomba Smashed: 0xB63AA
Goomba Alert: 0xBA522
Small Bully Grunt: 0xA61F6
Monkey Message: 0xEDF04
Big Penguin Message: 0xEDF08
Short Bowser Laugh Message: 0xEDF0C
KTQ Message: 0xEDF10
King Bob-Omb Message: 0xEDF14
Boo Message: 0xEDF18
Bob-Omb Buddy Message: 0xEDF1C
Long Bowser Laugh Message: 0xEDF20
Whomp Message: 0xEDF24
Wiggler Message: 0xEDF28
Yoshi Message: 0xEDF2C

Free free to contribute to this list if you'd like and I can update it!]]>

First you need to know which version of SM64 you are using. The only difference between the different versions of SM64 is the addresses in RAM. For this post I'm going to keep things vague so you can follow with any version.

The idea is that you first set the warp delay timer to some value above 0 (minimum of 1), set the Warp ID, then set the first value to any number besides zero. The warp delay timer decrements every frame. Once it reaches zero, the warpwill activate instantly.

Warp ID 0xF1 is used when Mariodies. He will exit the level and lose a life in the process.

Note: The player will not Game-Over if Mario has 0 lives. The game will decrement Mario lives to -1. You will need to check Mario's lives yourself.

Warp ID 0xF0 is used when Mario grabs a star or bowser key. He will go back to the castle and prompt the "Save and Continue" menu.

Note 1: Since you didn't actually collect a star/key, the star counter will not be increased. You will need to code that in yourself.

Note 2: You need to set a specific byte in RAM, otherwise the game will crash when trying to display the text of the star you should've gotten. It is normally set whenMario grabs a star/key. This byte should be set between 1 and 6, corresponding to the act # you want to display.

Below is a table with the corresponding to the address of the byte you need to change for each version:

[J] [Q] [V] [X] [Z] [!] [!!]
[?] [&] [%] [Circle] [Key]

Compatible with SM64 (U) ROMs extended with VL-Tone's extender or equivalent.

Summary

• Appends image data from more-letters.bin to segment 02
  
• Updates segment-offset pointers in the character table
  
• Updates segment 02 loader addresses
  

• 0x1800 bytes of free space at 0x0081D364 (or NUM_CHARS * 0x200)
  

• Reduce NUM_CHARS in more-letters.asm if SM64 crashes
  

This is a Blender plugin I've been working on that allows you to import custom Mario models, without having to manually import each body part separately. It also lets you import/export custom display lists. It relies on Blender custom data attributes that determine how the mesh in Blender is imported.

Features (import means import into Blender)

• Mario import/export
  
• Modified bone lengths are saved, excluding the root bone
  
• Face animation supported
  
• Can import custom hatless head/other hand poses
  
• Will update metal/vanish models
  
• Geo layout import
  
• Display List import/export
  
• Custom color combination functionality
  

• Textures are not imported, only exported
  
• The Blender custom data attributes are necessary for the plugin to work; Make sure to follow the process outlined in the instruction files.
  

You can see all the pictures in this imgur album:https://imgur.com/a/lSP90bM

You can see the AO & Shadow texture maps individually here: https://imgur.com/a/Uze5UaS]]>

There is a peculiar up arrow texture stored at offset 0x17698, right in the middle of some F3D display lists. I don't recall seeing it in the game. It is the first arrow listed in the picture below. The other font textures that look like arrows are listed for reference as well.

The ambient and diffuse lighting parameters for the paintings are stored at offsets 0x177B8 and 0x177C0 respectively. You can use this to change how the paintings are rendered while animating. Here, I made the diffuse color red instead of white.

The vertex and triangle data used to construct the animated painting triangle mesh is stored at offset 0x178C0 (0x81AA16 extended ROM) and takes the following format. The Z values of the vertices don't matter as they are controlled by code, but the X and Y can be adjusted for some interesting results. I tried changing the order of the last triangle table, but it just locked up the game when I touched a painting, so it means something.

As a test, I compressed the top and bottom triangles and expanded the middle ones as shown. Looks pretty bad in game:

SM64 ROM Manager

Developed by Pilzinsel64

Download:

The SM64 ROM Manager is a brand new all-in-one tool for SM64 Hacking!

Bug fixes and small improvements I will publish ASAP as small updates (third number of version).

New features comes with big feature updates (second number of version).

Here is a list of things that are already finished:

• Level Manager
• Create and remove Levels easily.
  
• Add and remove areas in your levels easily (with up to 8 areas per level).
  
• Change the level ID easily (if the level is replacing level 1, you can easily change that to e.g. Level 2).
  
• Set up many level dedicated settings every time.
  
• Set up many area dedicated settings every time.
  
• Select objects banks for your level (Optional).
  
• Import and Replace Area Modes
  
• Export Level Model & Collision
  
• Export Object Models
  
• One-0xE-Bank-Per-Area
• This allows you to move the model size limit from per-level to per-area.

• That means that now you have around 1.5 times as much space for a single area as you used to have for an entire level in the past.

• Down in this post, I explained the system of it, so the developer can add support for Levels with this system.

FAQ and Information:

"Can I use my SM64 Editor made ROM with this tool?"
It isn't supported and never will be because there are too many bugs to solve in the ROM. Like the N64 compatiblity e.g.

But there is an experimental way to import your levels to a new ROM.
Just open a new ROM and goto "Level Manager". Click the arrow on the left of "New Level" and click "Import Level ..".
Then select your ROM (used by SM64 ROM Manager or SM64 Editor) and import any Custom Level that the ROM Manager is able to read.

"What happens if I edit the levelscript, geolayout or displaylist?"
Nothing. The SM64 ROM Manager reads the edited script and keeps the changes.
Note: After you changed something on the ROM outside the ROM Manager, you need to reload your ROM .

"Where are the Objects/Warps located"?
If the One-0xE-Bank-System is enabled, then the objects and warps are located in the "special" 0xE-Bank. This "special" 0xE-Bank will be loaded at parsing the levelscript and will be cleared at loading the first area. I can do that while the objects and warps will not be needed anymore after loading them. So, we have more space in the levelscript and for the area model, yeah!
If the One-0xE-Bank-System is disabled, then they are located in Bank 0x19 directly in the levelscript.

The One-0xE-Bank System explained:
In the Levelscript is an area table. The levelscript is mainly located in Segmented 0xE. So, the data for the current area is located at 0x19005F00 + AreaID * 0x10. The first four bytes shows the ROM address where the bank 0xE for this area starts. The second four bytes shows the ROM Address where the bank 0xE of this area ends. So, it is like a 0x17 levelscript command, but without the first four bytes of such command. But how do I know that the System is enabled? Easy. Just check the four bytes at 0x19005FFC. If they equal to 0x4BC9189A then the One-0xE-Bank-System is enabled. Otherwise, the 0xE Bank is per Level (as known from the SM64 Editor).

Please note: The One-0xE-Bank-System is not supported in SM64 Editor Levels (in converted ROMs).

"My Textures are offset a bit. Is it a bug?"
No, it isn't. The SM64 ROM Manager does everything right. The problem is your video plugin in your emulator. Many popular plugins does have this bug, such as GLideN64, Glide64, Jabos Direct3D, and some others. The texture is offset a half pixel then. But on a real N64 the textures are on the right place.
Read here an issue on GLideN64 plugin repository.

Any more questions? Any Errors/Issues? Any ideas or suggestions?
Let me know!

• Ask questions
  
• Explain errors in detail
  

Bug Reports & Feature Requests:

Credits:

• Big thanks to Kaze Emanuar for coding some useful ASM codes, answering my questions and motivating me.
  
• Also a very big thanks to all who supported me and believed in my new tool, which motivated me a lot.
  

Links:

On my website, you will find the changelog and download.

Other tools that I have made for SM64 Hacking can be downloaded on my site.

Subscribe to my channel to get information about updates or new previews.