Editing Cemu
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| + | {{WIP}} | ||
{{Infobox emulator | {{Infobox emulator | ||
|logo = Cemu-Logo.png | |logo = Cemu-Logo.png | ||
|version = {{Version|Cemu}} | |version = {{Version|Cemu}} | ||
|active = Yes | |active = Yes | ||
| − | |platform = [[Emulators on Windows|Windows]]</br>[[Emulators on Linux|Linux | + | |platform = [[Emulators on Windows|Windows]]</br>[[Emulators on Linux|Linux]] (experimental) |
|architecture = x86_64 | |architecture = x86_64 | ||
|target = [[Wii U emulators|Wii U]] | |target = [[Wii U emulators|Wii U]] | ||
| Line 15: | Line 16: | ||
}} | }} | ||
| − | '''[[wikipedia:Cemu|Cemu]]''' is a [[Wii U emulators|Wii U emulator]] | + | '''[[wikipedia:Cemu|Cemu]]''' is a now open-source [[Wii U emulators|Wii U emulator]]. Its development was started circa 2015 and it's known to be the very first Wii U emulator ever that can boot games. |
| + | |||
| + | Before updates are publicly released, they're accessible to backers over at [https://www.patreon.com/cemu their Patreon]. | ||
==Download== | ==Download== | ||
| Line 22: | Line 25: | ||
|'''[http://cemu.info/index.html#download Latest public release]'''<br/><small>Available one week after the Patreon builds release</small><br/> | |'''[http://cemu.info/index.html#download Latest public release]'''<br/><small>Available one week after the Patreon builds release</small><br/> | ||
|- | |- | ||
| − | |align=center|{{Icon|Win|Lin | + | |align=center|{{Icon|Win|Lin}} |
| − | |'''[https://github.com/cemu-project/Cemu/releases GitHub release]''' | + | |'''[https://github.com/cemu-project/Cemu/releases GitHub release]''' |
|} | |} | ||
==System requirements== | ==System requirements== | ||
| − | + | You will also need enough storage for the [[Wii U emulators|Wii U]] games. Running Cemu on [[Wine]] has been reported to work just as well as Windows. | |
| − | * Windows 7 ( | + | ===Minimum=== |
| − | + | * Windows 7 (64-bit) | |
| − | * OpenGL 4.5 or Vulkan 1.1 | + | * Graphics Card: Supports at least OpenGL 4.5 or Vulkan 1.1 |
| − | * | + | * Memory: 4 GB |
| − | + | ===Recommended=== | |
| − | + | * Windows 10 (64-bit) | |
| − | + | * Graphics Card: Supports OpenGL 4.6 (Vulkan 1.1 for AMD or Intel) | |
| − | + | * Memory: 8 GB or more | |
==Game formats and needed files== | ==Game formats and needed files== | ||
| Line 56: | Line 59: | ||
The Update installation method has been reworked since 1.11.0 simplifying the installation method a lot. | The Update installation method has been reworked since 1.11.0 simplifying the installation method a lot. | ||
| − | To install updates and DLC on Cemu on (1.11.0)+ versions you need to follow | + | To install updates and DLC on Cemu on (1.11.0)+ versions you need to follow theses steps : |
| − | *On Cemu interface, select File | + | *On Cemu interface, select File -> Install game update or DLC |
*Select the meta.xml in the meta folder of the update or DLC | *Select the meta.xml in the meta folder of the update or DLC | ||
*Run the game to update the UI and show the update and/or DLC version | *Run the game to update the UI and show the update and/or DLC version | ||
===Amiibo support=== | ===Amiibo support=== | ||
| − | [[Amiibo]] are 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). There's a regularly updated complete set of the official ones | + | [[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). There's a regularly updated complete set of the official ones but there are also unofficial spoofed packs on various other sites. |
Recent versions of Cemu include Amiibo support. Simply go to NFC / Scan NFC Tag from file, and load the relevant .bin file. Keep in mind Amiibo support in Cemu is incomplete right now and not all figurines are compatible yet - though incompatibilities may be caused by bad Amiibo dumps as well. | Recent versions of Cemu include Amiibo support. Simply go to NFC / Scan NFC Tag from file, and load the relevant .bin file. Keep in mind Amiibo support in Cemu is incomplete right now and not all figurines are compatible yet - though incompatibilities may be caused by bad Amiibo dumps as well. | ||
| Line 72: | Line 75: | ||
Cemu cannot connect to a real (or emulated) [[Nintendo 3DS emulators|3DS]]. | Cemu cannot connect to a real (or emulated) [[Nintendo 3DS emulators|3DS]]. | ||
| + | |||
| + | ===Cemuhook=== | ||
| + | Using this is completely optional but highly recommended. Without Cemuhook, some games won't have texts, have laggy cutscenes and display numerous other bugs. | ||
| + | |||
| + | Download [http://sshnuke.net/cemuhook/ the latest version] compatible with your Cemu version, unpack it to the same directory as cemu.exe and right-click on dbghelp.dll, check Proprieties, Digital Signatures tab, select a signature and press Details. This should make it no longer crash at start-up. Make sure you also have the latest GPU driver installed, as well as both x86 and x64 versions of the [https://aka.ms/vs/15/release/vc_redist.x64.exe Microsoft Visual C++ 2017 X64 Redistributable]. | ||
| + | |||
| + | After the first boot of Cemu with cemuhook installed, accept to download the missing shared fonts to make the text in some games (Super Mario Maker among others) display correctly. | ||
| + | Whenever you boot Cemu now, this cemuhook tool is enabled by default and offers various additions for better motion control emulation or some graphical hacks that greatly enhance Zelda BOTW in particular. | ||
| + | Various way to take advantages of the cemuhook motion control emulation are listed [http://compat.cemu.info/wiki/Motion_Sensing#Full-motion_Solutions here]. | ||
| + | |||
| + | Enabling "GX2SetGPUFenceSkip (HACK)" enhances graphical emulation in BOTW in particular. A pre-installed Graphical Pack that comes with recent versions of Cemuhook, "LWZX Crash Workaround", as well as the "GX2DrawDone()" option under Experimental, should help with some general crashes specific to BOTW. | ||
| + | |||
| + | As of version 1.18.0, cemuhook is no longer considered required to run the emulator, as all major functions previously provided by cemuhook have been implemented into the emulator itself. | ||
===Shader caches=== | ===Shader caches=== | ||
| − | When your game is loaded, check for its ID on the title bar 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 [ | + | When your game is loaded, check for its ID on the title bar 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. | 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. | ||
| Line 86: | Line 102: | ||
[[File:Shadercachestuff.png|thumb|Some settings in the Nvidia control panel might help.]] | [[File:Shadercachestuff.png|thumb|Some settings in the Nvidia control panel might help.]] | ||
| − | Some games' transferable caches may cause slowdowns on some graphics cards | + | Some 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>. |
==Graphic Packs== | ==Graphic Packs== | ||
| − | To work around emulation bugs and other problems the way [[Dolphin]] does, "Graphic Packs" are title-specific property sheets which define advanced settings you might not be able to change in the interface. Basic rendering options including shadow resolution and quality, post-processing effects like bloom, lighting and god rays, custom | + | To work around emulation bugs and other problems the way [[Dolphin]] does, "Graphic Packs" are title-specific property sheets which define advanced settings you might not be able to change in the interface. Basic rendering options including shadow resolution and quality, post-processing effects like bloom, lighting and god rays, custom anti-aliasing, and such can be applied here. You can even use them to ''reduce'' the internal resolution for an increase in the framerate. This is not to be confused with '''Texture Packs''', which are replacement textures; Cemu doesn't support that, but it is planned. |
The "Graphic Packs" themselves are folders under the <code>graphicPacks</code> directory. They can be named anything, but they should contain the "<code>rules.txt</code>" file. A bare-bones example of a "Graphics Pack", called "Bayo_1080p", would look like this: | The "Graphic Packs" themselves are folders under the <code>graphicPacks</code> directory. They can be named anything, but they should contain the "<code>rules.txt</code>" file. A bare-bones example of a "Graphics Pack", called "Bayo_1080p", would look like this: | ||
| Line 103: | Line 119: | ||
overwriteHeight = 1080 | overwriteHeight = 1080 | ||
| − | Whenever the titleId matches the current one, Cemu will show the Graphics Pack under Options | + | 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>logs.txt</code> file. You can safely delete it in the event that it gets too big for a text editor to parse. |
The overwriteWidth and overwriteHeight properties used in this example will upscale the game from 720p to 1080p. But if the game doesn't have all of its textures in the specified resolution, they won't be upscaled and could look messy as a result. In this case, this problem is seen in some FMVs in the game. This is the purpose of the TextureRedefine rule. | The overwriteWidth and overwriteHeight properties used in this example will upscale the game from 720p to 1080p. But if the game doesn't have all of its textures in the specified resolution, they won't be upscaled and could look messy as a result. In this case, this problem is seen in some FMVs in the game. This is the purpose of the TextureRedefine rule. | ||
| Line 123: | Line 139: | ||
[[Category:Wii U emulators]] | [[Category:Wii U emulators]] | ||
[[Category:Windows emulation software]] | [[Category:Windows emulation software]] | ||
| + | [[Category:Closed-source emulators]] | ||
