Changing these files is only to be done by advanced users because making changes at random can cause Citra not to work as expected or at all. The Citra executable has options menus that allow users to change most of the aforementioned configurations safely. If Citra has trouble running after changing a file and the user cannot remember what they changed, delete the configuration files and run the executable again so that they are regenerated automatically albeit as though Citra is being run for the first time so any existing configurations are lost.
This file is automatically generated by Citra and stores the logging. It is overwritten every time Citra is launched. This directory will contain the data directory and potentially also the system archives. This directory is automatically generated by Citra and contains the system and extra data for the emulated NAND. Inside this directory is another directory, On a physical 3DS, the directory inside data would be named differently.
This knowledge is only important if you plan on dumping any NAND system data or extra data from a physical 3DS and associating it with Citra. Most system save data has a TID high of For details about the different kinds of system save data, see 3dbrew. For first-time Citra users, there may be nothing inside the sysdata directory. In fact this will be the case for most Citra users, and is nothing to be alarmed about. This data will be created automatically in some cases, such as when a Mii is saved in Mii Maker.
Almost none of this data is essential for Citra to run homebrew games or backups of licensed titles. On a real SD card, there would not be two folders, but instead the folders would be named as hexadecimal characters corresponding to a 3DS console ID. If any games have been saved while playing them with Citra, there should be a folder inside sysdata named This folder contains all of the save data for 3DS titles.
It is entirely possible to retrieve save data from an SD card using a physical 3DS console and import it into Citra to continue a game where it was last left off on the console. On a real SD card, the sysdata folder will also contain the files required to run any 3DS titles installed to the SD card. On a real SD card, there may be two other directories inside sysdata.
These directories are named e and c and correspond to downloaded game updates and DLC respectively. The latest version of GodMode9 is required to redump your DLCs if you do not own all them as it was dumped incorrectly before. This directory contains all of the extra data created when playing 3DS game backups.
The backups folder contains saved data backed up via the Home Menu. Citra does not need any of these folders so there is currently no value in dumping them. If the user does not have shared font installed, Citra will use the open source font replacement instead. Users should redump their shared font since the open source font replacement may not always look accurate. See a mistake? Want to contribute?
Note: although separate in the title, the shared fonts are part of the system archives now. The title was made when they were separate, and is kept unchanged to avoid breaking wiki links. By following the guide below you do get the shared fonts as well. At this time, Citra can run many games without needing to do any special work on a physical 3DS. My name has been dropped here twice so I'll also add my 2 cents: I fully agree with SigmaVirus.
Here is why: We do HLE and implement most of the OS which is contained on the 3DS, for completeness this should include data files which are necessary to run games. The whole "you need system files" is exclusive to Citra.
We live in a world of HLE and emus-including-bioses. Emu users don't expect that they need more files from a real 3DS. We get a ton of support requests about this. The instructions how to get these files, which games need them etc. Ideally we wouldn't need such docs at all if we have proper recreation files. RavenHome1 mentioned this issue Aug 10, Shared Font Substitute And please don't reply to this. Just ask somewhere else.
Limited commentary to collaborators to reduce noise. We have implemented our own versions of all the archives by now. BreadFish64 closed this Feb 19, Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in. Linked pull requests. You signed in with another tab or window. Reload to refresh your session.
0コメント