rabbiddeity is right. Issues like that do not occur because of your PC specifications, but because of your graphics plugin or emulator.
The best plugin is a nice discussion, but I'll get to that later. For now, like Doomulation said, use BigHeads config list!
Nintendo 64 Emulation Configuration List Online
A table of the best emulators and plugins for each and every dumped N64 game.
But there is no such thing as a flawless gfx plugin. They all do things that others don't.
The best audio plugin, IMO, is Nemu64s audio plugin. The emulator, itself, is bad, but it is the only other audio plugin apart from Jabos DirectSound that lets you Record WAV sounds, Sync Game to Audio, control prebuffering, and is full of advanced options. Jabos DirectSound is usually the audio plugin you almost always want to use, half of the time. The other half of the time, you want to use one of Azimers latest audio plugins, as they have better sound emulation than Jabos DirectSound, once you subtract the Sync Game to Audio option in that plugin, which screws some games up like TWINE.
The best input plugin. Pretty goddamn easy: N-Rage"s DirectInput. In order, the best input plugins:
- N-Rage"s DirectInput 8 V2 1.82a (lets you export A64 mempak notes and use control modifiers, transfer pak usage, format mempaks and insert A64 note files, use N64 DexDrive MemPak saves, and such a big configuration plugin and so much more)
- N64 Virtual Pad (well, better than Jabo"s DirectInput, thats for damn sure.)
- Jabo"s DirectInput (One of Project64"s not-so-good default plugins, comparatively. Piece of crap won't even let you assign the same key to multiple controller buttons, which I need to do sometimes.)
As for the best graphics plugin, in general, that decision can be made. I'd have to say Rice"s Video Plugin v6.1.1 beta 10. Jabo"s Direct3D 8 and Glide64 are its top competitiors. Rice"s Video Plugin has, like, 50 configuration options in the Advanced Game Options tab, whereas Glide64 has roughly near that much and Jabo"s has only 15 or so config options. Rice"s Video Plugin has a bad screenshot log for its crappy JPEG compression and goes straight to the emulator when you log a screenshot, but seems to be such a goddamn advanced plugin. Lets you dump textures to native N64 resolution, all that configuration guess work for me to do for my choice of optimal INI configuration, seems to process graphics less "artificially" than Jabo"s Direct3D 8, which forces Accurate Texture Mapping and therefore gives a hardly noticeable 'fake' look to a few graphics in some games. Rice"s Video Plugin"s biggest weakness is the fact that it may emulate better than both Glide64 and Jabo"s for some games, but only once its configured, and there"s a lot of configuring to still be done for perfection in that INI file. Once configured, the plugin is very great in emulation. IMO, Rice has not done a perfect job of configuing the INI for the plugin. I have many disagreements.
Jabo"s Direct3D 8 and 6 are pretty damn good, as well. Jabo"s Direct3D 6 is a previous form of Direct3D 8 that should only be used for emulating some games, like Yoshi"s Story. Glide64 is powerful with the Mupen64 emulator, as it is then known for its unique ability to add support for coronas and, as already mentioned above, is impressively quick with framebuffer emulation. This is, perhaps, the top OpenGL emulation plugin out there.