Issue:
There is a specific area in the beginning of Metroid Samus Returns in which Citra will freeze the screen but you’ll still be able to play the game and listen to the sound. It seems related to intel UHD 630 graphics as it doesn’t happen with my Nvidia card.
Client Version Nightly 1628 HEAD-1c8461f
Operating System Windows 10 (10.0)
CPU Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Graphics API OpenGL 3.3.0
Graphics Renderer Intel(R) UHD Graphics 630
GPU Driver Version 27.20.100.8587
CPU JIT [x]
Hardware Renderer [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [ ]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
Here’s some issues I found with your log that might help.
Enabling Accurate Multiplication is recomended in certain games. If you are experiencing graphical glitches, try enabling this option.
Same results. I believe it’s probably due to intel’s crappy opengl drivers, but who knows if you guys could take a look at it and see if there’s any workaround for intel graphics’ users.
Client Version Nightly 1628 HEAD-1c8461f
Operating System Windows 10 (10.0)
CPU Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Graphics API OpenGL 3.3.0
Graphics Renderer Intel(R) UHD Graphics 630
GPU Driver Version 27.20.100.8783
CPU JIT [x]
Hardware Renderer [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [ ]
Shader JIT [x]
System Region -1
Shader Disk Cache [x]
Here’s some issues I found with your log that might help.
Enabling Accurate Multiplication is recomended in certain games. If you are experiencing graphical glitches, try enabling this option.
Whilst your GPU isn’t supposed to have the issue I’m thinking off, doesn’t hurt to test it anyways. Please try a portable nightly 1392:
Download citra-windows-mingw-20191214-ddb7ead.7z (direct link) from https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1392
Extract it using Winrar or 7zip. Put the extracted folder anywhere you want. Inside the extracted nightly-mingw folder, create a folder called user . Now run citra-qt.exe from the folder and run your game.
Client Version Nightly 1392 HEAD-ddb7ead
Operating System Windows 10 (10.0)
CPU Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Graphics API OpenGL 3.3.0
Graphics Renderer Intel(R) UHD Graphics 630
GPU Driver Version 27.20.100.8783
CPU JIT [x]
Hardware Renderer [x]
Hardware Shader [x]
Hardware Shader, Accurate Multiplication [ ]
Shader JIT [x]
System Region -1
Here’s some issues I found with your log that might help.
Enabling Accurate Multiplication is recomended in certain games. If you are experiencing graphical glitches, try enabling this option.
Interestingly Citra reports the opengl api version is 3.3 but according to intel uhd 630 was supposed to be 4.6. Maybe that’s the problem, the opengl detection may be broken or intel’s opengl update is buggy, which should be probably the case. I hope someone else can try it with their iGPU.
Nah, Citra targets OpenGL 3.3. It says it for me as well even on a GTX 1070.
You should enable accurate multiplication and clear the shader cache so you won’t get another bug that would lead to crashes. To clear the crash, open Citra then File -> Open Citra Folder, delete shaders\opengl folder.
Client Version Nightly 1628 HEAD-1c8461f
Operating System Windows 10 (10.0)
CPU Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Graphics API OpenGL 3.3.0
Graphics Renderer Intel(R) UHD Graphics 630
GPU Driver Version 27.20.100.8783
CPU JIT [x]
Hardware Renderer [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 moderator to assist.
No, because Intel HD Graphics 4000 is vastly different from the Intel HD Graphics 630 that you’re using for example. Add to that that not all of us have your game and that makes reproducing your issue under the same circumstance nigh impossible.
Regardless, does that crash also occur when you only use in-game saves? I.e. no save state usage whatsoever?
I don’t use save states, I use a normal save point in the game. This bug happens in the very beginning of the game and the crash is very close to a save point, so I can easily and consistently reproduce it. That’s why I’m trying all your suggestions, and if you have any others, let me know.
If any of you’d have skylake or above you’d pretty much be able to reproduce it because all intel 6th+ generations use the same crappy graphics driver.
This is just to confirm that the GPU is at fault, can you try reproducing your crash without hardware shaders enabled? It will be extremely slow, that’s normal. You can find the option in emulation>configuration>graphics>advanced
