Changes

'''Cemu''' is a closed-source, Windows-only [[Wii U emulators|Wii U emulator]]for Windows. Currently, the GamePad, Classic, and Pro controllers System requirements are emulated. It also requires a pretty high-end PC if you want games to run games at full speed, although there are numerous bugs that can crash games due to unimplemented features. It emulates the GamePad, Classic, and Pro controllers. A compatibility list can be found [http://docs.google.com/spreadsheets/d/19WV2YQvS2PkiHnQTlYP7cE2eHOPl06Rx4tCvfud_Hpw/edit?pref=2&pli=1#gid=0 here].

The latest version of Cemu is restricted Before updates are publicly released, they're accessible to backers over at first to project donors for a week.<ref>[https://www.patreon.com/cemu</ref> It's then followed by a free release with further improvementstheir Patreon].

* [http://cemu.info/index.html#download Latest free public release]

You will also need enough storage for the Wii U games. Running Cemu on WINE has been reported to work just as well as Windows.===Minimum===* OS: Windows 7 (64-bit) or above* GPUGraphics Card: Supports at least OpenGL 4.0 or above, Intel iGPUs are not recommended* RAMMemory: 4 GB minimum, ===Recommended===* Windows 10 (64-bit)* Graphics Card: Supports OpenGL 4.0 or newer (avoid integrated graphics)* Memory: 6 GB or more recommended

If you==Setting up=====Physical dumps===Cemu're on Linux, CEMU s directory needs proper values in the "keys.txt" file. The example line can be run using WINE with unexpectedly good results. Compared to performance on Windows, it runs in full speed with no noticeable input lag for instancedeleted.

==Playing Games=====Physical Dumps===You'll first need yours to fill in have many lines like this; one for the "keysWii U Common Key, and one line each for Game Keys.txt" file in CemuNote that for games that use the Loadiine format, you don's directory. It has a sample line with a bogus key and t need a commentGame Key at all, which you may as well deleteonly the latest version of Cemu.

Your file must have many lines like thisFormats supported are uncompressed, one for the Wii U Common Key (D7B00402659BA2ABD2CB0DB27FA2B656)WUD compressed, and one line for the Game Key of each game. Sharing these keys isn't exactly safe legally, but ROM sites at least share [http://pastebin.com/GWApZVLa the Game ones]. Note that for games using the Loadiine format, you won't need a Game Key at all, but those will need Cemu versions from 1.4.0 onwardISOs.

Your ISO must be either uncompressed, compressed using WUD format, or in Loadiine format (only possible for versions 1.4.0 onward) to boot in Cemu. Here's a [http://docs.google.com/spreadsheets/d/19WV2YQvS2PkiHnQTlYP7cE2eHOPl06Rx4tCvfud_Hpw/edit?pref=2&pli=1#gid=0 compatibility list]. ===Digital CopiesAmiibo support===CEMU supports either physical games dumps in WUD, or compressed WUX format, as well as game can read binary dumps converted to the Loadiine format. Loadiine games come as multiple directories with game files and a rpx file.  Nintendo's servers are poorly secured due to a huge oversight when designing Wii U/3DS software protection. As such, with tickets proving you bought the game (but which you can get through less legit ways), there are downloader utilities like NUSGrabber, FunKiiU, UWizard, or jnus among others, and decryption tools like UWizard and CDecrypt, to obtain a functional copy.* Download an NUS downloader such as [http://application.wiiuusbhelper.com/Updater.exe WiiU USB Helper].* Paste this URL into WiiU USB helper when prompted for the titlekey database. - https://wiiu.titlekeys.com/* Select the game you want to download, click get it and then download games.* This will download the files for the game you chose (the same as the .tik's title). May I suggest that you choose your own region where possible, so the download is quicker (from your regional servers).* Now we need to convert the game into Loadiine format so that you can load it in Cemu. Simply right click your newly downloaded game, then click "Prepare for Emulation".* Load the .rpx file from [Your gamelocation]/code/[yourgame].rpx with cemu. ===Updates and DLC===Prior to 1.7.3, only updates were supported though pasting update files on the main game's folders (keeping in mind the main game is in Loadiine format) and overwriting any files. DLC wouldn't work at all through this method, though with some specific games there were workarounds and some could play DLC tracks in Mario Kart 8 through swapping of specific files. From 1.7.3 onwards, proper support for DLC and updates was included in CEMU. Use the same process as above to download updates. Once decrypted, simply copy and paste these over the original game's files. To install updates and DLC on Cemu (1.7.3+): * Run the game at least once.* Check Cemu's log.txt file and look for a line that says "Mounting local storage (AOC): .\mlc01\usr\title\NUMBERS\NUMBERS\aoc\"* Add (create) folders with the same name as the above (substituting the "NUMBERS" bit with the actual numbers) in your "CEMUFOLDER/mlc01/usr/title" folder.* Add any updates (which must be added first) you want to the "CEMUFOLDER/mlc01/usr/title/NUMBERS/NUMBERS/" folder.* Create a folder named "aoc" and put the DLC files into there. The "code", "content", and "meta" folders of the actual game itself also go in the "aoc" folder. ===Amiibo Support===Amiibo are hard-to-find figurines unlocking various on-disc content in select 3DS and Wii U games. They use the NFC technology. Nintendo Amiibo data is distributed online as NFC tags (.bin files). Here's a recent complete set of the official ones ([https://mega.nz/#F!Z4UWVIYS!HsOvjW4tUMHE40ECIG7sMQ March 2017]) but there's also unofficial spoofed packs on various other sites. Recent versions of CEMU include Amiibo support. Simply go by going to NFC / -> Scan NFC Tag from file, and load the relevant .bin file. Keep in mind Amiboo support in CEMU Support is incomplete right now , and not all figurines are may be compatible yet - though incompatibilities may be caused by due to potentially bad Amiboo dumps as wellreads.

As of 1.7.3d, the Wii U GamePad and the Wii U Classic Controller are emulated, but the The Wiimote still isn't emulated yet. You , but you can set have up to 8 GamePads set in the menu if you want.

Emulated Wii U GamePad features are as followbindings:

A menu allows for loading NFC tags from Amiibos. Cemu cannot go online or connect to a real (More details would be appreciatedor emulated)[[Nintendo 3DS emulators|3DS]].

As of now, no online features or 3DS/Wii U connectivity features are possible. ==Improving PerformanceTroubleshooting/Speeding up==

Normally, when playing a game in Cemu, a shader cache will be generated Shaders are normally cached as you playthe game. This will can cause a lot of stutter and slow the game down the first time you play that level/area/game.Luckily, Cemu allows you to transfer your shader cache, allowing you to download one from a friend (or just someone else on the internet).Reddit seems to be a good place to get these shadercaches. Simply [https://www.reddit.com/r/CEMUcaches/ go here] and search for the game you want a cache for.*Note that it is very difficult to generate a 100% complete shadercache for large games and therefore this will not definitely completely eliminate stuttering.

Transferable Cemu accepts other shader caches may cause slowdowns in some games, on some graphics cards (observed in Geforce 970s)that can be traded online. You can go to [https://www.reddit. If this is the case, delete both your transferable com/r/CEMUcaches/ /r/CEMUcaches] and precompiled caches as well as search for the ones you want.bin It's often very difficult to generate a complete cache for large games, and /toc file in your NVIDIA GLCache found in C:\Users\(You)\AppData\Roaming\NVIDIA\GLCache\(hexstring)\(hexstring). In this case, you will have to generate your own shaders.*This may get fixed after 1.7not completely eliminate stuttering.0, who knows?

Changing your NVidia [[File:Shadercachestuff.png|thumb|Some settings in the Nvidia control panel settings to look like this might help with shadercache slowdown issues:.]]

[[File:ShadercachestuffSome games' transferable caches may cause slowdowns on some graphics cards like the GeForce GTX 970. If this is the case, you will have to generate your own shaders and delete the ones you downloaded. In the case of the GeForce, also consider deleting the .bin and /toc file in your GLCache at <code>%APPDATA%\NVIDIA\GLCache\(hexstring)\(hexstring)</code>.png]]

===Native H264 H.264 Decoder===Lots of Wii U games use high resolution MP4 videos and render them using codecs intended are often encoded for the Wii Ugames with the expectation that the hardware plays it back on-the-fly, which can get slow but because the x86 architecture is not PowerPC, this is resource-intensive for Cemu since it has to emulate, and cause display bugs on CEMUrun the PowerPC video decoder. An unofficial utility called [https://sshnuke.net/cemuhook/ CEMUhook] is a hook utility used in conjunction with CEMU from versions 1.7bypasses this by playing H.3 onward to render these cutscenes with a much faster 264 video codec native to directly from Windows. It's not officially supported thoughcodecs that are programmed for x86.

===Getting more performanceDisable Hyperthreading===Some users have reported that disabling hyperthreading improves performance in Cemu. On Windows may not be programmed well with hyperthreaded cores, turn off processor affinity for imaginary cores. This will be every other core in your processor affinityhyperthreading. To do thisdisable it, go to into the Task Manager, right click cemu.exe process in task manager, right click, set affinity and then turn off every other coreset these affinities:

==Increasing Internal ResolutionGraphics Packs==The so-called To work around emulation bugs and other problems the way [[Dolphin]] does, "Graphic Packs", '''are title-specific property sheets which defines advanced settings you might not to be confused with Texture Packs (since CEMU can't use them for that functionality yet),''' allow for upscaling the in-game graphics able to higher resolutions than change in the original, as well as other basic interface. Basic rendering options (including shadow resolution/and quality, post-processing effects like bloom, lightning lighting and godrays, custom anti-aliasing). It can affect what resolution the game is rendered as, as well as shaders, and works as a workaround for some emulation bugssuch can be applied here. You can even use them to ''reduce '' the internal resolution to enjoy a slight FPS for an increasein the framerate. Developers plan This is not to add custom texture be confused with '''Texture Packs''', which are replacement in the future (hence the name) textures; CEMU doesn't support that, but that's yet to be seen as of 1.7.6it is planned.

The "Graphic Packs " themselves come as are folders under the <code>graphicPacks </code> directory. You They can name these folders whatever you want (for example "Bayo_1080p")be named anything, which contains just a single but they should contain the "<code>rules.txt</code>" file. A more bare-bones file example of a "Graphics Pack", called "Bayo_1080p", would look like this:

<code>:: [Definition]:: titleIds = 0005000010172600,0005000010172700,000500001011b900,000500001014db00,0005000010157e00,0005000010157f00:: name = "Bayonetta 1 + 2 - 1080p":: :: [TextureRedefine]:: width = 1280:: height = 720:: overwriteWidth = 1920:: overwriteHeight = 1080 </code>

In CEMUWhenever the titleId matches the current one, Cemu will show the Graphics Pack under Options/-> Graphics Pack, . If you'll see this particular graphic pack as "Bayonetta 1+2 - 1080p". The name doesndon't matter, know what matters the most would be that the titleIds (here matching all three US/EU/JP versions of both Bayonetta 1 and 2) match that titleId of the game in question. You can get the titleIds looking at you want is, check the <code>logs.txt </code> file CEMU generates whenever it loads a new game (and which you . You can safely delete safely so it in the event that it doesn't get gets too big for a text editor to read)parse.

When you enable The overwriteWidth and overwriteHeight properties used in this graphical pack and then load example will upscale the game, it will play following this rule which is upscaling a game that runs as 1280x720 so that it runs as 1920x1080from 720p to 1080p. But if the game doesn't have all of its textures originally in that the specified resolution you specified (1280x720), they won't be upscaled and it could look messy as a result. For example, in Bayonetta 2's In this case, this problem can be is seen in some FMVsin the game. That's why some graphical packs add exclusions to This is the purpose of the TextureRedefine rule. But this here is a good starting point to create graphical packs for games that no one bothered to do, like Meme Run or Devil's Third among others.

You can (and probably should) get most See some of the community graphics packs made so far at [http://slashiee.github.io/cemu_graphic_packs/ from herethis page].

Here's some of the actual issues that directly relate to the end user experience: * Save states aren't getting implemented any time soon. A This has a lot of this has to do with the complexity of the Wii U memory layout and architecture, as well as the huge file size. As a result, the current developers are not interested in implementing them.* Frequent stuttering is often experienced when you first start a game, because CEMU is building your shader cache. One solution The emulator is to get shader caches available online for your game and use it. They also have been compatible across different versions of the emulators for quite a while. That aside, there's other issues that stem from the still unfinished and unoptimised nature of the emulator, like as noted in the lack of native H264 efficient and stable H.264 video decoding libraries , causing green screens and glitchy videos (which . This is solved worked around with Cemuhook) among other things. ===Unofficial Builds===The restricted Patreon early access builds (behind a $5 donation a month for around two builds)entirely, released one week prior but its approach to the public release, have some checks in place. Builds that weren't verified online would have some features restricted impacting performance, as well as a ban video decoding is unlikely to be taken into the original backer if the build was shared more than how it reasonably should be for personal useemulator.

One particular developer, mudlord, who disagreed with ===Piracy===There are anti-piracy measures on the choices made by the CEMU devs, proceeded to release illegal cracked versions of these Patreon early -access builds on his personal blog, ironically also used to expose people breaching licenses for other emulatorsthat are put behind the $5 tier. A Cemu piracy subreddit and discord was even started to discuss Backers putting out these builds and how to can get them. These builds' illegal nature means youbanned if they're unlikely to find them anywhere else. This however stopped with 1.7.5 with him announcing he's not interested any longer in continuing thiscaught, and when the program fails verification, it locks down some features that impact performance.

UnderstandablyUntil 1.7.5 was released, one developer from Team Cemu, mudlord, spun off the project out of creative differences with the official CEMU subreddit advises against downloading these buildsteam, dismissing them as unsafe and malware, with bans in protest he put out cracked versions of early builds on his personal blog. These were also used to expose people breaching licenses for people not heeding this "advice"other emulators. However it didn't took too long for malware authors to take advantage of this A subreddit and distribute malicious copies of the early access build according Discord server was made to user reports in the CEMU discuss Cemu piracy subreddit. So use them at your own risk.