Citra: Difference between revisions
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
==Download== | ==Download== | ||
;We do not recommend using Citra anymore. Instead, we recommend using [[#Forks|active forks of Citra]]. | |||
{| cellpadding="4" | {| cellpadding="4" | ||
|- | |- | ||
| Line 28: | Line 30: | ||
|} | |} | ||
If you decide to install it from the archived link, the updater tries to fetch for updates and can't fetch any due to it shutting down forcing you to quit the setup. However, you can download Citra from "Manual Installation" section and you can download and use Citra as usual. | |||
==System requirements== | |||
See [[Computer specifications#Citra]] | |||
==History== | ==History== | ||
| Line 35: | Line 40: | ||
===Lawsuit=== | ===Lawsuit=== | ||
See [[Yuzu#Lawsuit]]. | See [[Yuzu#Lawsuit]]. | ||
==Shared data== | |||
Some 3DS games make use of shared files from the console's system software. These games will not boot in Citra if said files are not present in the user folder. | |||
These files are not provided by the Citra developers for legal reasons, so they can be downloaded from the [[Emulator Files#Nintendo 3DS|Emulator Files]] page. | |||
==Importing saves== | |||
Some games require this to bypass bugs in title screens. | |||
# Get the Title ID for the game version you have from [http://www.3dsdb.com/ here]. For example, we'll try with the European version of Zelda: ALBW. Its full Title ID is <code>00040000000EC400</code>. | |||
# Take the last 8 digits of the Title ID. (in our example, <code>000EC400</code>) In case this method fails later, take <code>00000000</code> instead, or make sure the save file and the ROM image are from the same region. | |||
# Make an empty folder named as that partial Title ID (<code>000EC400</code>). Put inside it another folder named "data", then inside that one put another folder named <code>00000001</code>, then inside that one put the actual save data files. | |||
# Move the folder with the title ID and put it here: | |||
#: <code>\user\sdmc\Nintendo 3DS\00000000000000000000000000000000\00000000000000000000000000000000\title\00040000</code> | |||
==Issues== | |||
===Emulation issues=== | |||
Emulation for various features is non-existent or not actively worked on enough to be in a usable state. This includes: | |||
* Connectivity features relying on Wi-Fi (Wii U/3DS, Switch/3DS, 3DS Local Multiplayer, 3DS Online...), not in small part due to the setbacks hindering Wi-Fi DS emulation. However, Download Play is emulated. | |||
* New 3DS mode. It is now in a playable state, but some games may still crash with it enabled. | |||
===Game image format=== | |||
Citra accepts games in '''.3ds, .cia or .cxi format'''. Furthermore, in Summer 2017, chances are your existing dumps tailor-made for Citra most probably made with the officially recommended tool braindump, which were missing some data yet could be emulated on Citra, have had their compatibility broken as a design choice with no options provided to fix those dumps. You'll have to get new dumps. | |||
While the latest sighax exploit allows for dumping decryption keys to convert (and possibly load) encrypted games in either .3ds or .cia format, development for a solution to allow for this Citra, even one requiring keys from your console, was formerly not actively pursued ''as a design choice''. Tools on 3DS and PC exist to convert those to decrypted .3ds format, and a guide can be found [[Nintendo 3DS emulators#Encryption|here]]. However, Citra now allows loading/installing encrypted 3ds/CIA files if the necessary AES keys are provided. The required keys are provided with the 3DS Shared Data downloadable above. | |||
===Telemetry=== | |||
Citra developers decided to implement a telemetry feature, uploading to them through Internet connection detailed logs and data about your computer specs and the games you're playing. When booting Citra for the first time, you get asked if you want to enable it. | |||
===macOS compatibility=== | |||
Although macOS support in Citra is still poor, macOS builds have returned to Citra Canary 2485 and newer thanks to the addition of the new Vulkan renderer. Previously, macOS builds were discontinued after build 1782 due to the developers raising the OpenGL requirements to version 4.3, while macOS only supports up to version 4.1. The new Vulkan renderer addresses this by utilizing the MoltenVK translation layer instead of OpenGL, enabling compatibility with macOS systems. Additionally, these latest builds are Universal and have native support for both Intel and Apple Silicon. | |||
==Forks== | ==Forks== | ||
| Line 229: | Line 264: | ||
;Citra MMJ: '''Citra MMJ''' is a Citra fork for Android written by weihuoya. In the past, it has been claimed that it offers better performance on Android, however, with recent Android performance improvements in other forks, it is unclear if this is still the case. Additionally, not all of the code distributed in Citra MMJ binaries is included in the source code repository on GitHub, meaning there is less transparency for users who want to know what code is being run on their systems and less openness for external developers who may wish to contribute. This may also violate the emulator's GPLv2 license, which stipulates that source code must be available to anyone who can obtain a binary. | ;Citra MMJ: '''Citra MMJ''' is a Citra fork for Android written by weihuoya. In the past, it has been claimed that it offers better performance on Android, however, with recent Android performance improvements in other forks, it is unclear if this is still the case. Additionally, not all of the code distributed in Citra MMJ binaries is included in the source code repository on GitHub, meaning there is less transparency for users who want to know what code is being run on their systems and less openness for external developers who may wish to contribute. This may also violate the emulator's GPLv2 license, which stipulates that source code must be available to anyone who can obtain a binary. | ||
== References == | == References == | ||