Nintendo 64 Game Support

[Iconoclast]

I've just came up with a great idea. Instead of waiting for users to report a game they are having trouble emulating, I will post solutions to game glitches ahead of time here.

I will start out by posting files for only the games that I have already been through configuring, which will take a long time.

If there is a game that you are having problems with that I have not listed in this thread, start a thread about your issue(s).

When I mention, Project64, Direct64, N64Virtual Pad, and you're like, what does all of this mean? Go to this page to download plugins, and this page to download emulators.

If you have any questions about this thread, send me a private message.

To make navigating in this thread a little easier, I have decided to put up links to the posts in this thread for each game I fixed:

• Banjo-Kazooie
• Banjo-Tooie (Updated!)
• Bomberman 64
• GoldenEye 007
• Mario Kart 64
• Perfect Dark (Incomplete)
• Star Wars: Rogue Squadron
• Super Mario 64

[Iconoclast]

For which emulator you should use, this is just one game that most, if not all, Nintendo 64 emulators support well. Even Corn supports this game. Here's a list of emulators you could use for this game:

• Project64 is generally the best Nintendo 64 emulator, but you don't have to use it.
• 1964 let's you assign certain plugins to certain games, unlike PJ64.
• Nemu64 is ususable, but I don't think many of you will like it with some other games. It doesn't have many features.
• Mupen64 should work OK, let's you assign certain plugins, and lets you even change your RSP plugin. Usuable by Windows, Macintosh, and Linux operating systems.
• Corn hardly supports any Nintendo 64 games at all, but for those few games that it does support, it emulates them at least 4 times as fast as Project64 does! Use this emulator if your PC is slow with emulating the N64.

The best graphics plugin? I mostly recommend Direct64, which is rarely a good plugin to try on games that are already supported fine. It doesn't give you any FSAA or AF like Jabo's Direct3D and Rice's Video Plugin do, but it fixes the missing dissolve effect in Super Mario 64, and it gets rid of the crust around the coin and star indicators.

This plugin already restores the missing dissolve effect in Super Mario 64, but makes him pixilated, the pixils too large. To fix it perfectly, configure your graphics plugin, and check the check box for the "PC noise at resolution" option.

As for the best audio and input plugin, this is going to be my answer for all Nintendo 64 games, unless I specify otherwise for a certain game. For audio plugin, have prepared plugins for:

• Jabo's DirectSound: Perfectly removes sound crackling from N64 games, and it even records audio files, too! But you have to configure it everytime you want to enable/disable the speed limiter.
• Azimer's Audio WIP 2: The only other five-star graphics plugin besides Jabo's DirectSound. Use this if you can tolerate the ALMOST perfectly removed sound crackling, and if you don't like configuring Jabo's DirectSound everytime you want to change the speed limiter.
• No Sound: Use this plugin if your PC doesn't have a sound device working, or if you're deaf, to free up CPU for your system while playing a game.

As for the best input plugin, I really...don't recommend Project64's Jabo's DirectInput plugin. It doesn't let you assign the same key to multiple 'buttons', which sometimes I feel necessary to do, and is a little too basic compared to N64 Virtual Pad and N-Rage's DirectInput V2. Use either of those plugins. I prefer N64 Virtual Pad for it's simplicity.

[Iconoclast]

I can't speak for the other emulators; I don't have time to test them. YOU do, though. Project64 works just fine with this game.

Except for two things. There are core timing issues. You may notice that, if you disable the speed limiter, the video won't keep up with the sound, if you know what I mean. Project64 says it may even hang, but it's never done so for me.

The other thing is that framebuffer issue with the missing jigsaw effect. You know, when the Press Start screen comes up? The jigsaw pieces are black when they first load. There are two solutions for this:

1. If you are using Jabo's Direct3D, configure your graphics plugin, go to the Advanced tab, and check the "Copy Framebuffer to RDRAM" option. This will almost definitely slow down your emulation speed. But I've found something. In the Settings tab, give yourself some FSAA, or Full Screen Anti-Aliasing. The more FSAA you ask for, the faster your PC goes even with this option. Unfortunately, the less the Copy Framebuffer to RDRAM option fixes this issue in Banjo-Kazooie.
2. If you are using Rice's Video Plugin, open the file 'RiceVideo6.1.0.ini' in your Plugin folder. Copy and paste this text, and save changes:

{0693bfa4d1df0cbf-45}
Name=Banjo-Kazooie
FrameBufferEmulation=8
RenderToTexture=4

Problem solved.

One last thing. If you are using the No Sound audio plugin, that's the only way to fix the core timing issues when the speed limiter is off. By disabling sound, the problem is fixed. Assuming you don't want to disable sound, this problem you may have to live with.

[Iconoclast]

I recommend Rice's Video Plugin for this game. Jabo's Direct3D works just fine, but not as good. It doesn't process the Press Start background perfectly well, and there are periods of slow speed in transition between the menus.

The 1964 package comes with the files 'MSVCR71.dll', 'MSVCP71.dll', and 'BMGLib.dll', which need to be in the same directory as the EXE of your emulator to make Rice's Video Plugin usable.

Open the INI configuration file for Rice's Video Plugin. Copy this text in the file, and save it:

{b655503e52da922e-45}
Name=Mario Kart 64
NormalAlphaBlender=1
NormalColorCombiner=1

Should work perfectly, for all I know, now. Except for one thing. Another framebuffer issue. Have you noticed that, when you are racing in the Luigi's Raceway course, the bridge opening has a black rectangle on it? Normally, it's suppose to show what's on your screen. Same thing happens in the theatre screen in the Wario Stadium course.

Both Jabo's Direct3D 8 and Rice's Video Plugin can fix this problem, but neither can fix it lossless of speed. To fix it using Rice's Video Plugin, copy this additional line of text in your INI configuration file:

FrameBufferEmulation=6

But I don't recommend this. It will REALLY slow down your game, inevitably. If you really want to fix it, try using Jabo's Direct3D 8 (Copy Framebuffer to RDRAM option) to fix this problem, and see if it fixes it without losing so much speed, but either method, there will be a speed loss.

[Iconoclast]

The game is slow, and depending on your system, 1964 may emulate it faster.

Also, there is a missing sky glitch. A different plugin does the trick. Rice's Video Plugin should fix that problem. No unusual configuration necessary.

And for those of you with Radeon R200 core video cards (e.g. Radeon 8500 or 9200, not 9500+), you might notice some geometry issues in full screen mode if you have Full Screen Anti-Aliasing (FSAA) enabled. Either disable it or enable the Advanced option on Jabo's Direct3D plugin (if you still want to use that), Use Direct3D Transformation Pipeline, to fix the problem.

Yes, I know; I got that one from the Project64 GameFAQ.

[Iconoclast]

For Bomberman 64, you should use Project64 and Jabo's Direct3D 8 graphics plugin.

In this game, there are several transpareny and display issues. There are only two issues that can be fixed.

I don't know why the Project64 team didn't do this. Maybe I caught something that they didn't? Anyway, right mouse-click the game Bomberman 64, and select "Edit Game Settings." Set the Counter Factor to 1, and click OK. This fixes the sync issue in the introduction of the game.

The other thing you could fix is some of the glitchy Bomberman screens. If you configured your graphics plugin and enabled the Copy Framebuffer to RDRAM option, the following glitches would be fixed:

• Introduction screens and transitions
• Boss screen transitions
• Shrink screen transition in game credits

But this option really slows down your emulation, so unless you got a killer brilliant sytem for emulating the N64, the speed reduction is too great to be worth what it fixes.

[Iconoclast]

The game will hang depending on the cheats you are using. For this game, you can use either Project64 or Mupen64. Both work just fine with it.

Some people report that the Jabo's Direct3D v1.5.2 plugin is more stable than the v1.6 plugin PJ64 v1.6 comes with. In my experience, however, the game never hangs on me as long as I don't have any cheats enabled, so I'm not sure if this is true or whoever reported this was on crack. If this sounds considerable to you, you can get Jabo's Direct3D v1.5 plugin from the Project64 v1.5 package. You can download the package from here.

However, there is also another reason you might want to use Jabo's Direct3D v1.5.2 plugin to emulate this game. It is the only way to fix the glitchiness of the jigsaw puzzles in Jiggywiggy's challenges. While playing the game, configure your graphics plugin by applying the following settings:

• Advanced/Update less frequently
• ROM Settings/Self rendered textures

Otherwise, I don't know how to fix the issues. The game will also run slow while playing Jiggywiggy's challenges with this fix applied, so you may or may not want to just stick to using Jabo's Direct3D 8 plugin to almost fix the glitchy jigsaw pieces, but run at a good speed. Otherwise, slowing down the emulation, by using this plugin to completely fix the problem, may be used as an advantage to giving you more time to think about which piece goes where!

[Iconoclast]

For this game, you either want to use Mupen64 v0.6, or Project64 v1.7. As of the date I've submitted this, these versions have not yet been released. Now, for Project64, I think it uses what is called "low-level graphics" to emulate that game. I could be wrong, but you might be better off with playing the game with the next version of Mupen64. The current version of Mupen64 does not support it because the game loops infinitely at the Expansion Pak Enhanced screen, and unlike all other decent emulators, there's no way to disable the expansion pak in v0.5.

You may also need to use Nemu64's graphics plugin. Normally, you can only use that plugin with Nemu64. Since the emulator is discontinued, there's no new version to wait for for that emulator. Install Nemu64, and copy the file 'LemD3D8.dll' from the Plugin subfolder of Nemu64 to the Plugin subfolder of Mupen64. You will also need to copy the file GS_DLL.dll, located in the same folder as Nemu64.exe, to the directory of the EXE for Mupen64. Once you have done all this, you should be able to emulate the game in Mupen64 using Nemu64's graphics plugin.

Now, you can also just emulate the game with Nemu64's graphics plugin...by using the Nemu64 emulator, which keeps things simple. Problem is, Nemu64 does not use RSP emulation, and you will get no sound in the game. At least I don't think you will. I doubt there will be any exceptions. With Mupen64, however, you may also not get any sound, but in the case of this emulator, THAT can be fixed.

Copy the file 'RSP.dll' from the Plugin subfolder of Project64's EXE file. Paste it in the Plugin subfolder of Mupen64's EXE file. Open Mupen64. Change your RSP plugin to the plugin named "RSP emulation plugin," and click OK. Configure your RSP plugin, and set it to the Interpreter option, not the Recompiler option. Even if you did get this game working in Project64, the sound will suck bad unless you use the Interpreter core.

Sound and graphics should be optimal.

*Note: Neither of these emulator versions of Project64 1.7 nor Mupen64 0.5 have been released as of the date I have posted this, so I have not yet tested this game. I am only telling you what I know. Until then, you will have to settle with Nemu64, and you will get no sound. For information as to when Project64 1.7 may be released, go to http://www.pj64.net, and for information as to when Mupen64 will be released, go to http://www.emutalk.net.

[Iconoclast]

I don't know anything about this game, because I have never played it. But I do know that many users on this site play it, and it is essential that I find a solution for all of its issues.

Though, I have started this, because someone sent me a private message, explaining the game's issues.

Originally Posted by Y helo thar

I saw your topic on specific game fixes and wanted to give you some input on Perfect Dark, the game I've had the most trouble running. I run it in Project64 and the only troublesome thing seems to be the graphics plugin.

Jabo's Direct3D6 runs great, but for some reason completely removes all punctuation (commas, periods) from the game, something I personally find overly annoying.

Jabo's Direct3D8 has a great deal of slowdown.

Rice's runs beautifully until you try to put it into fullscreen mode, and then it has some sort of unique (and very bothersome) choppiness.

glN64 was the one working best for me after trying the above, but then at some point it began crashing the emulator with an error message concerning some exception 0xc0000005.

To my knowledge nothing displays Campsy, Night Vision Goggles, or X-ray vision, though I do know that glN64 displays the Farsight scope to a working degree.

I've toyed around with options and I don't know how to get glN64 to stop with the error message or how to get Rice's to work on full screen mode.

Since I have no experience with testing this game, it may take a long time to confirm an ultimate fix method for the issues in this game. I will post here again, after deleting this post, when I do.

[Iconoclast]

Show me the screenshots of the issues you are having with the Campsy, Night Vision goggles, and X-ray tools, because I know nothing about this game or how to get to those!

If you are having choppiness in Rice's plugin, I think you mean the emulation is slow? That seems typical; full screen mode tends to be slower. More pixels to display because of the higher resolution. So try lowering your full screen resolution, color depth down to 16-bit (if tolerable), or change your hertz.

Jabo's Direct3D 8 and 6 both have their separate disadvantages for emulating this game. I do not notice any slow speed in window mode once you get past the introduction.

According to the GameFAQ, you can also change your Counter Factor option from 2 to 1 to increase the smoothness of the game, if you have a fast PC. You may need one. Right-click the game Perfect Dark, Game Options, should be a Counter Factor option.

Again, since I don't know this game (or want to play it), it is difficult for me to test it. Screenshots of where I need to go to see this issue and that issue may help me.