It appears that when I use 60 fps cheat and hd textures on metroid samus returns it crashes unpredictably. I know that probably is the cheat but since most users can run it just fine, I’'l upload the log and maybe we discover is something else. Also, it crashes at random time intervals.
- Operating System: Windows 10
- CPU: i5-12400
- GPU: GeForce GTX 1080Ti 11GB
- Citra Version (found in title bar): 1859
- Game: Metroid: Samus Returns
- Screenshot of Issue (include the full Citra window including titlebar): There’s nothing to see really, its really random and just says fatal error
In order for us to provide better support, we need to see the log generated by citra. This guide will walk you through how you can obtain the log file: How to Upload the Log File
Well, disable the cheat, then see if you encounter the issue.
i tried and never encountered the issue, but i think the game is another experience at 60fps. I was wondering if it woukd be possible to understand what went wrong from the log. I don’t wnat to waste your time, so in case i’ll try to work i ìt out myself, thanks anyway
Apparently it has something to do with the citra version, the cheat is not stable on later versions. Versions from july 2022 should work, i’m using citra 1776 and currently i’m having no crashes.
Thanks for the support throughout, byeee
If you’re still around, could you try this version? I’d like to figure out where the cheat stopped functioning as advertised: Release nightly-1782 · citra-emu/citra-nightly · GitHub (This is the last build before a major graphical change).
I’m having this issue with Samus Returns using the 60 fps hack as well. I’ve tested several different versions, both on my desktop (Windows 11, Ryzen 7 5800x, 3080 Ti) and Steam Deck (installed via flatpak).
1782 on desktop: error not observed
1819 on desktop: error present
1823 on Deck: error present
1860 on Deck: error present
I’m unable to test earlier versions on Deck because the flatpak commits accessible via konsole only go back to 1823.
Testing on desktop is fine for now. Can you test Nightly 1783? That build includes a big graphical change. So it might be the cause of this issue. Let me know how it goes.
Error does not appear to be present with Nightly 1783.
Then going by simple (1819+1783)/2=1801
Please try Nightly 1801 next: Release nightly-1801 · citra-emu/citra-nightly · GitHub
Sorry for the delay on this. The error does not appear to be present on Nightly 1801.
Sorry for being late on the topic, I didn’t expect these replies. If I can test other builds let me know. I’ll also try 1801. Thanks for the feedback on the topic, you’re awesome : )
currently used 1801 for a long session, i think 4 hrs, didnt crash and was super stable. I managed to also save from the emulator a lot of times and didnt crash a single time
@Carlo_Proserpio @TheRealMcDan Alright, let’s continue on with the testing then: (1801+1819)/2=1810
Please try Nightly 1810 next: Release nightly-1810 · citra-emu/citra-nightly · GitHub
tested 1810 a couple of hours, stable (the latest version crashed once every 10ish minutes, so I think this one is pretty stable)
Alright, then (1810+1819)/2=1814,5
So lets try Nightly 1815 next: Release nightly-1815 · citra-emu/citra-nightly · GitHub
The error does not appear to be present on Nightly 1815. I’ll test 1818 next, as based on github info it seems to be more significant an update than 1816. 1817, if it exists, does not appear to be on there.
I’ve now confirmed the error is present in 1816 and 1818.
Edit: Reverting to 1815 again to be sure.
i was playing just now and 1815 crashed for some reason after a while but i assume it was my setup then?
@Carlo_Proserpio what does the log report?
Edit because it won’t let me reply because I’m a new user or something?:
I’ve had 1815 running for over 90 minutes without issue. It seems 1816 if the release where the 60fps cheat stopped functioning as intended.