You should also contact any of the developers in the forum in order to know about the current state of the emulator because the TODO list isn't maintained anymore. If you want to contribute please take a look at the Contributor's Guide and Developer Information. It's also where our central repository is hosted. Most of the development happens on GitHub. Details on the build process can be found in our Flathub repository.
PRs tagged canary-merge are merged only into the Canary builds.īoth builds can be installed with the installer provided on the website, but those looking for specific versions or standalone releases can find them in the release tabs of the Nightly and Canary repositories.Ĭurrently, development and releases of the Android version are in a separate repository.Ī Flatpak for Citra is available on Flathub. The Canary build is based on the master branch, but with additional features still under review. The Nightly build is based on the master branch, and contains already reviewed and tested features. ReleasesĬitra has two main release channels: Nightly and Canary. Need help? Check out our asking for help guide.įor development discussion, please join us on our Discord server or at #citra-dev on libera. Please read the FAQ before getting started with the project. (Playable here means compatibility of at least "Okay" on our game compatibility list.)Ĭitra is licensed under the GPLv2 (or any later version). It is written with portability in mind, with builds actively maintained for Windows, Linux and macOS.Ĭitra emulates a subset of 3DS hardware and therefore is useful for running/debugging homebrew applications, and it is also able to run many commercial games! Some of these do not run at a playable state, but we are working every day to advance the project forward.
You can find the original README.md below the break.īEFORE FILING AN ISSUE, READ THE RELEVANT SECTION IN THE CONTRIBUTING FILE!!! CitraĬitra is an experimental open-source Nintendo 3DS emulator/debugger written in C++. Port yuzu-emu/yuzu#3791: "configuration: Add Restore Default and Clear options to hotkeys"Įnd of merge log. Service/frd: return cfg username on GetMyScreenNameĬitra_qt/configure_input: Account for analog buttons when checking for used buttons
Remove CopyImageSubData and enable TextureView reinterpreter only on nvidiaįix software renderer for empty texture addresses PS: The point of bleeding edge is to have a build that allows the developers to crowd test for regressions, since people will often go on the forums or reddit or other places and complain if something breaks in bleeding edge, we can use this info to tell which in development branch caused the breakage.Base revision: 0126ecb3e25295edc0768d20223d1358e330c622 Pull Request
Source: i wrote the code for bleeding edge to merge the pull requests and build it and upload it and stuff. Any other build is made from master + in development branches from citra contributors meaning some times there will be bugs in those builds. So the benefit of running nightly is it is code that was reviewed and checked for quality. We have a label on github that says something should be in bleeding edge so it only takes a click of a button Bleeding edge in particular only adds changes that are currently under review for citra, the pull requests that I was talking about earlier. Changes to master have gone through review and are generally sound.īleeding edge (and similarly any other "chinese" or unofficial builds or whatever people decide to call them) are just master + a few more code changes.
Consider it the trunk of the tree, where its sturdy and stable and any other build is just a branch from the trunk. Every last build out there is based off master. Master (nightly builds) is the current code base for citra. When someone submits code to citra, its called a Pull Request (i wrote this code and request that you pull the changes into citra) Any random person will write some code for citra, then other people will read through the code to make sure that its good code and will work. Its the same way dolphin, ppsspp, and many other popular emulators work. Everything that makes it into citra goes through a review process.