N-archive/citra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Add entry about missing config blocks

Yuri Kunde Schlesner 2015-09-14 19:08:01 -03:00
parent 55c3356664
commit 757922b9dd
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
FAQ.md

@ -38,3 +38,13 @@ There are no specific hardware requirements for Citra - any modern x86-64 system
#### I think what you guys are doing is awesome! I am not a developer, but still want to support the project. What can I do? #### I think what you guys are doing is awesome! I am not a developer, but still want to support the project. What can I do?
That's awesome! Such support is what motivates us to keep working :) Stick around and keep motivating our work! If you're interested in donating, please join our IRC channel (#citra @ [Freenode](https://webchat.freenode.net/)) and contact a developer. Donations will be used to buy systems and games to test with, as well as paying for infrastructure and web costs. That's awesome! Such support is what motivates us to keep working :) Stick around and keep motivating our work! If you're interested in donating, please join our IRC channel (#citra @ [Freenode](https://webchat.freenode.net/)) and contact a developer. Donations will be used to buy systems and games to test with, as well as paying for infrastructure and web costs.
#### What to do if I get an error saying something like "GetConfigInfoBlock: Config block 0xXXXXX with flags X and size X was not found"?
Sometimes a game will freeze and you'll get an error which looks like this in the log, usually followed by a "Fatal Error":
```
Service.CFG <Error> core\hle\service\cfg\cfg.cpp:Service::CFG::GetConfigInfoBlock:236: Config block 0xA0001 with flags 2 and size 2 was not found
```
In this case, try deleting the file at `user/nand/data/00000000000000000000000000000000/sysdata/00010017/00000000/config` and running the latest version of Citra. If this does not work, then note the config block number (like `0xA0001`) and file a bug report.