Pokemon Omega Ruby - Citra shows a black screen while the game continues to work in the background

Ive seen this exact issue posted here by many others and have tried all the solutions provided but nothing has worked
i cant update my Graphics card because its built in by the manufacturer or something and i get warned of compatibility issues so if theirs a workaround for that, please let me know

it is interesting to note that if i switched my Graphics API from ‘OpenGL’ to ‘Software’, the game runs without getting that black screen, at around 1-3 fps

System Information

  • Operating System: Windows 10 Pro 21H2
  • CPU: Intel(R) Core™ i5-7200U CPU @ 2.50GHz 2.71 GHz
  • GPU: Intel(R) HD Graphics 620
  • Citra Version (found in title bar): 1884 Nightly Build
  • Game: Pokemon Omega Ruby
  • Screenshot of Issue (include the full Citra window including titlebar):

Diagnostic Log
citra_log.txt (59.7 KB)

In order to save a copy of the log, follow this guide:

If your GPU is integrated, there isnt really a lot you can do to fix this. Integrated cards will also have extremely low power, as it is from 2016. Its really more of a hardware problem, so unless you are wanting to upgrade there isnt alo you can do

Thank you for your answer,

Unfortunately, upgrading my setup isn’t an option yet.

But on the bright side, I installed the latest Citra Canary and the game works perfectly fine (so far) on it.
Don’t know what the difference is between the two versions that caused this but I’m not complaining :smiley:

Glad to see that using Canary works for you! :slight_smile:

GL_VERSION: 4.3.0 - Build
This driver is severely out of date. But since you said that you’re on a proprietary driver, we can get around that by manually installing a legacy driver first, and then updating to the latest GPU driver available:

To update, download win64_25.20.100.6373.zip from Legacy Intel® Graphics Driver for Windows® 10
Mirror download: https://downloadmirror.intel.com/28289/a08/win64_25.20.100.6373.zip

Then follow this guide to install it: https://www.howtogeek.com/343287/how-to-fix-the-driver-being-installed-is-not-validated-for-this-computer-on-intel-computers/

Now you should be able to install the latest DCH drivers directly:
Download and install gfx_win_101.2121.exe from Intel® 6th-10th Gen Processor Graphics - Windows
Mirror download: https://downloadmirror.intel.com/774409/gfx_win_101.2121.exe

You don’t know what you’re talking about. Integrated graphics, so long as they meet Citra’s minimum graphics API requirements, work just fine. Their drivers simply need to not be from 3+ years ago. Please don’t misinform users out of ignorance.

My bad, just trying to help out :frowning:

The gesture is appreciated, but giving uninformed advice to users will not help anyone.

Unrelated, but is there somewhere for dummy log files that i can look through and try to evaluate for practice?

Not exactly. I’ve thought about making a resource similar to that in the past, however with how active development has been recently, it’s been difficult to make one that doesn’t immediately go out of date. For better or for worse lol

Best way I’ve found is to look at log files, see what experienced people like myself, autumnburra or tywald say about it, and then ask them how they came to that conclusion. Through that, you can steadily learn what means what.

Thanks for your reply, i’ll try doing that in the future to (attempt to) help the community. Hopefully im not wrong in future :slight_smile:

1 Like

Thanks for your reply

ive updated my driver accordingly, it now has the latest version from 2022 and there are not problems so far :smiley:
(tho it keeps telling me to update to a ‘newer’ driver from 2020, probably that old proprietary one so im going to ignore it.)

thank you so much for your help, i hope the new driver improves some graphics issues im facing with my other games (i dont have time to check rn :frowning: )

There’s a chance that Windows will force “upgrade” the driver to the older one without your consent. If that happens, let us know. We have a couple ways we can prevent Windows from doing that again in the future.