New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No 3D rendering(black area) on macOS #155
Comments
@grexe As a workaround you can comment the Line 350 in e41d872
Build and run again |
This is the output I get (using MacOS 12.6 (21G115)):
will try the code change later. |
Hello @HuguesDelorme & @grexe I was experiencing this same issue on MacOS 13.0.1 (22A400), I followed your advice to comment out the block in main.cpp under the comment "// Use QOpenGLWidget if possible" All is working fine now. Looking good. |
@HuguesDelorme comment fixed it, on OS X Big Sur. Thanks! |
@zambetti and @grexe |
@HuguesDelorme I have just downloaded and built the latest version, and I can confirm the fallback widget works on my machine. Compliments on this nice application. |
Hi! I had the same issue with the black screen. I tried the fallback widget option (i.e. I turned it off and restarted
(roughly lines 392-408) fixed my problem. Now, I can see the model. I am on Ventura 13.1, Apple M1 chip, built |
@andrsd |
The fallback widget was originally ON. I believe that's the default (?). That's when I had the issue with black screen, so I went to look for the cause and found this issue. I can try again. |
I tried a clean build of c85fe27, made sure the |
@andrsd mayo/src/app/app_module_properties.cpp Line 87 in c85fe27
I don't like this option, it's preferrable to fix the OpenGL framebuffer rendering with Qt for macOS |
This is a pure guess and I might be totally wrong, but could it be that because |
@andrsd Line 394 in 925403f
But for some reason this could fail on the very first execution of Mayo |
Reported by @grexe in issue #151
Notice that some other user(@livigni) mentionned Mayo to run correctly on macOS(see #67 (comment))
The text was updated successfully, but these errors were encountered: