Skip to content
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

Fix running blazium on blocked GPUs. #171

Conversation

WhalesState
Copy link

Patch from godot 4.4.

@jss2a98aj
Copy link
Member

jss2a98aj commented Dec 2, 2024

If this was cherry-picked, it does not appear that contributor information was kept intact.
Commit info is now mostly intact.

@WhalesState
Copy link
Author

If this was cherry-picked, it does not appear that contributor information was kept intact.

Those files are changing a lot, and I compare the godot master to blazium so i be able to see all the changes, we can update the authors file from 4.4 before we release to make sure we are crediting the contributers properly.

@WhalesState WhalesState force-pushed the fix-running-blazium-on-blocked-GPUs branch 5 times, most recently from 52165be to aa692ae Compare December 3, 2024 05:34
bruvzg and others added 14 commits December 3, 2024 11:45
Before it was a bit unclear on what was happening, since a display
server has to fail to fall back and so the user would be left with an
error _and_ a (hopefully) running game.

Should make the experience more pleasant on Linux/BSD now that we have
two display servers.
Before, they would always complain even if there was no attempt at
initializing them (e.g. because there's no X11 display).

While we're at it, this patch also adds a specific message for OpenGL ES
and rewords "OpenGLES" to "OpenGL ES" in an error, for consistency
(AFAIK we either say "GLES" or "OpenGL ES").
This brings it to parity with the X11 backend.
Godot checks if there's Vulkan or GLES3 support.
If no support is found, it shows an error message.

However the code for this error message is left out when building with
opengl3=no
@WhalesState WhalesState force-pushed the fix-running-blazium-on-blocked-GPUs branch 2 times, most recently from 6ab8000 to 012c604 Compare December 3, 2024 10:20
@WhalesState WhalesState force-pushed the fix-running-blazium-on-blocked-GPUs branch from 012c604 to 5e53efc Compare December 3, 2024 10:39
Copy link
Author

@WhalesState WhalesState left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed and removed the RenderingContextDriverMetal from display_driver_macos.mm.

@jss2a98aj Thank You for helping and many thanks to the authors of the commits ^

@WhalesState WhalesState marked this pull request as ready for review December 3, 2024 10:44
@jss2a98aj jss2a98aj merged commit 932319a into blazium-engine:blazium-dev Dec 4, 2024
22 checks passed
@WhalesState WhalesState deleted the fix-running-blazium-on-blocked-GPUs branch December 4, 2024 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.