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

Forward+ and Mobile modes open to black screen on macOS versions older than 10.15 #78891

Open
1234567890boo opened this issue Jul 1, 2023 · 2 comments

Comments

@1234567890boo
Copy link

Godot version

4.0.3.stable.official [5222a99]

System information

Macbook Air (13 inch, early 2017), Macos 10.14.6 ,2.2 GHz Intel Core i7 Broadwell, 8GB Ram, Intel HD Graphics 6000 1536 MB

Issue description

When I open a new projects in Forward+ or Mobile modes, the screen is black, but responsive.

For example, there is no spinning wheel instead of the cursor and the project doesn't say its unresponsive in the force quit applications menu. when I open the version control setting or anything else similar, it opens the menu, but it is black, other than the name bar.

Steps to reproduce

  • Open godot
  • press on new project
  • write the name
  • make a folder for it
  • select Forward+ or Mobile mode
  • press create and edit

Minimal reproduction project

GodotProjects.zip

@1234567890boo 1234567890boo changed the title Forward+ and Mobile modes open to clack screen Forward+ and Mobile modes open to black screen Jul 1, 2023
@Calinou
Copy link
Member

Calinou commented Jul 1, 2023

You need macOS 10.15 or newer to use Vulkan-based renderers in Godot, but you're on macOS 10.14. This is due to MoltenVK requiring macOS 10.15.

We should prevent choosing Forward+ or Mobile in the project manager if running a macOS version older than 10.15. OS.get_version() should be usable for this purpose.

@Calinou Calinou changed the title Forward+ and Mobile modes open to black screen Forward+ and Mobile modes open to black screen on macOS versions older than 10.15 Jul 1, 2023
@lostminds
Copy link

Perhaps something similar to #73999 could also be implemented for cases like this as well, in other words at least showing a system alert with information about the missing renderer support causing the black screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants