Navigate to Internal Storage/citra-emu/log and look for the file called citra_log. Do not start the Citra app again until after you have completed this guide. Run the game you are having issues with until it reaches the point where it crashes or encounters the bug. If the Citra app is already open, restart it first.
Upload that file, just like step 3 on the other set of directions. In appdata/roaming/citra/log, look for the file labeled ‘citra_log.txt’. If something has been printed out, however, you should follow that directory instead and manually navigate to /citra-emu/log there. If nothing gets printed out, that means the directory hasn’t been changed and the log is present in ~/.local/share/citra-emu/log. This command will print out the user-specific data directory.
How do i change the mac start up to verbose in mame emulator windows#
What to do if your copy of Citra cannot boot:įor Windows users: Paste %appdata%/Citra/log into your explorer address bar, and it should take you there.įor Linux/Mac users: In the terminal, type echo $XDG_DATA_HOME. MAME + MESS: Support for new emulator debug attribute. If you accidentally relaunched Citra, upload the citra_ file instead. Changed the order of MD5 and SHA1 in listinfo and XML datafiles. Upload (drag & drop) this file to your support post as a file attachment. Do not relaunch Citra or else the citra_log.txt file will be overwritten. In the window that you opened in Step 1, the log will be in citra_log.txt.
0 kommentar(er)
