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 56: | Line 56: | ||
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 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 86: | Line 86: | ||
[[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 103: | ||
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. | ||
