-
Notifications
You must be signed in to change notification settings - Fork 26
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
Black screen in Gngeo on macOS #9
Comments
Hi thanks for the report, it might have broken something in https://github.com/dciabrin/gngeo (unlikely) or in #9 (more likely). I'm going to compile locally and will try to figure it out. Do you mind telling me which version of macOS you're running on? |
10.14.1 on both computers, although the build that works was built on 10.14.0, in case something has changed between macOS versions. |
OK I was running 10.14.0, upgrading to 10.14.1 before I recompile. |
Hmmm OK with my previous build (which I believe was working fine) I'm having the same black screen symptom when running on 10.14.1. |
Probably related to https://bugzilla.libsdl.org/show_bug.cgi?id=4272 |
Yes, when you run gngeo with the glsl blitter, you have the ability to resize window. Doing so fixes the black screen and rendering starts to appear, as reported in the bugzilla mentionned above. Unfortunately, latest stable sdl2 in brew does not fix that yet (2.0.8 as I'm writing that comment) |
Right. Moving the window (as mentioned in the bugzilla issue) also works. Thanks for your help, at least with this workaround it's usable again :) |
Closing the issue now as the issue doesn't reproduce on the latest macOS 10.15. Tested with the pre-built binaries available in brew (see #31). |
After October's WSL fixes, building the devkit on macOS results in a Gngeo that doesn't draw anything. Keyboard input still works (e.g. pressing esc + up + enter quits the app)
I'm backtracking through the commits now to see what breaks it, but I could reproduce this on my other Mac which already had a working ngdevkit from before.
The text was updated successfully, but these errors were encountered: