3DS emulator based on Citra
Find a file
wwylele 36981a5aa6 pica/primitive_assembly: Handle winding for GS primitive
hwtest shows that, although GS always emit a group of three vertices as one primitive, it still respects to the topology type, as if the three vertices are input into the primitive assembler independently and sequentially. It is also shown that the winding flag in SETEMIT only takes effect for Shader topology type, which is believed to be the actual difference between List and Shader (hence removed the TODO). However, only Shader topology type is observed in official games when GS is in use, so the other mode seems to be just unintended usage.
2017-08-19 10:13:20 +03:00
.github Edit Citra URLs (#2728) 2017-06-03 23:51:45 +03:00
CMakeModules Modularized Qt and SDL file copying 2016-12-13 21:05:00 +01:00
dist citra-qt: Add Dark theme from https://github.com/ColinDuquesnoy/QDarkStyleSheet 2017-06-24 05:48:42 +02:00
externals Update cryptopp 2017-08-08 17:50:09 +10:00
hooks hook: remove clang-format check 2017-02-17 13:52:23 +02:00
src pica/primitive_assembly: Handle winding for GS primitive 2017-08-19 10:13:20 +03:00
.gitignore Add deploy to bintray for builds to master 2016-12-31 13:54:51 -05:00
.gitmodules Don't pull in entire JSON repo for single header file 2017-07-18 13:37:27 +10:00
.travis-build.sh Travis: Use a stable version of clang-format 2016-12-03 01:32:46 -08:00
.travis-deps.sh Produce 7zip artifacts on Travis and Appveyor 2017-07-28 14:22:43 +10:00
.travis-upload.sh Produce 7zip artifacts on Travis and Appveyor 2017-07-28 14:22:43 +10:00
.travis.yml Produce 7zip artifacts on Travis and Appveyor 2017-07-28 14:22:43 +10:00
appveyor.yml Produce 7zip artifacts on Travis and Appveyor 2017-07-28 14:22:43 +10:00
CMakeLists.txt common: Add build timestamp to scm_rev. 2017-08-03 20:10:37 -04:00
CONTRIBUTING.md Fixes typo on Citra forum link. 2017-03-06 08:27:59 -05:00
Doxyfile Remove every trailing whitespace from the project (but externals). 2015-05-29 21:59:29 +01:00
license.txt added license txt file 2014-04-08 19:03:00 -04:00
README.md fixing a couple of typos 2017-06-28 12:56:10 +01:00

BEFORE FILING AN ISSUE, READ THE RELEVANT SECTION IN THE CONTRIBUTING FILE!!!

Citra Emulator

Travis CI Build Status AppVeyor CI Build Status

Citra is an experimental open-source Nintendo 3DS emulator/debugger written in C++. It is written with portability in mind, with builds actively maintained for Windows, Linux and macOS. Citra only emulates a subset of 3DS hardware and therefore is generally only useful for running/debugging homebrew applications. At this time, Citra is even able to boot several commercial games! Most of these do not run to a playable state, but we are working every day to advance the project forward.

Citra is licensed under the GPLv2 (or any later version). Refer to the license.txt file included. Please read the FAQ before getting started with the project.

Check out our website!

For development discussion, please join us @ #citra on freenode.

Development

Most of the development happens on GitHub. It's also where our central repository is hosted.

If you want to contribute please take a look at the Contributor's Guide, TODO list and Developer Information. You should as well contact any of the developers in the forum in order to know about the current state of the emulator.

Building

Support

We happily accept monetary donations or donated games and hardware. Please see our donations page for more information on how you can contribute to Citra. Any donations received will go towards things like:

  • 3DS consoles for developers to explore the hardware
  • 3DS games for testing
  • Any equipment required for homebrew
  • Infrastructure setup
  • Eventually 3D displays to get proper 3D output working

We also more than gladly accept used 3DS consoles, preferably ones with firmware 4.5 or lower! If you would like to give yours away, don't hesitate to join our IRC channel #citra on Freenode and talk to neobrain or bunnei. Mind you, IRC is slow-paced, so it might be a while until people reply. If you're in a hurry you can just leave contact details in the channel or via private message and we'll get back to you.