Wikis

Log Filters

Citra supports configurable filtering of log message per-class. This is especially useful if you’re debugging a subsystem and want very detailed messages from it or if you want to silence some annoyingly spammy errors (e.g. unimplemented GPU features.) Messages are filtered in each class according to their severity, the filter will block all messages in the class that are below the configured severity. The severity levels are: Trace: Extremely detailed and repetitive (many times per frame) debugging information that is likely to pollute logs.

Continue Reading

Set Up APK Signing in Bitrise

Open src/android/ in Android studio Create New Fill out the necessary info, remember the passwords for later Finish the wizard to make sure it works Open the bitrise dash-board and go to workflows>code signing Upload the key store and enter the passwords and key alias in their respective spots That’s it :)

Continue Reading

Stack Trace Guide for Citra

Stack trace on Windows Download and install Visual Studio 2015 Community. Download the nightly build, source code and debug symbols (make sure they have the same commit hash). If you’ve compiled your own msvc build, then skip this and the following step. Extract them and place the .pdb files from the debug symbols into the nightly build folder. Run Citra and initiate the crash. If you’ve compiled your own msvc build, then run Citra from .

Continue Reading

Typical Git Workflow

This is a guide to a typical Git workflow with Citra. It covers forking from the main repository, creating a branch, keeping your branch up to date with the main repository, resolving conflicts, and merging back into the main repository. It’s not meant to be a hard-and-fast set of rules. However, if you follow something along these lines, you’ll be less likely to piss people off. It’s appreciated if every single commit in a branch on its own compiles on all supported platforms (Windows, Linux, and macOS) and doesn’t cause any regressions if the commits after it were left unmerged.

Continue Reading

User Directory

The User Directory Citra’s user directory is where the emulator persists the emulated 3DS NAND, save data, extra data, and a host of other files necessary for Citra to run properly. The path of the user directory can be opened from within the Citra application with the Open Citra folder menu option. On different systems the paths are: on any system, the presence of a directory named user on the same directory of the executable will override the default behavior and Citra will use that instead.

Continue Reading

Using a Controller or Android Phone for Motion or Touch Input

This page is currently under construction. See here for more information: https://cemuhook.sshnuke.net/padudpserver.html

Continue Reading