godot: GLES2 and default environment (ProceduralSky) cause a crash on some hardware
Godot version: v3.1.alpha
OS/device including version: Windows 10 Intel HD Graphics - OpenGL ES 2.0
Issue description: When I create a new project and edit it, the explorer freezes and then Godot closes.
Steps to reproduce: Create a New Project and edit it.
Workaround: Go to the project directory, open the file called project.godot and remove this line:
[rendering]
environment/default_environment="res://default_env.tres"
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 36 (20 by maintainers)
Commits related to this issue
- Actually respect the low quality cubemap filter on mobile, should fix crashes on mobile for #21551 but not sure on intel. — committed to godotengine/godot by reduz 6 years ago
with
default_env.tresI could reproduce the crash at start with my iPhone 4s 100%. but not anymore. 😃This is probably fixed now, but just in case give it a test again…
@akien-mga I think this bug became a mix up of things, the title mentions:
GLES2 and default environment (ProceduralSky) cause a crash on some hardware
I actually did fix this bug and should no longer be a problem on mobile.
However, all I see afterwards are reports that GLES3 driver does not work on old-radeons. I think this is an entirely different issue. I would like to know from such people (including @Zireael07, @Akira1San and @Vikram1323) if this works in GLES2 or the issue is exclusively GLES3 only.
As there is some confusion on this issue between GLES3 and GLES2 issues, and the original issue was fixed for many users, I propose to move the remaining cases (@Zireael07, @Akira1San) to @Vikram1323’s new issue: #25482.
I cannot use GLES2 (crashes) with default_env.tres, AND I get the errors on GLES3. If I delete default_env.tres, I can use GLES2 fine.
I switch to a desktop pc and can no longer test with the laptop.
What coincides? @Vikram1323’s error log above just means that the drivers can’t start GLES3, it has nothing to do with GLES2 and default environment.
@akien-mga: They coincide though, maybe they’re related?
This issue is about GLES2, not GLES3 driver issues.
@Vikram1323: I get the same errors on my Radeon 6630M currently.
P.S. Those are the drivers I am running: https://www.dell.com/support/home/pl/pl/rc1078552/drivers/driversdetails?driverid=8v6kh
Yes I know, ancient, but this laptop is a switchable graphics laptop so trying to update drivers completely breaks the switchability and/or introduces BSOD at startup.
I tried this on a very old Sony Vaio with an hd 6370m and latest drivers (which are quite ancient) and it works fine both with GLES2 and GLES3. I honestly have no idea what else I can do.
I will add that, unfortunately, it seems to depend not only on hardware, but also on drivers (for the last year or so, I ran unofficial drivers and did NOT have the issue, but now that I got the computer back from repairs with a new card, I am back to official Dell drivers and I do have the issue now)
Reopening as it’s still not fixed for some hardware.
On Radeon 6630M (and Dell’s official drivers), I am having this crash in beta 1.
I have a crash with the environment too. v3.1.alpha 5 OS Win 7, AMD Radeon hd 6370m
A ton of duplicates being reported, as well as, why do we load default_env.tres in 2D projects?