Hacking Injecting N64 roms... for idiots, please?

  • Thread starter Thread starter Osakasan
  • Start date Start date
  • Views Views 27,675
  • Replies Replies 25
  • Likes Likes 1

Osakasan

Well-Known Member
Member
Joined
Sep 19, 2015
Messages
1,310
Reaction score
1,132
Trophies
2
Age
41
XP
3,623
Country
So, i want to experiment a little bit with Ng4 VC rom injection because there are games that we basically KNOW that are not going to reach the eShop. NEVER

However i can't find any reliable tutorial, not even here. A little help please? So far i have Loadiine last version in my U, but i don't know what to do with it.
 
  • Like
Reactions: SlimPortable
So, i want to experiment a little bit with Ng4 VC rom injection because there are games that we basically KNOW that are not going to reach the eShop. NEVER

However i can't find any reliable tutorial, not even here. A little help please? So far i have Loadiine last version in my U, but i don't know what to do with it.
  1. Dump a legit N64 VC with ddd or pirate one.
  2. Name it properly for Loadiine.
  3. Go to content/rom and delete whatever's there, remembering the filename (may be unnecessary, isn't for 3ds)
  4. Copy your rom in n64 format there, and rename it + extension to the old one.
  5. Put it on SD and play it with Loadiine.
 
  • Like
Reactions: SlimPortable
  1. Dump a legit N64 VC with ddd or pirate one.
  2. Name it properly for Loadiine.
  3. Go to content/rom and delete whatever's there, remembering the filename (may be unnecessary, isn't for 3ds)
  4. Copy your rom in n64 format there, and rename it + extension to the old one.
  5. Put it on SD and play it with Loadiine.

So I tried injecting Banjo-Kazooie and Ocarina of Time: Master Quest using Donkey Kong 64 and Ocarina of Time respectively as base.
I can load both "base" games perfectly fine with loadiine, but when I try to load one of the injected ones I only get a black screen (and in the case of Banjo-Kazooie the Wii U even frreezes and I have to unplug it.)
What am I doing wrong?
 
So I tried injecting Banjo-Kazooie and Ocarina of Time: Master Quest using Donkey Kong 64 and Ocarina of Time respectively as base.
I can load both "base" games perfectly fine with loadiine, but when I try to load one of the injected ones I only get a black screen (and in the case of Banjo-Kazooie the Wii U even frreezes and I have to unplug it.)
What am I doing wrong?
Can I have a screenshot of the folder in content/rom?
 
Ok, fixed my issue with OoT:MQ by using a different base (I think I used Mario Kart 64).

Banjo-Kazooie won't work, though. According to the Wiki BK schould be injected into DK64. That's what I did. Take Donkey Kong 64 PAL as a base, note the filename of the file in content/rom, copy a Banjo-Kazooie PAL N64 ROM into the folder and rename it to the noted filename. Everytime I launch it, it crashes my Wii U.
screenshot_BK.png
 
  • Like
Reactions: KiiWii
Ok, fixed my issue with OoT:MQ by using a different base (I think I used Mario Kart 64).

Banjo-Kazooie won't work, though. According to the Wiki BK schould be injected into DK64. That's what I did. Take Donkey Kong 64 PAL as a base, note the filename of the file in content/rom, copy a Banjo-Kazooie PAL N64 ROM into the folder and rename it to the noted filename. Everytime I launch it, it crashes my Wii U.
screenshot_BK.png
Try downloading this, renaming it to config.ini, and putting it in /wiiu/games/Banjo-Kazooie [N64BJK]/content, replacing the existing one.
 
Protip: The base is irrelevant, and the rom filename is irrelevant. All that matters is that you have a proper config.ini file for your rom that matches your proper filename. So for example you have MarioKart64.z64 in the rom folder? Your config.ini needs to be renamed to MarioKart64.z64.ini and placed in the config folder. ALL the other ini files in the config folder can be safely deleted since they are for other games.

I injected Donkey Kong 64 into Super Mario 64 with its official config.ini just to see if the bases were different, and if the bases weren't uniform, this absolutely would have crashed. It's interesting how many games Nintendo has made ini files for that they won't be releasing, for me Mario Kart 64 and Mario Party 2 were the ones I ended up wanting.

I'm definitely interested in setting up some kind of debugger setup. If we could try running unsupported roms, figuring out where they crash and building custom config.ini files off that, it's possible we could support more roms than currently available. (Or not I'm just spitballing ideas right after waking up)

Another tip: If you started messing with files in the meta folder, you could change the game name and icon and etc so it actually shows as your game in loadiine. Unnecessary for the most part, but I was glad to have all my games show up as the proper title ;) I also gave my injections custom TitleIDs that other games wouldn't be using so there wouldn't be any conflicts down the line (Like INJ101, INJ201, etc)

Anyways sorry for the long ramble post, hopefully there's something helpful in there
 
Protip: The base is irrelevant, and the rom filename is irrelevant. All that matters is that you have a proper config.ini file for your rom that matches your proper filename. So for example you have MarioKart64.z64 in the rom folder? Your config.ini needs to be renamed to MarioKart64.z64.ini and placed in the config folder. ALL the other ini files in the config folder can be safely deleted since they are for other games.

I injected Donkey Kong 64 into Super Mario 64 with its official config.ini just to see if the bases were different, and if the bases weren't uniform, this absolutely would have crashed. It's interesting how many games Nintendo has made ini files for that they won't be releasing, for me Mario Kart 64 and Mario Party 2 were the ones I ended up wanting.

I'm definitely interested in setting up some kind of debugger setup. If we could try running unsupported roms, figuring out where they crash and building custom config.ini files off that, it's possible we could support more roms than currently available. (Or not I'm just spitballing ideas right after waking up)

Another tip: If you started messing with files in the meta folder, you could change the game name and icon and etc so it actually shows as your game in loadiine. Unnecessary for the most part, but I was glad to have all my games show up as the proper title ;) I also gave my injections custom TitleIDs that other games wouldn't be using so there wouldn't be any conflicts down the line (Like INJ101, INJ201, etc)

Anyways sorry for the long ramble post, hopefully there's something helpful in there

This did the trick! :D Thanks for sharing this info, it's pretty interesting.
Just a quick and probably pretty naive thought: If the base doesn't matter, couldn't we use it as starting point for a standalone N64 emulator on the Wii U? Basically that it loads the ROMs and corresponding .ini's on the fly?
 
Anybody knows where I can find config.ini files for games? I want to inject star wars rogue squadron and spiderman 64 but both give black screen
 
Tried to dump one of my VC files, but it wont dump, even being the Wii U connected to the client

What did go wrong?
 
I've searched for a Mario Kart 64 base without luck, is there any program that convert N64 roms to Wii U VC format like nds2wiiu?
 
I really want to have Quest 64 .. so the name really doesn't change anything? I could just use the basic ini file with the matching rom name I choose?
 
Ok I injected Quest 64 but it crashes before reaching the main menu. I guess that could only be fixed by editing the config.ini file?
 
Anyone able to confirm if Mario Party 3 works? Been seriously wanting to play this game on my Wii U but wii64 has some really messed up graphics issues.

Also, @KuraudoSutoraifu : You got OOT: MQ working? When I go ahead with this do you think you would mind sharing your config file with me?
 
Protip: The base is irrelevant, and the rom filename is irrelevant. All that matters is that you have a proper config.ini file for your rom that matches your proper filename. So for example you have MarioKart64.z64 in the rom folder? Your config.ini needs to be renamed to MarioKart64.z64.ini and placed in the config folder. ALL the other ini files in the config folder can be safely deleted since they are for other games.

I injected Donkey Kong 64 into Super Mario 64 with its official config.ini just to see if the bases were different, and if the bases weren't uniform, this absolutely would have crashed. It's interesting how many games Nintendo has made ini files for that they won't be releasing, for me Mario Kart 64 and Mario Party 2 were the ones I ended up wanting.

I'm definitely interested in setting up some kind of debugger setup. If we could try running unsupported roms, figuring out where they crash and building custom config.ini files off that, it's possible we could support more roms than currently available. (Or not I'm just spitballing ideas right after waking up)

Another tip: If you started messing with files in the meta folder, you could change the game name and icon and etc so it actually shows as your game in loadiine. Unnecessary for the most part, but I was glad to have all my games show up as the proper title ;) I also gave my injections custom TitleIDs that other games wouldn't be using so there wouldn't be any conflicts down the line (Like INJ101, INJ201, etc)

Anyways sorry for the long ramble post, hopefully there's something helpful in there
Thanks for the great info. I thought it was worth noting that the base does matter, as ninty updates their VC emu's from time to time the more recent the better (generally at least)
 
Thanks for the great info. I thought it was worth noting that the base does matter, as ninty updates their VC emu's from time to time the more recent the better (generally at least)

Oh interesting, are there any officially released games that take advantage of emulator updates yet? I haven't seen any but I also haven't been looking very hard ;)
 

Site & Scene News

Popular threads in this forum