mirror of
https://github.com/citra-emu/citra.git
synced 2024-11-15 05:50:08 +00:00
update faq information
parent
039f6c9feb
commit
56b6e2c7be
34
FAQ.md
34
FAQ.md
@ -50,11 +50,11 @@ Yes, though you'll need to dump your 3DS' system keys for this to work:
|
|||||||
|
|
||||||
#### Can _Citra_ run _Pokémon_ games?
|
#### Can _Citra_ run _Pokémon_ games?
|
||||||
|
|
||||||
All Pokémon games now work properly. For Pokémon X & Y. Linux users building from source need to take a look at [[Building for Linux]] for building with the AAC audio decoder.
|
All Pokémon games now work properly. For Pokémon X & Y, Linux users building from source need to take a look at [[Building for Linux]] for building with the AAC audio decoder.
|
||||||
|
|
||||||
#### Does _Citra_ run on an Apple silicon device?
|
#### Does _Citra_ run on an Apple silicon device?
|
||||||
|
|
||||||
_Citra_ does NOT support Apple silicon (M1/M2) MacOS devices.. Our Mac builds may run through Rosetta, but you WILL encounter various issues that we won't provide support for. We may eventually support M1 Macs, but not at this time.
|
Yes! _Citra_ does support Apple silicon (M1/M2) MacOS devices.
|
||||||
|
|
||||||
#### Are you planning on making an iOS Citra port?
|
#### Are you planning on making an iOS Citra port?
|
||||||
|
|
||||||
@ -89,9 +89,9 @@ Yes, you can configure your controller directly through the GUI in `Emulation ->
|
|||||||
#### Can I make _Citra_ fully portable?
|
#### Can I make _Citra_ fully portable?
|
||||||
|
|
||||||
Yes, go to our [download](https://citra-emu.org/download/) page and select `Manual download`. Then under **Nightly Build**, click on your operating system's icon to the right of the latest build available to download the build.
|
Yes, go to our [download](https://citra-emu.org/download/) page and select `Manual download`. Then under **Nightly Build**, click on your operating system's icon to the right of the latest build available to download the build.
|
||||||
Extract it (.7z can be extracted using Winrar or 7zip) and put it wherever you wish. Inside the extracted `nightly-mingw` folder, create a folder called `user`. This _Citra_ should now store all of its config, save files and such inside of this `user` folder.
|
Extract it (.7z can be extracted using Winrar or 7zip) and put it wherever you wish. Inside the extracted `nightly` folder, create a folder called `user`. This _Citra_ should now store all of its config, save files and such inside of this `user` folder.
|
||||||
Check to make sure that this `user` folder is in the same folder that contains `citra-qt(.exe)`
|
Check to make sure that this `user` folder is in the same folder that contains `citra-qt(.exe)`
|
||||||
Now you can start this _Citra_ by launching the citra-qt executable found inside of the `mingw` folder.
|
Now you can start this _Citra_ by launching the citra-qt executable found inside of the `nightly` folder.
|
||||||
|
|
||||||
#### Can I expect _Citra_ to play [GAME] at full-speed?
|
#### Can I expect _Citra_ to play [GAME] at full-speed?
|
||||||
|
|
||||||
@ -143,25 +143,19 @@ Unofficial builds are not supported. There may be other branches that are planne
|
|||||||
|
|
||||||
We're pleased to say that _Citra_ works on all three major desktop operating systems and Android!
|
We're pleased to say that _Citra_ works on all three major desktop operating systems and Android!
|
||||||
|
|
||||||
_Citra_ is actively tested and supported on various 64-bit version of _Windows_ (_10_ and up), _Linux_ and Android (9.0 - Pie or newer). Other platforms may work, but aren't tested by developers. We have no plans to support 32-bit operating systems officially.
|
_Citra_ is actively tested and supported on various 64-bit version of _Windows_ (_10_ or newer), _MacOS_, _Linux_ and _Android_ (9.0 - Pie or newer). Other platforms may work, but aren't tested by developers. We have no plans to support 32-bit operating systems officially.
|
||||||
|
|
||||||
MacOS support has been temporarily dropped whilst work on the graphics backend is underway. Part of that work required us to up the OpenGL 3.3 version requirement to OpenGL 4.3, which is something that MacOS doesn't support. So until a Vulkan implementation is implemented, the last Citra MacOS build that works is Nightly 1782:
|
|
||||||
Download `citra-osx-20220901-d380980.tar.gz` from https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1782
|
|
||||||
Extract the .tar.gz file and run `citra-qt`.
|
|
||||||
|
|
||||||
After installing this version, make sure to not update your Citra version to a newer build, they won't work. We will make an announcement about when it is safe to so again.
|
|
||||||
|
|
||||||
#### What kind of specification do I need to run _Citra_?
|
#### What kind of specification do I need to run _Citra_?
|
||||||
|
|
||||||
The only **hard** requirements for the official version of _Citra_ is a graphics chip that supports **at least _OpenGL 4.3_** and a **64-bit OS** running on a standard PC, but you definitely want a processor with the highest possible performance per core.
|
The only **hard** requirements for the official version of _Citra_ is a graphics chip that supports **at least _OpenGL 4.3_ or _Vulkan 1.1_** and a **64-bit OS** running on a standard PC, but you definitely want a processor with the highest possible performance per core.
|
||||||
|
|
||||||
#### What are _Citra_ Android's requirements?
|
#### What are _Citra_ Android's requirements?
|
||||||
|
|
||||||
* A 64-bit operating system.
|
* A 64-bit operating system.
|
||||||
* Support for OpenGL ES 3.2
|
* Support for OpenGL ES 3.2 or Vulkan 1.1
|
||||||
* At least Android 9.0 (Pie) or newer.
|
* At least Android 9.0 (Pie) or newer.
|
||||||
|
|
||||||
If you're unsure whether your Android device meets the requirements, download Aida64 from the google play store. You can find the instruction set (64-bit or 32-bit) information in the _CPU_ tab, the OpenGL ES version in the _Display_ tab and the Android version in the _Android_ tab.
|
If you're unsure whether your Android device meets the requirements, download Aida64 from the Google Play Store. You can find the instruction set (64-bit or 32-bit) information in the _CPU_ tab, the OpenGL ES version in the _Display_ tab and the Android version in the _Android_ tab.
|
||||||
|
|
||||||
We also recommend at least a Snapdragon 835 SoC or better. Your experience may vary greatly depending on the quality of your device's GPU drivers.
|
We also recommend at least a Snapdragon 835 SoC or better. Your experience may vary greatly depending on the quality of your device's GPU drivers.
|
||||||
|
|
||||||
@ -315,7 +309,7 @@ Unmapped read/write related crashes and freezes can occur both right at the star
|
|||||||
|
|
||||||
#### There is an error that occurs in _Citra_ with Intel HD 4000/2500 integrated GPUs on Windows (and Intel HD Graphics of the same architecture (Ivy Bridge)).
|
#### There is an error that occurs in _Citra_ with Intel HD 4000/2500 integrated GPUs on Windows (and Intel HD Graphics of the same architecture (Ivy Bridge)).
|
||||||
|
|
||||||
These GPUs have driver bugs that will cause freezing and crashing, seemingly at random. Some users can run some versions of _Citra_ Nightly with no issues whatsoever, but after updating to a newer, or downgrading to an older _Citra_ version, these crashing/freezing issues start to occur. Other users can't run any _Citra_ Nightly version at all. The only way to fix this currently is to use [Citra Nightly 1392](https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1392) or older.
|
These GPUs have driver bugs that will cause freezing and crashing, seemingly at random. Some users can run some versions of _Citra_ Nightly with no issues whatsoever, but after updating to a newer, or downgrading to an older _Citra_ version, these crashing/freezing issues start to occur. Other users can't run any _Citra_ Nightly version at all. The only way to fix this currently is to use [Citra Nightly 1782](https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1782) and to disable *V-sync* in `Emulation -> Configuration -> Graphics -> Advanced Tab`.
|
||||||
If you're unsure what iGPU you're using (or what generation), right click on your Windows start button and select `Device Manager`. Expand the Display adapters tab. It should tell you what GPU you have. If it only says `Intel HD Graphics`, expand the Processors tab as well. Then google your processor name. On Intel's product page, it should tell you what generation it is from next to the "Code Name". If it says "Products formerly Ivy Bridge", the above also applies to you.
|
If you're unsure what iGPU you're using (or what generation), right click on your Windows start button and select `Device Manager`. Expand the Display adapters tab. It should tell you what GPU you have. If it only says `Intel HD Graphics`, expand the Processors tab as well. Then google your processor name. On Intel's product page, it should tell you what generation it is from next to the "Code Name". If it says "Products formerly Ivy Bridge", the above also applies to you.
|
||||||
|
|
||||||
#### There is a graphical error that occurs in _Citra_ with Intel HD 4400/4600 integrated GPUs on Windows (and Intel HD Graphics of the same architecture (Haswell)).
|
#### There is a graphical error that occurs in _Citra_ with Intel HD 4400/4600 integrated GPUs on Windows (and Intel HD Graphics of the same architecture (Haswell)).
|
||||||
@ -341,16 +335,6 @@ Not exactly. You can set up something similar, but this will only work if your s
|
|||||||
|
|
||||||
Go to `Emulation -> Configuration (Citra -> Preferences on MacOS) -> General`. Set your **Emulation Speed** slider to what you want your regular speed to be. Then set your **Use Alternate Speed** slider to what you want your speed-up/fast forward speed to be. Navigate to the `Controls -> Hotkey` menu. Find the **Toggle Alternate Speed** option and double click it to change it to whatever key you want your speed-up/fast forward key to be. Press OK and enjoy.
|
Go to `Emulation -> Configuration (Citra -> Preferences on MacOS) -> General`. Set your **Emulation Speed** slider to what you want your regular speed to be. Then set your **Use Alternate Speed** slider to what you want your speed-up/fast forward speed to be. Navigate to the `Controls -> Hotkey` menu. Find the **Toggle Alternate Speed** option and double click it to change it to whatever key you want your speed-up/fast forward key to be. Press OK and enjoy.
|
||||||
|
|
||||||
#### My _Citra_ has a gray screen, but I can hear game audio on the background (MacOS).
|
|
||||||
|
|
||||||
This is a MacOS specific bug. Resizing your _Citra_ window should fix it.
|
|
||||||
|
|
||||||
#### Why are my custom textures being displayed on the wrong surfaces?
|
|
||||||
|
|
||||||
This is a bug that occurs when Custom Textures are used in conjunction with a Texture Filter. You can disable the **Texture Filter** in `Emulation -> Configuration (Citra -> Preferences on MacOS) -> Graphics`. Make sure to restart your game after disabling the option.
|
|
||||||
|
|
||||||
If you really want to use both Custom Textures and a Texture Filter at the same time, you'll need to use [_Citra_ Nightly 1691](https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1691) until the bug is fixed.
|
|
||||||
|
|
||||||
#### How to fix "Array Size too short" error?
|
#### How to fix "Array Size too short" error?
|
||||||
|
|
||||||
This error occurs when attempting to load a Save State on a _Citra_ version that is different from the one that it was created on. Save States aren't compatible between different _Citra_ versions or even between different _Citra_ installations. It is therefore always recommended to use your in-game save files most of all for recording your progress, and to only use Save States within single gaming sessions.
|
This error occurs when attempting to load a Save State on a _Citra_ version that is different from the one that it was created on. Save States aren't compatible between different _Citra_ versions or even between different _Citra_ installations. It is therefore always recommended to use your in-game save files most of all for recording your progress, and to only use Save States within single gaming sessions.
|
||||||
|
Loading…
Reference in New Issue
Block a user