-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Implement automatic OpenGL fallback for GPUs that don't support Vulkan #57622
Comments
GLES3 is not fully implemented yet, and there's no automatic fallback to it when Vulkan is not supported (the error message is slightly misleading, but it is what will be valid once GLES3 is fully implemented). You can force using it with |
I've had the same problem when trying to launch godot 4 on linux. With the command-line flag I can indeed open Godot, but when that session opens another window (opening a project from the project overview or running a scene from the editor) then it tries (and fails) vulkan again |
Same as @jmdejong on Mac OS with an M1 proc. I tried building for x86 too, same errors, same behaviours if I use |
M1 Macs can run Vulkan with MoltenVK. You need to install the Vulkan SDK if you've built Godot from source, as per the documentation. |
As suggested in Zylann#387 This allowed 2 full Mac builds using these commands: ``` scons platform=osx arch=x86_64 --jobs=$(sysctl -n hw.logicalcpu) warnings=all tools=yes tests=no target=release_debug production=yes ``` ``` scons platform=osx arch=arm64 --jobs=$(sysctl -n hw.logicalcpu) warnings=all tools=yes tests=no target=release_debug production=yes voxel_fast_noise_2=false ``` - ( Also after having the VulkanSDK like mentioned here[1] and after deleting the `denoise` module which doesn't like ARM64) [1]: godotengine/godot#57622 (comment)
This has been partially addressed. The Project manager now defaults to GLES3 so users without Vulkan support can still open the engine and create a project. The team needs to discuss having an automatic fallback as it may not make sense. In other words, if a team creates a game that is designed for the Forward+ renderer, it will likely look broken if run from the gl_compatibility renderer as the gl_compatibility renderer lacks some features. So automatically falling back may not be helpful |
A way to make things NOT break would be godotengine/godot-proposals#6207 but, obviously, not something that can go into 4.0 |
I have something to add on continuing from my closed thread. As mentioned before, I've observed two kinds of projects that cannot be opened:
While both can be worked around, I think the GLES3 fallback should be applied to the former. Mabe this is the only other timer the fallback should be applied to. When it comes to other projects, the original owner may intend to render in Vulkan, so fallback may not be applicable there. However, they need to disclaim so that others won't clone them only to be greeted with the Vulkan error message. |
See #74159. We shouldn't unconditionally convert all 3.x projects to use OpenGL, as many rendering features are currently missing in that renderer (such as shadows in 3D). |
Closing in favor of godotengine/godot-proposals#8006. |
Godot version
4.0 alpha
System information
Windows 8 intel hd 4000 GLES3
Issue description
the Godot 4.0 alpha doesn't open in my intelHD4000 Although my device supports GLES3
Steps to reproduce
its not open
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: