I updated the citra nightly from 1980 to 1984 and when I started up the game it put me far back from where my last save was.
The saves show the last updates and when I try to jump to them it gives me a black screen and error popup.
- Operating System: Win10 Home
- CPU: RYZEN 5 3600
- GPU: GTX 1650
- Citra Version (found in title bar): Citra Nightly 1984
- Game: Pokemon Moon
- Screenshot of Issue:
screen after loading the save:
(The language is Polish)
citra_log.txt.old.txt (48.7 KB)
(I don’t know if this’ll work)
System Information for Support
Client Version Nightly 1984 HEAD-9e898bc
Operating System Windows 10 Version 22H2 (Build 19045.3324)
CPU AMD Ryzen 5 3600 6-Core Processor | AVX2 | FMA
Graphics API OpenGL 4.3.0
Graphics Renderer NVIDIA GeForce GTX 1650/PCIe/SSE2
GPU Driver Version 536.23
CPU JIT [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [x]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
I did not find anything wrong in your log file. Please wait for a human moderator to assist.
Download this Citra version: https://github.com/citra-emu/citra-nightly/releases/download/nightly-1880/citra-windows-mingw-20230409-cdb157f.7z
Extract it, open the extracted folder and open
citra-qt(.exe) load your saved rate there, save in-game and then load the in-game save in the latest Citra version, so you can play on the newest version.
Citra has two kinds of saves available to users, in-game saves and save states.
In-game saves are the ones you know from the 3DS. These can be shared between devices and are recommended for general use, as they do not corrupt as easily.
Save states, on the other hand, save Citra’s entire emulation state. This includes Citra’s configuration, a game’s RNG seed, as well as any faults in the emulation at the time of saving. This makes them very useful as a tool for practicing in-game tricks, or for usage in shiny hunting and other RNG related trigger events. However they’re not suitable as replacements for in-game save files as the faults in the emulation state would keep building up until the emulation state is too unstable to load properly. They’re also non-transferable because they are made with one setup and only one and can break with any Update.