Changes

{{Infoboxemulator|image logo = Cemu-Logo.png|first version = {{CemuVer}}|second active = Yes|third platform = Windows|fourth architecture = x86_64|target = [[Wii U emulators|Wii U]]|developer = Exzap|fifth website = [http://cemu.info Cemu]|sixth support = Closed source[https://www.patreon.com/cemu Patreon]}}'''Cemu''' is a closed-source, Windows-only [[Wii U emulators|Wii U emulator]]for Windows. A compatibility list can be found [http://compat.cemu.info/ here] or [http://docs. Currently, the GamePad, Classic, and Pro controllers are emulatedgoogle. It also requires a high-end PC to run games at full speed, although there are numerous bugs that can crash games due to unimplemented featurescom/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

==Playing GamesGame Formats and Files Needed==

Your file must have many lines like this, one for the Wii U Common Key (D7B00402659BA2ABD2CB0DB27FA2B656), 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 onward.

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]. Dump your discs using [https://gbatemp.net/threads/wudump-dump-raw-images-from-a-wiiu-game-disc.451736/ Wudump].

CEMU Cemu supports either physical games dumps in WUD, or compressed WUX format, as well as game 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 Unpack/Convert to Loadiine (Pack/Unpack - Loadiine/CIA).* Load the .rpx file from [Your gamelocation]/code/[yourgame].rpx with cemu.

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 CEMUCemu.

To install updates and DLC on Cemu (1.7.3+): * Play the game at least once * Open "log.txt" and find "TitleId of launched game" followed by a 16-digit number. Copy down that 16-digit number. * Go to "CEMUFOLDER/mlc01/usr/title" and create a folder with the first 8 digits of that 16-digit code* Inside of that folder, create a folder named with the last 8 digits. * Put in the files of the update into the folder* To apply DLC create a folder inside of the folder with your update and create a folder named "aoc" and put the DLC files into there and simply run the game. To add DLC to games:*Run the game as normal, 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 cemu\"CemuFOLDER/mlc01\etc/usr/title" folder. file*Add any updates (which must be added first) and DLC you want to this 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 live inside of the actual game itself also go in the "aoc " folder).

[[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). HereThere's a recent regularly updated 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 Cemu include Amiibo support. Simply go to NFC / Scan NFC Tag from file, and load the relevant .bin file. Keep in mind Amiboo Amiibo support in CEMU Cemu is incomplete right now and not all figurines are compatible yet - though incompatibilities may be caused by bad Amiboo Amiibo dumps as well.

As Cemu added native support for Wii Remote controllers as of 1.712.0.3d, the Wii U GamePad and the Wii U Classic Controller are  Cemu cannot connect to a real (or emulated, but the Wiimote still isn't emulated yet) [[Nintendo 3DS emulators|3DS]]. You can set up to 8 GamePads in the menu if you want ===Cemuhook===Using this is completely optional.

Emulated Wii U GamePad features are Download [http://sshnuke.net/cemuhook/ the latest version] compatible with your Cemu version, unpack it to the same directory as follow: * Touch Controls: Mouse left clickcemu.* Tilting exe and Gyro Controls: Holding the mouse right-click on dbghelp.dll, check Proprieties, Digital Signatures tab, select a signature and draggingpress Details. It's lacking ZThis should make it no longer crash at start-axis key binding at up. Make sure you also have the moment.* Switch Screens between TV latest GPU driver installed, as well as both x86 and GamePadx64 versions of the [http: "TAB" key, "Ctrl+TAB" to keep focus//www.microsoft. TV by defaultcom/en-US/download/details.* Microphone: Spoofed, a configurable key simulates blowing on the micaspx?id=53840 Microsoft Visual C++ 2015 X64 Redistributable].

A menu allows Whenever you boot Cemu now, this cemuhook tool is enabled by default and offers various additions for loading NFC tags from Amiibosbetter motion control emulation, or some graphical hacks that greatly enhance Zelda BOTW in particular. Accept to download the missing shared fonts as well to make text in some games (More details would be appreciatedSuper Mario Maker among others)display correctly.

As Enabling "GX2SetGPUFenceSkip (HACK)" enhances graphical emulation in BOTW in particular. A pre-installed Graphical Pack that comes with recent versions of nowCemuhook, no online features or 3DS/Wii U connectivity features are possible"LWZX Crash Workaround", as well as the "GX2DrawDone()" option under Experimental, should help with some general crashes specific to BOTW.

==Improving Performance=Shader Caches===When your game is loaded, check for its ID on the titlebar in front of "SaveDir:" and note it down. The directory where transferable shader caches are stored is <code>.\Cemu\shaderCache\transferable</code>. They're generated the first time you play through a game and at that time cause noticeable stuttering. You can download a complete cache from places like [http://www.reddit.com/r/Cemucaches/comments/7bv7el/complete_shader_cache_collection_1110c_v2/ here] and rename them to match your game version's ID to spare yourself most of that unpleasant experience. Just keep in mind that shader caches from versions older than 1.8.0 are incompatible with later versions of Cemu. At startup, Cemu will prepare a compiled version of that cache under <code>.\Cemu\shaderCache\precompiled</code> and that one depends on your GPU driver, so you might want to erase it if any problems or crashes when compiling shaders at startup occur. ==Troubleshooting/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/ CEMUhookCemuhook] 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 for an increase in the framerate. This is not to enjoy a slight FPS increasebe confused with '''Texture Packs''', which are replacement textures; Cemu doesn't support that, but it is planned.

Developers plan to add custom texture replacement in The "Graphic Packs" themselves are folders under the future (hence <code>graphicPacks</code> directory. They can be named anything, but they should contain the name) but that's yet to be seen as of 1"<code>rules.7.6txt</code>" file.A bare-bones example of a "Graphics Pack", called "Bayo_1080p", would look like this:

The Graphic Packs themselves come as folders under the graphicPacks directory. You can [Definition] titleIds = 0005000010172600,0005000010172700,000500001011b900,000500001014db00,0005000010157e00,0005000010157f00 name these folders whatever you want (for example = "Bayo_1080pBayonetta 1 + 2 - 1080p"), which contains just a single "rules.txt" file. A more bare-bones file would look like this: [TextureRedefine] width = 1280 height = 720 overwriteWidth = 1920 overwriteHeight = 1080

Whenever the titleId matches the current one, Cemu will show the Graphics Pack under Options -> Graphics Pack. If you don't know what the titleId of the game you want is, check the <code>::[Definition]::titleIds = 0005000010172600,0005000010172700,000500001011b900,000500001014db00,0005000010157e00,0005000010157f00::name = "Bayonetta 1 + 2 - 1080p"::::[TextureRedefine]::width = 1280::height = 720::overwriteWidth = 1920::overwriteHeight = 1080 logs.txt</code>file. You can safely delete it in the event that it gets too big for a text editor to parse.

In CEMU, under Options/Graphics Pack, you'll see The overwriteWidth and overwriteHeight properties used in this particular graphic pack as "Bayonetta 1+2 - example will upscale the game from 720p to 1080p". The name But if the game doesn't matterhave all of its textures in the specified resolution, what matters the most would they won't be that the titleIds (here matching all three US/EU/JP versions of both Bayonetta 1 upscaled and 2) match that of could look messy as a result. In this case, this problem is seen in some FMVs in the game in question. You can get This is the titleIds looking at purpose of the logs.txt file CEMU generates whenever it loads a new game (and which you can delete safely so that it doesn't get too big to read)TextureRedefine rule.

When you enable this graphical pack and then load the game, it will play following this rule which is upscaling a game that runs as 1280x720 so that it runs as 1920x1080. But if the game doesn't have all of its textures originally in that resolution you specified (1280x720), they won't be upscaled and it could look messy as a result. For example, in Bayonetta 2's case, this problem can be seen in See some FMVs. That's why some graphical packs add exclusions to 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 of the community graphics packs made so far at [http://slashiee.github.io/cemu_graphic_packs/ from herethis page].

There's an ongoing controversy about CEMU being closed-source, but it's a purely meta discussion and isn* Save states aren't getting implemented any time soon. This has a deal killer if you just want lot to play do with the complexity of the Wii U games on PCmemory layout and architecture, as well as the huge file size. As a result, considering CEMU the current developers are not interested in implementing them.* The emulator is good enough for that still unfinished and unoptimised, as noted in the best choice available currentlylack of efficient and stable H.264 video decoding, causing glitchy videos. With that out of the wayThis is worked around with Cemuhook entirely, here's some of the actual issues that relate but its approach to video decoding is unlikely to be taken into the end user experience:emulator.

* Save states aren't getting implemented any time soon. A lot of this has to do with ===Piracy===There are anti-piracy measures on the complexity of Patreon early-access builds that are put behind the Wii U memory layout and architecture, as well as the huge file size$5 tier. As a resultBackers putting out these builds can get banned if they're caught, and when the current developers are not interested in implementing them.* Frequent stuttering is often experienced when you first start a gameprogram fails verification, because CEMU is building your shader cache. One solution 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 whilelocks down some features that impact performance.

That asideUntil 1.7.5 was released, there's other issues that stem from the unfinished and unoptimised nature of the emulator, like the lack mudlord put out cracked versions of native H264 video decoding libraries causing green screens early builds on his personal blog. A subreddit and glitchy videos (which is solved with Cemuhook) among other thingsDiscord server was made to discuss Cemu piracy.