Changes

{{Infobox console|title = Nintendo 64|logo = Nintendo64Console.png|developer = [[:Nintendo]]|type = [[:Category:Consoles|Home video game console]]|generation = [[File:N64Category:Fifth-Console-Set.jpggeneration video game consoles|Fifth generation]]|thumbrelease = 1996|250pxdiscontinued = 2002|The predecessor = [[Super Nintendo 64 (N64)emulators|SNES]]|successor = [[GameCube emulators|GameCube]]The |emulated = {{✓}}}}The '''[[gametech:Nintendo 64|Nintendo 64]]''' is is a 64-bit, 5th fifth-generation console released by Nintendo in on September 29, 1996 for {{inflation|USD|199.99|1996}}. It has a NEC VR4300 CPU clocked at 93.75 MHz, 4MB of RAM (a separate add-on was later released called the "Expansion Pak" that added an additional 4MB of RAM, making a total of 8MB of RAM), and an SGI RCP GPU.

{| class="wikitable"|+PC|style="text-align:center;"

! scope="col"|Memory Controller Pak?! scope="col"|Rumble Pak?! scope="col"|Transfer Pak?! scope="col"|64DD

! scope="col"|[[Recommended emulatorsEmulators|Recommended]]|-!colspan="11"|PC|-|[[Mupen64Plus]]|Multi-platform|[https://github.com/mupen64plus/mupen64plus-core/releases {{Mupen64PlusVer}}]|{{✓}}|{{✓}}|{{✓}}|{{✓}}|{{✗}}|{{✓}}|{{✓}}|-|[[Project64]]|Windows|[https://github.com/project64/project64/releases {{Project64Ver}}]|{{✓}}|{{✓}}|{{✓}}|{{✓}}|{{✓}}|{{✗}}|{{✓}}|-|[[CEN64]]|Windows, Linux, macOS|[https://github.com/tj90241/cen64 Git]|{{✓}}|{{✓}}|{{✓}}|{{✓}}|{{✓}}|{{✗}}|{{✗}}|-|[[1964]]|Windows|[http://www.emulation64.com/files/getfile/936/ 1.1] (Official)<br />[http://files.emulation64.fr/Emulateurs/EMU_1964_146.zip 1.2 r146] (Unofficial SVN)|{{✗}}|{{✓}}|{{✓}}|{{✓}}|{{✗}}|{{✗}}|{{✗}}

|style="text-align[https://web.archive.org/web/20160828165435/http:center;"//forums.daedalusx64.com/ Daedalus]|[[Mupen64Plus]]Windows|style="text[http://www.dcemu.co.uk/vbulletin/threads/599734-Daedalusx64-for-Windows-OSX-Linux-Updated-align:center;"|Multiv1-platform|style1?p="text2148637718 1.1] -align:center;"|[https://bitbucketgithub.orgcom/ecsvDaedalusX64/mupen64plus-mxe-daily/overview SVNdaedalus Git]|style="text-align:center;"{{✗}}|{{✓}}|style="text-align:center;"|{{✓}}|style="text-align:center;"|✓{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|✓{{✗}}|style="text-align:center;"|✓{{✗}}

|style="text-align:center;"|[[Project64Sixtyforce]]|style="text-align:center;"|WindowsmacOS|style="text-align:center;"|[http://www.pj64-emusixtyforce.com/downloadsdownload/project64/binaries/ 21.0.24]|style="text-align:center;"|{{✓}}|style="text-align:center;"|{{✓}}|style="text-align:center;"|{{✓}}|style="text-align:center;"{{✗}}|✓{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|✓{{✗}}

|style="text-align:center;"|[[CEN64UltraHLE]]|style="text-align:center;"|Windows, Linux|style="text-align[https:center;"|[//web.archive.org/web/20070312015944/http://gitwww.cen64emuunlim.com/?p=cen64UltraHLE/ultrahle.zip 1.git;a=summary Git0]|style="text-align:center;"{{✗}}|✓{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}

|style="text-align:center;"|[http://1964js.com 1964[MAME]]|style="textMulti-align:center;"|Windowsplatform|style="text-align:center;"|[http://1964jswww.mamedev.com/blogorg/downloadrelease.html 1.1{{MAMEVer}}] (official)<br />[http://code.google.com/p/emu-1964/ 1.2 r146] (SVN)|style="text-align:center;"{{✓}}|{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|✗{{✓}}|style="text-align:center;"|{{✗}}

|style="text-align:center;"|[http://forums.daedalusx64.com Daedalus[Ryu64]]|style="text-align:center;"|Windows, Linux, macOS|style="text-align:center;"|[httphttps://forums.daedalusx64github.com/viewtopic.php?f=38&t=4187 1.1Ryu64Emulator/Ryu64 Git]|style="text-align:center;"{{✗}}|✓{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}

|style="text-align:center;"|[[Sixtyforce]]R64Emu|style="text-align:center;"|OS XWindows, Linux, macOS|style="text-align[https:center;"|1//github.0com/rasky/r64emu Git]|style="text-align:center;"|{{✓}}|style="text-align:center;"{{✗}}|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}

|style!colspan="text11"|Mobile|-align:center;"|[[UltraHLEMupen64Plus]]FZ|style="text-align:center;"[[Android emulators|WindowsAndroid]]|style[https://play.google.com/store/apps/details?id="text-align:center;"|1org.mupen64plusae.v3.fzurita 3.0.0208 (beta)]|style="text-align:center;"|✗{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}|{{✓}}{| class="wikitable"|+Mobile

! scope="col"|Name[[Mupen64Plus]]-pandora|Pandora! scope="col"|Operating System[https://pyra-handheld.com/boards/threads/mupen64plus-2-2.72661/ Build 20] (sv2.2)! scope="col"|Latest Version{{✓}}! scope="col"|Active{{✓}}! scope="col"|Memory Pak?! scope="col"|Rumble Pak?! scope="col"|Transfer Pak?{{✗}}! scope="col"|[[libretro|Libretro Core]]{{✗}}! scope="col"|[[Recommended emulators|Recommended]]{{✓}}

|style="text-align:center;"MegaN64<br/><small>(Mupen64+ based)</small>|[[Mupen64PlusAndroid emulators|Mupen64+Android]] AE|style="text-align[https:center;"|Android|style//play.google.com/store/apps/details?id="text-align:center;"|2com.aspieapps.free.4emulator 7.40]|style="text-align:center;"|{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|✓{{✗}}|{{✗}} {| class="wikitable"|+Consoles

! scopecolspan="col11"|Name! scope="col"|Operating System(s)! scope="col"|Latest Version! scope="col"|Active! scope="col"|Memory Pak?! scope="col"|Rumble Pak?! scope="col"|Transfer Pak?! scope="col"|[[libretro|Libretro Core]]! scope="col"|[[Recommended emulators|Recommended]]Consoles

|style="text-align:center;"|[[Virtual Console]]|style="text-align:center;"|[[Wii emulators|Wii]], [[Wii U emulators|Wii U]]|style="text-align:center;"|-N/A|style="text-align:center;"|{{✓}}|style="text-align:center;"{{✗}}|{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✓}}

|style="text-align:center;"|[http://www.gc-forever.com/forums/viewtopic.php?f=9&t=842 Not64]|style="text-align:center;"|[[Wii emulators|Wii]], [[GamecubeGameCube_emulators|GameCube]]|style="text-align[https:center;"//github.com/Extrems/Not64/releases/latest 20171009]|20130408{{✗}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|?{{✓}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✓}}

|style="text-align:center;"|[httphttps://code.google.com/p/mupen64gc / Wii64]|style="text-align:center;"|[[Wii emulators|Wii]], [[GamecubeGameCube_emulators|GameCube]]|style="text-align[https:center;"|//code.google.com/archive/p/mupen64gc/downloads 1.1 beta]|style="text-align:center;"|{{✗}}|style="text-align:center;"{{✓}}|?{{✓}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}

|style="text-align:center;"|[httphttps://forums.daedalusx64github.com /DaedalusX64/daedalus/releases/ Daedalus]|style="text-align:center;"|[[PlayStation Portable emulators|PlayStation Portable]]|style="text-align:center;"|[httphttps://www.emucrgithub.com/searchDaedalusX64/labeldaedalus/DaedalusX64 SVNreleases 1.1.7]|style="text-align:center;"{{✗}}|?{{✓}}|style="text-align:center;"|?{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}|style="text-align:center;"|{{✗}}

===Comparisons===Although many Nintendo 64 emulators have been made and many games can be run between them, complete compatibility and/or accuracy still leaves a bit to be desired. For half a decade, Mupen64Plus and Project64 have vied for the most playable emulator, and which has been more compatible has depended on when and in what configuration each emulator has been tested. Both emulators default to lackluster plugins, but, as of August 2017, both emulators have roughly equal graphical accuracy when running with GLideN64. * [[Mupen64Plus]] is an open-source, multi-platform, plugin-based emulator based on Hacktarux's Mupen64. As of [https://github.com/mupen64plus/mupen64plus-core/pull/336 July 2017], the codebase has reached compatibility parity with Project64, when both emulators are run with GLideN64. Mupen64Plus lacks a native GUI, instead of being run either from the command line or by dragging and dropping ROMs onto the executable and editing the config with a text editor such as Notepad++. Mupen64Plus has also been ported to a number of different platforms. [[BizHawk]] and [[OpenEmu]] use shallow forks of Mupen64Plus and its plugins for their N64 emulation. :* Wii64 and Not64 are both based on Mupen64, with Not64 being a fork of Wii64. Not64 claims to be better optimized as well as having higher compatibility and more frequent updates. N64 emulation on Wii is not very good, and it is recommended to stick with the Virtual Console N64 releases whenever possible.

* [[Mupen64PlusProject64]]is an open-source emulator for Windows. Its official release builds are more up-to-date than Mupen64Plus', and the current version, based on Hacktarux's Mupen642.3.2, is currently roughly as accurate as the most reliable N64 emulatordevelopment versions of Mupen64Plus when both are played with recommended plugins. It lacks has a native GUI, instead being run by dragging more user-friendly interface than the Mupen64Plus attempts and dropping ROMs supports more features such as overclocking and editing Transfer Pak emulation. However, it doesn't come with GLideN64 out-of-the config with Notepad++. There are third-party GUIs made for itbox, but these often suffer from their own issues. Mupen64Plus is actively developed and has been ported to a number of different platforms. The [[RetroArch]] core of this emulator is heavily modified the default video and may experience discrepancies or issues that wouldnaudio plugins aren't occur using even the standalone version of itbest in the box. The core It presently remains confined to Windows, though work is constantly being worked on underway to port it to Android and has features not present Linux. For the most part, it works well in mainline alongside RetroArch's general features, including Project64-style overclocking for faster framerates and 3-point texture filtering. [[BizHawkWine]] also uses , but, if you're on a port of different platform, use Mupen64Plusinstead.

* [[Project64RetroArch]] 's Nintendo 64 libretro core is still a decent choice for emulating many of the popular games, seeing various work done based on it in recent yearsMupen64Plus and its plugins but with heavy modifications. It is capable of using a wide variety of pluginsintroduces many features and optimizations not present in mainline alongside RetroArch's general features, including Project64-style overclocking for faster framerates, 3-point texture filtering, superior A/V sync and latency, and has a relatively usereven an exclusive LLE Vulkan renderer based on Angrylion's pixel-friendly interface. Howeverperfect plugin, making it remains confined a better alternative to Windowsthe standalone version in some cases. Version 2Its developers have expressed intentions to eventually rewrite the core and brand it as its own emulator, called paraLLEl.2 That new paraLLEl core has various fixes over version 1a special "[https://www.6youtube.1 and is overall more accuratecom/watch?v=mzR93F9gPdc Super VI Mode]" option which, if used, can make the visuals of N64 games look less blurry with fairly mitigated jaggies even outclassing Mupen64Plus in some instancesat their native resolutions. HoweverAlthough, audio playback is worse due to lag and crackling. It it may be handy to keep need a copy of version 1[https://www.6youtube.1 alongside it for this reason. Whatever you do, '''DO NOT USE THE OFFICIAL INSTALLER FOR THE LATEST VERSION OF PROJECT64.''' Doing so will prompt you to install various programs, some of which are malwarecom/watch?v=z7_D_D419S0 powerful GPU].

* [[CEN64]] is an up-and-coming emulator that aims for cycle accuracywhile, while at the same time , aiming to eventually be usable on modern PC hardware. It currently lacks sound many features and has a whole host of other featuresspotty compatibility, and its compatibility is still very spotty but it is 's gradually improving. Despite this, it is able to play many of It can already emulate some well-known edge cases such as the system's popular games, albeit slowlypicture recognition in Pokemon Snap.

* [[1964]], along with its various versions and forks, was once a decent, speedy open-source alternative to Project64 and Mupen64, though it usually lagged behind the two in compatibilitycompatibilities wise. Nowadays, it has completely fallen off the radar, as development has stopped, is Windows-only, and there is no longer a central code repo to speak of. There is little reason to use it nowadays outside of historical purposes, very specific edge cases, or if your device is too slow to run Mupen64Plus or Project64.

* Daedalus is an N64 Nintendo 64 emulator for the PSP, which has been ported to Windows, but results are even more hit-and-miss than on other emulators due to being made for PSP first and foremost. On PSP, most games are unplayable, but there's a [http://forumsdaedalusx64.daedalusx64wikia.com/compat.php wiki/DaedalusX64_Compatibility_List small amount of them that work really well] with the right settings (Quest 64, for example).

* [[Sixtyforce]] is MacmacOS-only, closed-source, and asks you to pay for full access to its features. It was once one of the only choices for Mac users (, particularly those with older Macs, since it's the only emulator with a <abbr title="Power PC">PPC </abbr> [[Dynamic recompilation|dynarec]]), but , with the switch to x86 and Mupen64Plus improving beyond its peersbeing ported to macOS, it has now become irrelevant.

* Wii64 and Not64 are both based [[UltraHLE]] marked a milestone in Nintendo 64 emulation, in that it was the first to play some popular N64 titles at full speed on Mupen64hardware made at the time of its release through [[High/Low level emulation|high-level emulation]]; it isn't without its drawbacks though - pressure from users, combined with Not64 legal threats from Nintendo, forced them to discontinue development. Besides being a fork of Wii64. Not64 claims to be better optimizedfor historical value, as well as having higher compatibility and more frequent updates. N64 emulation on Wii is there's not very good, and it is recommended much to expect from this emulator anyway due to stick with the Virtual Console N64 releases whenever possiblecompatibility issues.

* [[UltraHLERyu64]] marked is a milestone in Nintendo 64 emulation, emulator made in C#. The 'Ryu' word is named after the "RyuJIT" used in that both Visual Basic & C#. But it was might have been inspired by the first to play some popular N64 titles lead author's sole (so far) [https://github.com/Ryujinx/Ryujinx/commits?author=Dudejoe870 commit] at full speed on hardware made at the time of its release through Switch emulator, [[High/Low level emulation|high-level emulationRyujinx]]; it isn't without its drawbacks though - pressure from users combined with legal threats from Nintendo forced them to discontinue developments Git repository and his depreciated [https://github.com/Dudejoe870/RyujinxAutoUpdate Ryujinx Auto Updater] tool. Besides "86RYU", a x86 JIT compiler, is being for historical value and for users with toasters, there's not much to expect from developed alongside this emulator anyway due to compatibility issuestoo.

{{Main|Recommended N64 plugins}} Emulation for the N64 is not at the point where many may have expected would expect it to be by now. The system is extremely complex compared to its contemporary consoles and confounded with . With almost no documentation being available to emulator developers, leading to it being is difficult to create an emulator with a high degree of compatibility with games. Many games require specific plugin set ups setups with specific emulators to be played decently.

One of For this reason, most developers have instead opted to approximate the biggest hurdles RDP's functions using high-level emulation (HLE) through various APIs such as Direct3D, OpenGL, and even Glide. While this results in the road much more reasonable system requirements for emulation, along with prettier, higher resolution graphics, this method can be hit and miss. It often requiring per-game tweaks and settings to prevent graphical glitches on many games. Some games implemented custom graphics microcode which had yet to proper N64 emulation has be reverse-engineered. Although many or even all of them have already been accurately emulating the N64implemented in HLE mode in 2016-2018 with dedicated work from GLideN64's graphics hardwarelead programmer, known as the Reality Display Processorgonetz, itself a part and one or two assistants.<ref name="gliden64_blog-1">{{cite web|url=https://gliden64.blogspot.com/2017/|title=Public Release 3.0|publisher=Blogspot|accessdate=2018-06-17|date=2017-12-29}}</ref><ref name="ZSortBOSS">{{cite web|url=https://github.com/gonetz/GLideN64/issues/1685#issuecomment-364436534|title=Initial implementation of the N64's Reality CoBOSS ZSort ucode (WDC, Stunt Racer)|publisher=GitHub|accessdate=2018-06-17|date=2018-02-Processor10}}</ref> For example, [https://youtu. The N64be/HfCOnmRHI0o Factor 5]'s RDP was the first real 3D accelerator GPU on consoles. In factgames do now work, it was the most powerful consumerspecifically when using GLideN64 plugin's high-grade GPU in the world at the time it came outlevel graphics mode.<ref name="Indiegogo">{{cite web|url=https://www.indiegogo. It is very hard to emulate com/projects/indiana-j-infernal-machine-high-level-emulation#/updates/all |title="Indiana J. & Infernal Machine" HLE|publisher=Indiegogo|accessdate=2018-06-17|date=2018-05-17}}</ref><ref name="gliden64_blog-2">{{cite web|url=https://gliden64.blogspot.com/2018/05/hle-implementation-of its functions accurately due to the lack -microcodes-for.html|title=HLE implementation of publicly available documentation microcodes for "Indiana Jones" and "Battle for emulator developersNaboo" completed. Many |publisher=Blogspot|accessdate=2018-06-17|date=2018-05-26}}</ref> Other games may have issues with such RDP functions have to be reproduced in software for quirks as frame buffer/depth buffer access (issues with how the frame buffer is used as well as performance issues), VI emulation as well as issues with how combiner/blender modes are emulated (such as noise issues and combiner accuracy, which takes a lot of power).

For this reasonLow-level emulation can be handled in two ways, complete low-level software emulation or a hybrid approach of LLE RDP emulation, most developers have instead opted which involves using graphics APIs to approximate simulate the RDP's functions while using highlow-level RSP emulation to emulate the graphics microcode. Low level software emulation (HLE) through various APIs of the RDP involves replicating all RDP functionality in software, which allows for very high accuracy but can suffer from major performance issues unless optimizations such as Direct3D, OpenGL, vectorization and even Glidemulti-threading are performed. While this results in much more reasonable system requirements Hybrid LLE emulation can allow for performance enhancement over low level software RDP emulation along with prettier, higher resolution graphics, this method but can be hit and misssuffer from various problems due to things such as replicating the N64's numerous blending/combine modes, often requiring per-game tweaks emulating frame buffer access and settings replicating how polygons are rasterized to prevent graphical glitches on many games. Some games that implemented custom microcode the screen (which has yet due to be reverse-engineeredhow the RDP renders primitives on a low level) such as Factor 5's games do not work no matter what using high-level graphics plugins.

It should also be noted that even though most games "work" through the HLE method, it is not an accurate representation of what the N64 hardware's video output actually looked like, but rather a rough approximation by PC graphics hardware. Your mileage may vary on whether this is a good thing or not, given the N64's often blurry, low-res output.

Majora's mask accurate.png|Majora's Mask, with low-level graphics (using SoftGraphic)Project64 2013-07-26 14-20-17-55.png|Majora's Mask, with high-level graphics (using Jabo's Direct3D)

===[[Texture filtering]]===The N64 was the first console to feature texture filtering of any kind. However, unlike PC graphics hardware and every console after the N64, its implementation of bilinear texture filtering was unique , in that , in order to reduce strain on the system, it only used three samples as opposed to four, resulting in slightly jagged textures. Instead of faithfully applying this "imperfect" version of bilinear, HLE plugins instead apply conventional bilinear filtering, interpolating straight from the source texture up to the output resolution, much like on PC games. While technically this method of bilinear filtering is superior to the N64's, it can also result in textures that look even blurrier than on real hardware.

Another issue lies with the appliance of texture filtering per quad on static images, text, and sprites. Because each quad is filtered separately, this can cause some visual inconsistencies. Text and UI elements often look as though their edges cut off abruptly, and static images , such as pre-rendered backgrounds or menu screens , may look as though they are separated into squares. Some plugins allow the user to turn off texture filtering to remedy this, but , unfortunately , this also applies to textures in the game world, exposing their oftentimes-low resolutions.

===64DD EmulationVoice Recognition Unit emulation===The 64DD Voice Recognition Unit (VRU) is an abbreviation for "64 Disk Drive") was a peripheral which allowed a proprietary disk format to be accessory used with the N64primarily by ''Hey You, Pikachu''. These disks had more space at a cheaper manufacturing cost. The peripheral was a commercial failure and was never released outside of Japan. Recently No emulator or input plugin supports this, although there has been is an on-going effort to emulate get it working.<ref name="emutalk">{{cite web|url=http://www.emutalk.net/threads/55279|title=Hey You! Pikachu - Possible HLE Implementation|publisher=emutalk|accessdate=2018-06-17|date=2014-10-27, Last edit: 2016-04-04}}</ref>===''Densha De Go!'' Controller===Also available for the 64DD, and now [[MESSPlayStation emulators|MESSPlayStation]] can run several commercial 64DD games as part of its N64 emulator. This , ''Densha De Go! 64'' is being ported to a Japan-only train simulator released by [[CEN64Wikipedia:Taito|CEN64Taito]] that is compatible with an optional special controller that plugs into the help of [player 3 port.<ref name="ArcadeUSA">{{cite web|url=https://www.youtube.com/watch?v=cCcPAGhcnck|title=Densha De Go! Nintendo 64 Controller!|publisher=YouTube|accessdate=2018-06-17|date=2017-01-20}}</ref> No emulator supports it. ===Pokémon Snap Station===There was a special kiosk designed to promote ''Pokémon Snap'' called the ''Pokémon Snap Station'', which is also compatible with the North American ''Pokémon Stadium'' with its gallery mode. It is just a Nintendo 64 with special hardware designed for the station.<ref name="Sixty Formula">{{cite web|url=https://www.youtube.com/watch?v=AMbjvGvPkV4|title=The Pokemon Snap Station|publisher=YouTube|accessdate=2018-06-17|date=2016-05-21}}</ref><ref name="MetalJesusRocks">{{cite web|url=https://twitterwww.youtube.com/LuigiBlood LuigiBloodwatch?v=5_UGpRN6AnM&t=3m35s|title=VIDEO GAME KIOSKS - Extreme Game Collecting!|publisher=YouTube|accessdate=2018-06-17|date=2016-05-25}}</ref> Although the special cartridge boots in emulators compatible with the regular version, the printing functions are inaccessible due to no emulation of the printer for the player 4 slot, credit system, or the special board to switch between the regular and special cartridges.]

===iQue EmulationTransfer Pak emulation===Before A few games use the GBATransfer Pak such as ''Mario Golf'', ''Mario Tennis'', ''Mario Artist: Paint Studio'', DS and 3DS, Nintendo released a modified version of their Nintendo 64 system for the Chinese market with 14 ''Pokémon Stadium'' games localized to Chinese. Mostly, including Sin and Punishmentthis can be done with N-Gage's input plugin, but a unique revison couple of Ocarina of Time (a Majora Mask port was cancelled though) and Mario 64 among others. things aren't emulated:

Unlike *Taking pictures with the Chinese releases of their more recent systems and their games, no dumps Japanese ''Game Boy Camera'' (called ''Pocket Camera'') while in the same format as regular N64 releases exist yet for the N64 iQue releases, and no emulation support exist for them at all. The Chinese rom-hacking scene is very active though, and have translated the Japanese regular N64 releases for many of these to their language already, which explain some of the Chinese roms floating for thoseTransfer Pak mode playing ''Mario Artist: Paint Studio'' displays static.

===Aleck 64 Arcade Emulation64DD emulation===Nintendo collaborated with SETA to release The 64DD (an arcade system based on their Nintendo abbreviation for "64 system (kind of like their Playchoice-10 for Disk Drive") was a peripheral which allowed a proprietary disk format to be used with the NES, Super System arcade hardware for SNES, and later Triforce for GC and later WiiU)N64. These disks had more space at a cheaper manufacturing cost. The Nintendo 64-variant with more RAM, the Aleck 64, failed to catch on peripheral was a commercial failure and bombed. It was never released outside of Japan. Internal evidence suggests that, much like the GBA e-Reader, it wasn't even though one N64 port made itintended for a European release.

Expansion disks are region-coded to either Japan or US (obviously unused) and won't work with N64 games from the wrong region. Only F-Zero X has full support for this feature, but dummied-out expansion data in Ocarina of Time and Mario Party 2 (JP/PAL) exist as well. The special AV-In cartridge (NUS-028) that ''Mario Artist: Talent Studio'' can use doesn't work because it requires an RCA cable signal. Recently, there has been an effort to emulate the 64DD, and now [[Project64]] and [[MAME]] can run several commercial 64DD games as part of its N64 emulator. This is being ported to [[CEN64]] with the help of [https://twitter.com/LuigiBlood LuigiBlood]. {| class="wikitable" style="text-align:center;"|+PC|-! scope="col"|Name! scope="col"|Operating System(s)! scope="col"|Latest Version! scope="col"|Active! scope="col"|64DD Emulation! scope="col"|N64 Mouse! scope="col"|[[Recommended Emulators|Recommended]]|-|[[Project64]]|Windows|[https://github.com/project64/project64 2.3.2]|{{✓}}|Mid|{{✓}}|{{✓}}|-|[[CEN64]]|Windows, Linux, macOS|[https://github.com/tj90241/cen64 Git]|{{✓}}|Mid|{{✓}}|{{✗}}|-|[[MAME]]|Multi-platform|[http://www.mamedev.org/release.html {{MAMEVer}}]|{{✓}}|Mid|{{✗}}|{{✗}}|} * Project64's latest versions emulate the N64 mouse and can load Zoinkity's hacked 64DD cartridge conversions at playable speeds. You'll need to set every game to have 8MB of Memory by default manually. Games do not save, some need "32-bit engine" to be unchecked (like Talent Studio), and some (like Polygon Studio to fix models and Paint Studio to fix stamps) need the Angrylion GFX plugin rather than GlideN64, which does the job for the rest.**The 64DD hardware started to be emulated around 2.3's release with the help of [https://github.com/LuigiBlood LuigiBlood]. Saving works but in the form of NDR files. NDR files are copied versions of NDD images with save data included as to not write to the clean unaltered images. In order to play 64DD games in their original forms, 8MB of memory is still needed because the real hardware needed the Expansion Pak upgrade. The IPL is also needed. * MAME includes early basic 64DD emulation as well but is much slower. Disk images need to be in head/track format. See [https://github.com/Happy-yappH/ddconvert.git here] for more information. It does not currently support disk swapping or saving disk to files. Writes only update the copy in memory, and, once the MAME process ends, the changes are lost. Current usage: <code>mame n64dd -quickload disk -cart cart -nodrc</code> (both disk and cart are optional) * CEN64, like Project64, had 64DD emulation ported to it from MAME. However, it focuses on accuracy and plays much slower than other emulators, aside for the 64DD emulation itself is imperfect. ===iQue Player emulation===Before the GBA, DS, and 3DS, Nintendo released a modified version of their Nintendo 64 system for the Chinese market, which was called the iQue Player, through their not-quite-subsidiary iQue. Fourteen games were translated into Simplified Chinese, including Sin and Punishment, Ocarina of Time (the Majora's Mask port was canceled), Super Mario 64, and others. Unlike the Chinese releases of their more recent systems and their games, iQue Player releases are regular N64 roms wrapped with several layers of encryption, as well as a ticket and signature system like that on Wii, DSi, 3DS, Wii U and Switch. The Chinese ROM-hacking scene is very active though and has translated the Japanese regular N64 releases for many of these to their language already, which explain some of the Chinese ROMs floating for those. However, recently, almost all pieces of iQue Player software were decrypted to regular .z64 ROM format. Several of the Chinese game localizations already run on N64 emulators, but as some hardware features of the iQue Player are not yet supported, some games, as well as the system menu and features in games such as saving, do not work yet. ===Aleck 64 arcade emulation===Nintendo collaborated with SETA to release an arcade system based on their Nintendo 64 system (kind of like their PlayChoice-10 for the NES, Super System arcade hardware for SNES, and later Triforce for GCN and Wii U). The Nintendo 64-variant with more RAM, the Aleck 64, failed to catch on and bombed. It was never released outside Japan, even though one N64 port made it. The Aleck 64 roms ROMs were dumped, and Zoinkity is working on converting them to regular N64 roms ROMs (with controls remapped to N64 controller buttons). They generally require an 8MB Expansion Pak (to run at all) and 4K EEPROM (to save settings and scores). The ones covered by these patches are:

The already available [httpshttp://www.assemblergames.com/forumsl/threads/showthread.php?55041-Aleck64aleck64-on-Retailretail-Consolesconsoles-PoC poc.55041/ patches] to convert arcade rom ROM dumps to regular N64 rom ROM format can be found [http://micro-64.com/database/aleck64.shtml here].

* Hi Pai Paradise* Magical Tetris Challenge* Mayjinsen 3 / Meijin-Sen2

Some N64 games are emulated better as well on a Virtual Console game through Dolphin than on an actual N64 emulator. Mario Tennis, Kirby 64, and Paper Mario are all examples of this. The system requirements are much higher, but it's doable for many games. The following games are on the N64 Virtual Console for Wii: 

==References==<references/>  {{Nintendo}} [[Category: Consoles]][[Category:Fifth-generation video game consoles]][[Category:Nintendo consoles]][[Category:Nintendo 64 emulators|*]]