To play Indigo reliably, download the latest release from the project’s official GitHub page, apply its .bps patch to a legally obtained US 1.0 .z64 Ocarina of Time ROM, verify the finished file’s MD5 hash, and open that verified output in a supported emulator. The release currently listed as latest is Indigo: Chapter 2 v0.4.6 – Chaos Edition. Project64 3.0.1, Dolphin and Ares are the named emulator options; Project64 may require its interpreter core setting.
What you need before patching
Indigo is distributed as a patch rather than as a complete game image. The official Indigo releases page currently lists Indigo: Chapter 2 v0.4.6 – Chaos Edition as the latest release. Release listings can change, so check that page immediately before downloading and use the newest release shown there unless you have a specific reason to use an older build.
As an Amazon Associate I earn from qualifying purchases.
The release identifies three exact properties for the source ROM:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →- Region: United States (US)
- Revision: 1.0
- Byte order and filename type: big-endian
.z64
A ROM from another region, a different revision, or a different byte order is not an interchangeable substitute. Generic instructions for another Ocarina of Time hack may recommend a different file; Indigo’s own release instructions are the authority for this patch.
#1 Best Overall
- Full N64 Console Compatibility - Compatible with all Nintendo 64 consoles across UK, US, EU, and JP regions. The SummerCart64 supports PAL and NTSC systems for reliable gameplay on original N64 hardware.
- Open Source N64 Flashcart - Originally developed by Polprzewodnikowy, the SummerCart64 is an open-source N64 flashcart designed for homebrew development, ROM loading, and retro gaming enthusiasts seeking an EverDrive 64 alternative.
- 64DD Support & Regular Firmware Updates - Compatible with Nintendo 64 Disk Drive games and regularly updated with new firmware improvements and features. Cheat support is planned for future Summer Cart 64 firmware revisions.
- Genuine Approved Hardware Components - Unlike many resellers, Kaico follows the original BOM (Bill of Materials) specified by the creator to ensure full compatibility with future SummerCart64 firmware revisions, including the use of genuine 6TG chips for stable N64 flashcart performance.
- MICRO SD STORAGE & KAICO WARRANTY - Load and manage Nintendo 64 games directly from a micro SD card with fast access and convenient storage expansion. Includes 12-month Kaico warranty support with repair and replacement coverage.
Keep the original ROM unchanged and create a separate output file. You need a BPS-compatible patching utility, but the Indigo release does not endorse a particular program or publish a utility-specific click-by-click procedure. Use a patcher that explicitly supports the .bps format, and obtain the base game through a lawful method in your jurisdiction.
Download the correct Indigo patch
- Open the official releases page.
- Open the newest release entry. At the time of writing, that entry is v0.4.6, labeled “Chaos Edition.”
- Download the release asset whose filename ends in
.bps. Do not treat the GitHub source-code archive as the game patch unless the release specifically labels it that way. - Read the release notes beside the asset. They contain the base-ROM requirement, expected hash and platform notes used in the checks below.
The project’s repository description identifies this repository as the patch-file distribution for the Ocarina of Time Indigo mod. The releases page, rather than an unofficial mirror, is where you should confirm the current version and instructions.
Apply the BPS patch without changing the source ROM
Because no particular patching application is documented by the developer, the safest workflow is deliberately tool-neutral. Names of buttons differ between utilities, but the roles do not: the US 1.0 .z64 file is the source, the Indigo .bps file is the patch, and a new file is the destination.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Make a backup copy of the untouched US 1.0
.z64ROM. Work from the copy so you can retry without accumulating changes. - Open a BPS-capable patcher and choose its option to apply a patch. Select the Indigo
.bpsasset as the patch file. - When the utility asks for the original, source or input file, select the matching US 1.0
.z64ROM. Do not select an already-patched file. - Choose a new output filename and location. Keeping the
.z64extension makes it easier for emulators to identify the image; do not overwrite your clean backup. - Allow the operation to finish and wait for the utility to report success. If it reports a source mismatch, stop and check the region, revision and byte order before trying again.
A successful patch operation does not by itself prove that the right source was used. The release supplies a hash for that purpose, so verify the output before troubleshooting an emulator.
Verify the patched file with the published MD5
The v0.4.6 release says the patched output should have this MD5 value:
Rank #2
- 📺 Exclusive Retro Look – Collector-style cartridge with hand-drawn fan art, N64-themed postcard, and 5 unique retro stickers.
- 💾 Includes 32GB SD Card – Preconfigured for easy setup. Supports backups and homebrew content.
- 🌍 Region-Free Support – Compatible with all N64 and 64DD titles on NTSC-U, NTSC-J, and PAL consoles.
- 🧠 CIC Chip Emulation – Works on all consoles with no hardware mods required.
- 🔧 Durable PCB – High-quality board ensures long-term reliability and consistent performance.
1ccccdc1750b52c6677fa120e3b9a82f
Use an MD5-calculation tool available for your operating system and calculate the hash of the patched output, not the original ROM and not the .bps file. Compare every character, ignoring no digits or letters. The release warns that a different hash probably will not work.
- Matching hash: keep this file as your master Indigo image and proceed to emulator setup.
- Different hash: repeat the process with a verified US 1.0
.z64source, the current release’s patch asset and a fresh destination file.
A mismatch usually means the wrong release asset or wrong base image was selected, the source was already modified, or the patcher did not apply the BPS file as intended. Do not try to “repair” a mismatched image by applying the patch repeatedly; start again from the clean source.
Recommended Free Tools
Choose a way to play
The release names three emulator choices and also documents Wii Virtual Console and original-N64 routes. They are not equivalent in setup effort or documented caveats.
| Route | What the release says | Setup considerations | Documented caveats |
|---|---|---|---|
| Project64 3.0.1 | Suggested emulator; described as well tested with the GLideN64 rev.c36ffa9 graphics plugin. | Open the verified patched ROM. If it will not start, enable “Always use interpreter core” in Project64’s advanced configuration. | The interpreter-core setting may be necessary for startup. |
| Dolphin | Suggested emulator. | Load the verified patched image using Dolphin’s normal ROM-opening workflow. | The release does not specify a particular graphics plug-in or version. |
| Ares | Suggested emulator. | Open the verified patched image in Ares. | No additional Ares-specific configuration is documented. |
| Wii Virtual Console | Labeled compatible. | For an injection, apply an 8 MB memory patch. The mod uses D-pad and L-button inputs; optional remapping codes are supplied with the release instructions. | Injection and controller work are separate from emulator setup. |
| Original Nintendo 64 with a compatible flash cartridge | EverDrive-based play is described as compatible and completable. | Transfer the verified image to compatible flash-cartridge hardware and use the hardware’s normal loading process. | The author warns of lag in some places and texture z-fighting. |
| ModLoader64 | Explicitly unsupported. | Do not use it as an Indigo launch route. | The release says it will not be supported. |
The release also says that most non-ancient emulators should work, but that broad statement is not a guarantee for every emulator, plug-in or future version. The named options above are the documented starting points.
Launch Indigo in Project64
Project64 3.0.1 is the most specifically described emulator route. The release reports it as well tested with the GLideN64 rev.c36ffa9 graphics plugin. If you are using another plug-in or a different Project64 build, your menus and behavior may differ.
Rank #3
- [OPEN SOURCE PLATFORM] Enjoy a flexible open source game cartridge compatible with N64 consoles. Relive classic adventures or explore custom creations with a platform designed for retro players and developers who want more control over their gaming library.
- [LARGE GAME CAPACITY] Support games up to 64MB and use the built in 16GB memory card to store an extensive collection of compatible titles. Add or delete games through a straightforward menu and keep your favorite retro experiences ready to play.
- [FAST GAME LOADING] With transfer speeds reaching up to 23.8 MiB/s this cartridge helps reduce loading delays and gets you into gameplay faster. It supports N64 cartridge images plus combination games and multi disk games for a smooth retro gaming experience.
- [MULTI SYSTEM EMULATION] Play supported ROM files from GB GBC SMS GG and CHF systems through the built in emulator functions. ROM files are not included and must be obtained separately from sources for personal use.
- [SAVE AND EXPAND] Auto save backup helps protect your progress while RTC clock support keeps time based features working. Connect through USB Type C to manage content and expand functions with features such as background images music playback and menu sound effects.
- Install or open Project64 3.0.1 and make sure the verified Indigo output is accessible from your ROM folder.
- Use Project64’s normal open-ROM command and select the patched
.z64file. Do not open the clean base image or the.bpspatch. - If the game does not start, open Project64’s advanced configuration and enable the option labeled Always use interpreter core. The release gives this exact setting as the fix for startup problems.
- Close and reopen the ROM after changing the setting. If it still fails, stop and verify the MD5 before changing several graphics or emulation options at once.
Keeping one variable at a time makes diagnosis possible: first confirm the hash, then apply the documented interpreter-core setting, then consider whether your emulator version or plug-in falls outside the release’s tested combination.
Use Dolphin or Ares
Dolphin and Ares are listed by the developer as suggested emulators, but the release does not prescribe a special plug-in, graphics profile or command sequence for either one. Use the normal method for opening an N64 ROM in your installed version:
- Start with the MD5-verified Indigo output.
- Open that file through the emulator’s ROM browser or open-file command.
- If the emulator rejects the file, confirm that you selected the patched
.z64output and not the BPS patch or clean source. - Check the release page for a newer Indigo version before experimenting with settings from unrelated hacks.
The statement that most non-ancient emulators may work should be read as a practical possibility, not a compatibility promise. A successful launch in one emulator does not prove that every plug-in or build will render the game correctly.
Wii Virtual Console: the extra memory and control steps
The release labels Wii Virtual Console compatible, but this route involves injection work that emulator users do not need. For an injection made with gzinject, the release instructs users to apply an 8 MB memory patch. Treat that as a Wii Virtual Console-specific requirement; it is not a step for Project64, Dolphin or Ares.
Indigo uses the D-pad and L buttons. The release includes optional remapping codes for Wii Virtual Console installations. Use the codes and the exact instructions published with the release rather than importing controller codes from another mod. If your injected title launches but an action appears unavailable, check the controller mapping before assuming the ROM patch failed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Extensive Game Collection: The included 32GB TF card comes pre-loaded with a diverse selection of nearly 5000 game titles compatible with your Nintendo 64 console. Please note that due to compatibility with various console versions, some game files may appear duplicated. This is normal operation.
- Blazing-Fast Performance: Experience incredibly fast load times and smooth gameplay thanks to a peak transfer rate of 23.8 MiB/s.
- Comprehensive 64DD Emulation: Relive the experience of the 64DD peripheral with full emulation, allowing you to play games originally released only on this add-on.
- Enhanced Features: Beyond gaming, enjoy added functionalities such as MP3 music playback, background image support, and a user-friendly menu system.
- Advanced Save System: Never lose your progress again with reliable auto-save functionality.
- Patch and hash-check the Indigo image on a computer first.
- Follow your established Wii Virtual Console injection process and select the verified image.
- Apply the release’s 8 MB memory patch during the injection workflow.
- Configure the D-pad and L-button inputs; apply the optional remapping codes from the release if your controller arrangement needs them.
- Test basic movement and the L-button function before beginning a long play session.
These instructions describe what Indigo’s release requires, not a complete gzinject tutorial. The release does not replace the injector’s own documentation, and a Wii-specific injection problem should be separated from a patch or hash problem.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Playing on an original Nintendo 64
The developer reports that Indigo can be played to completion on an original N64 with an EverDrive-compatible flash cartridge. This is optional hardware, not a prerequisite for the software or emulator route. You still need to create and verify the same patched image first.
Copy the verified file to the flash cartridge using that device’s normal storage procedure, then launch it on the console. The release warns that some areas may exhibit lag and that texture z-fighting can occur. Those are documented characteristics of this route, so changing emulator settings cannot remove them from real-hardware play.
Choose this route when using original hardware is more important than the convenience of a desktop emulator. It requires compatible flash-cartridge hardware and a way to transfer files to it; neither is needed for the named emulator options.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Enable and manage Chaos Mode
Version 0.4.6 backports Chaos Mode. The release says it adds no new content compared with the Chapter 2 demo; it changes how the existing game behaves through randomized or altered effects.
Best Value
- 【INCLUDED】- ED64 Latest N64 Plus + 16gb SD Memory Card (No ROMS/GAMES are included)
- 【DISCLAIMER】 - No ROMS/GAMES are included
- 【SAVE GAME】 ---RESET BUTTON = To save the game, you need to press the Reset button.
- 【COMPATIBILITY】- Support PAL and NTSC consoles-- American and Japanese N64 Console
- 【SUPPORT】 - Support SD and SDHC card with FAT, FAT16, FAT32 format (maximum 32GB)
- Start Indigo and reach the file-select screen.
- Select File 3 to activate Chaos Mode.
- During play, press D-pad Right to view the active effects.
- Save often. The release warns that Chaos Mode can cause softlocks or crashes.
Chaos Mode is optional. If you want the most predictable first playthrough, use a normal file instead of File 3. If an effect leaves the game in an unrecoverable state, reload an earlier save rather than assuming the emulator or patch is defective.
Troubleshooting by symptom
The patcher reports an invalid source or refuses to apply the patch
- Confirm that the source is a US 1.0 ROM, not merely a US ROM.
- Confirm that the file is big-endian
.z64, not another byte order. - Download the current
.bpsasset from the official release entry again. - Start from an untouched source copy; do not patch an output from a previous attempt.
The patched file launches nowhere
Calculate its MD5 first. If it is not 1ccccdc1750b52c6677fa120e3b9a82f, rebuild it from the specified source and current patch. The release explicitly cautions that a different hash probably will not work, so emulator hopping is unlikely to solve a source-file mismatch.
Project64 opens but Indigo does not start
In Project64’s advanced configuration, enable Always use interpreter core, then reopen the verified image. This is the release’s documented Project64 startup remedy. If the problem remains, recheck the hash and note your Project64 and graphics-plugin versions before trying other changes.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe picture has glitches or the game slows down on real hardware
For original N64 play, lag in some places and texture z-fighting are documented warnings. They are not evidence that the patch failed. Verify the image, then decide whether the emulator route better suits your tolerance for those hardware-specific artifacts.
Controls do not work in a Wii Virtual Console injection
Check that the 8 MB memory patch was applied during injection and that D-pad and L-button inputs are mapped. The release’s optional remapping codes are intended for this route; they do not apply automatically to desktop emulators.
Can I use ModLoader64?
No. Indigo’s official release explicitly marks ModLoader64 as unsupported. Use one of the named emulator, Wii Virtual Console or original-N64 routes instead.
Quick Recap
A clean, repeatable checklist
- Use the newest release listed on the official releases page.
- Download its
.bpspatch. - Prepare a legally obtained US 1.0 big-endian
.z64base ROM. - Apply the patch to a copy and preserve the clean original.
- Verify the output MD5:
1ccccdc1750b52c6677fa120e3b9a82f. - Choose Project64 3.0.1, Dolphin, Ares, Wii Virtual Console or compatible N64 flash-cartridge hardware according to the documented caveats.
- For Project64 startup failures, enable Always use interpreter core.
- For Wii Virtual Console, apply the 8 MB memory patch and configure D-pad/L controls.
- For Chaos Mode, select File 3, inspect effects with D-pad Right and save frequently.
- Do not use ModLoader64, which the release marks unsupported.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
