Report the issue on GitHub after verifying nobody else posted it already.
We usually call our issues: "Game title - Observed problem"
Do not tag your issue name, it will be done for you (We’ll add “A-Audio” tags etc as we see fit, so do not include tags like “[Audio]” in the title)
When submitting the issue, make sure these links will still be reachable in 1-2 years.
Some issues are hard to track down. And even if they are fixed it’s good to have documentation reaching back a couple of months.
Please make sure to mention the latest commit hash/id of the nightly/master build you were using (which should be in the window title).
hehe just curious as we edited that post a few days ago. it used to say something different. it was functionally the same command, but a few of us were curious to see if the old command was the cause of the cut off log. apparently thats not the cause though…
I assume you’re referring to switching to the dedicated GPU? If you have a laptop with Nvidia graphics you can open Nvidia control panel. After running a game in Citra once you can add a program>Citra and switch it to use the “high performance Nvidia” graphics
[Moderator: This message has been moved here from a duplicate topic.]
Hey, it’s me again. While casually playing the game, when it comes time for the Dream Stone spirit to go downwards, the game crashes. The pipe in the beginning in the area also crashes. Did some searching on the issue and found this topic:
When looking through the topic, the only thing that might have resembled a solution to the issue was adding a high performance option to Citra in the NVIDIA graphics control. But I have Intel, which doesn’t have that option (or so I looked). According to the topic, nobody ever made a GitHub issue about it, which is the explanation to why this issue hasn’t been resolved yet.
Every time Citra has crashed and I’ve reported it, the mods have told me the log is incomplete. I think this is as a result of Windows telling me that it’s crashed and will shut it down for me. So yes, the log is incomplete (sorta), but there’s nothing I can do about it.