Citra: Citra-qt no longer loading games on MacOS 10.13

Created on 16 Dec 2018 · 40Comments · Source: citra-emu/citra

Hello,
From nightly build 1149 d2003da and Canary build 1113 8b4b40d onwards (as I found out by testing previous builds) Citra would no longer load games, instead returning this message

Your GPU may not support OpenGL 3.3, or you do not have the latest graphics driver

My GPU does have support for OpenGL 4.1 and in fact Citra has worked fairly well with games on my system before these updates.
I could not find any significant changes in the changelog that might cause Citra to suddenly stop loading games. Here's the logs from the latest working versions and the latest releases as of this post for comparison.
citra_log canary 1112 (latest working).txt
citra_log canary 1113.txt
citra_log canary 1131.txt
citra_log nightly 1144 (latest working).txt
citra_log nightly 1149.txt
citra_log nightly 1154.txt

This is not an isolated case and I've seen multiple similar reports, but I saw nothing about those on this rep so I'm putting this up here.

Operating System: MacOS 10.13.6
CPU: 2,7 GHz Intel i5
GPU: AMD Radeon HD 6770M

Source

MojitoFan

👍6

Most helpful comment

Closing as the original issue is fixed.

FearlessTobi on 19 Sep 2019

🎉2

All 40 comments

If nightly build 1148 still works, then the cause must be out of our scope because the change from 1148 to 1149 is pretty unrelated and trivial af. It might be that travis CI and/or MacOS silently updated something. Could anyone compile citra locally and test if it still works?

wwylele on 16 Dec 2018

I tried with both the most recent nightly (1161) and also with build 1148 - neither worked for me, although this if my first time installing Citra so I can't guarantee this is the same issue.

I tried to build from source but it failed partway through. If there's anything I can do to help move this issue forward lemme know!

JNaftali on 24 Dec 2018

I too am trying Citra for the first time, and I had exactly the same experience. The latest available build fails with this OpenGL 3.3 error, although I've got a relatively modern Mac. I haven't tried build 1148 since there's no MacOS version available, but the next most recent MacOS nightly build is 1144, and that one works for me.

farmerpaul on 24 Dec 2018

I downloaded the latest Citra. It's showed "Your GPU may not support OpenGL 3.3, or you do not have the latest graphics driver". My iMac is the relatively modern. Please quickly to resolve it.

smallqiang on 25 Dec 2018

I have same issue. Downloaded update and now my games stopped working due to OpenGL 3.3 support. My drivers support 3.3... this is why I always prefer off the shelf because it actually works

FYI I've tried building locally with few different versions and nothing works unfortunately. Probably hard to predict that it would break, not blaming devs or anything. Just saying if I was paying and money was going toward a lovely testing/deployment strategy then probably issue would be caught before hand.

JasonDeJonge on 28 Dec 2018

👎5 😕3

I had the same problem on OS X 10.13.6, running the latest nightly build. Rolling back to nightly 1144 fixes the problem.

Craig-Janssen on 20 Jan 2019

10.13.6 meet this problem too

androidfans on 26 Jan 2019

Same problem in 10.13.2

jjant on 28 Jan 2019

Does this issue have a workaround by reverting to a previous build, or have previous builds been retroactively broken?

Sparen on 2 Feb 2019

As far as I know only the Qt frontend is broken in High Sierra, Citra itself does play games fine when launched from terminal commands.

MojitoFan on 2 Feb 2019

I'm able to run on Canary 1112 for now. Thanks for the heads up.

Sparen on 2 Feb 2019

All the latest builds do NOT work on High Sierra 10.13.6. Only version 1144.
Wondering when the latest version will be fixed.

DrConflict on 19 Mar 2019

I have the same issue.

System Specs:
macOS High Sierra: 10.13.6 (17G65)
Processor: 2 GHz Intel Core i5

Omega7343 on 19 Mar 2019

As far as I know only the Qt frontend is broken in High Sierra, Citra itself does play games fine when launched from terminal commands.

How did you managed to launch citra from terminal?

lAnatoliyl on 26 Mar 2019

Problem appears to be introduced by QT5.12. Built master against it and reproduced the problem on 10.13.
Tried with QT5.11 and the problem is not present.
QT5.12.0 was released 2018/12/06, so with a little delay for brew to update, it matches the dates of the nightly builds that no longer work.

So citra will have to fix the QT version that is built against and not rely on brew (or make their own tap for 5.11).

Command line citra works because its window is not provided by QT.

yerejm on 31 Mar 2019

I'm glad that the source of the issue has been found, at the very least. Being stuck on Canary 1112 really sucks, especially when building from source fails due to the SDL Joystick library and since the command line version lacks so many UI features.

Sparen on 18 Apr 2019

Could someone test if the problem persists on the very latest Canary build?

FearlessTobi on 18 Apr 2019

Canary 1298 still has the problem. Just tested.

Sparen on 18 Apr 2019

Thanks for the report.

FearlessTobi on 18 Apr 2019

To revert qt5 back to the last 5.11 brew in the continuous build, insert in citra/.travis/macos/deps.sh after line 3 "brew update":

curl -s https://raw.githubusercontent.com/Homebrew/homebrew-core/5eb54ced793999e3dd3bce7c64c34e7ffe65ddfd/Formula/qt.rb > /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/qt.rb

Those building from source should also be able to do this manually to get a citra compatible QT5.

yerejm on 20 Apr 2019

👍1

I have the same problem on a Macbook Pro Late 2011 High Sierra
(Intel HD Graphics 3000, i7, OpenGL 3.3)

The thing is I can launch games with command line in the terminal. I can run Ocarina of Time 3D smoothly. However, my PS4 controller doesn't work, and I don't know if it's because i'm not running it through the QT GUI, or because my configuration is wrong (I even tried to change settings in conf files, but it didn't work)
So the problem should be related to the Qt5.

I've also tried the fix by yerejm, and building the app, but it didn't work either. It was my first time using CMake, and i didn't try it again, so maybe it's my fault here

"Issue openend on 16 déc 2018" : I think I will play on Citra on my Android phone first

NielsG98 on 17 May 2019

@yerejm's solution didn't work for me, but I derived a different temporary solution from it that did work.

Run curl -s https://raw.githubusercontent.com/Homebrew/homebrew-core/5eb54ced793999e3dd3bce7c64c34e7ffe65ddfd/Formula/qt.rb > /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/qt.rb in console, then brew reinstall qt5; brew pin qt5.
Note that __this will prevent Homebrew from upgrading QT5 to newer versions__.
Then build from source as usual.

It will build with the non-broken QT5 version and work just fine.

SmiVan on 23 May 2019

@gerger05 just open the terminal, use the cd command to move where you have the citra-qt.app and citra files (cd "Applications/citra/canary" for me)
After that just type ./citra "path/to/your/game.3ds" and it will launch your game

NielsG98 on 25 May 2019

@SmiVan Thanks it's working, but i will have to build every time there is a new version if I want to stay updated ?

NielsG98 on 26 May 2019

Of course now the performance in my custom build is worse than when i was testing with the command line in the latest canary version.
Well I can use the GUI and my controller now, but i have 20fps and I even have some graphics issues (link pants is black, his horse in the cinematic is invisible, etc.)
I tried to tweak the hardware shader settings, but it doesn't work.
Strangely I didn't had this with the command line in the canary version.

NielsG98 on 30 May 2019

To anyone who wants to try the nightly 1144, download it here. Make sure to turn off updating in the settings, at least for now.

It is a very strange bug, though. Has it been reported to QT5? Plenty of things have changed between version 5.11 and 5.12. I browsed around on the bug tracker but couldn't find anything relevant. Of course, making a bug report at this stage would be vague since we have very little information, but it might be difficult for non-QT5 developers to track this problem down?

msikma on 9 Jun 2019

Well, I don't want this old version.

NielsG98 on 10 Jun 2019

Even if you don't want to use an older version, that's all we have for now until the issue is fixed. Whether it is fixed by a temporary workaround or by a permanent solution, it will take time and will need visibility with regards to the importance of this issue.

Sparen on 10 Jun 2019

👍1

I don’t have a Mac, so I can’t do this myself.

You can use a git bisect to find the offending commit in Qt. The diff link already posted (https://github.com/qt/qt5/compare/5.11...5.12) shows 461 commits, so the binary search to find the commit introducing this issue will need 9 iterations.

Each iteration step consists of compiling Qt from source and then linking Citra against the local Qt build.
When you found the offending commit, it’ll be easier to report it to the Qt project.

luziferius on 3 Jul 2019

👍1

@luziferius Unfortunately my computer is too weak to recompile Qt5 nine times within any reasonable time-frame, but with some research I found this old QT bug report which sounds pretty similar to what's happening here, is it related perhaps? Although it was reported in QT 5.10, so that's probably unrelated.

SmiVan on 5 Jul 2019

Given that Citra seems to have explicitly dropped support for High Sierra with the latest releases of its macOS application, is it safe to assume that this issue has been abandoned?

Sparen on 13 Aug 2019

Given that Citra seems to have explicitly dropped support for High Sierra with the latest releases of its macOS application, is it safe to assume that this issue has been abandoned?

Where did you hear about that? The FAQ still says that

Citra is actively tested and supported on [...] macOS 10.13 High Sierra or higher.

And it compiles and launches just fine on High Sierra, without any deprecation warnings, unless I'm missing something.

SmiVan on 25 Aug 2019

Given that Citra seems to have explicitly dropped support for High Sierra with the latest releases of its macOS application, is it safe to assume that this issue has been abandoned?

Where did you hear about that? The FAQ still says that

Citra is actively tested and supported on [...] macOS 10.13 High Sierra or higher.

And it compiles and launches just fine on High Sierra, without any deprecation warnings, unless I'm missing something.

The official build for end users now requires Mojave or later. Users on High Sierra who used the Citra automatic updater discovered that Citra's update actually bricked the application, preventing it from being launched at all.

I'm perfectly sure that you can build Citra from the source code and get a functioning executable, but if the official Nightly/Canary citra-qt application can't be launched on macOS High Sierra, I think it's safe to say that to a typical end user, they'd think that Citra has dropped support for that OS.

Sparen on 25 Aug 2019

The official build for end users now requires Mojave or later. Users on High Sierra who used the Citra automatic updater discovered that Citra's update actually bricked the application, preventing it from being launched at all.

I'm perfectly sure that you can build Citra from the source code and get a functioning executable, but if the official Nightly/Canary citra-qt application can't be launched on macOS High Sierra, I think it's safe to say that to a typical end user, they'd think that Citra has dropped support for that OS.

It sounds to me less like dropped support and more like a buggy automatic updater/release package.
I guess we'll have to wait for a word from senior devs on the project regarding this.

SmiVan on 31 Aug 2019

As of Citra Canary 1471, this issue seems to have been resolved for macOS 10.13, and the application is also running as intended without prompting for an OS update. Please mark this issue as closed.

Sparen on 14 Sep 2019

👍2

As of Citra Canary 1471, this issue seems to have been resolved for macOS 10.13, and the application is also running as intended without prompting for an OS update. Please mark this issue as closed.

I can confirm that Citra Canary 1471 is working on macOS 10.13