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
GLES2 and default environment (ProceduralSky) cause a crash on some hardware #21551
Comments
Can you run it from a terminal and paste the output (there should be error messages)? |
There it is
|
What version of Intel HD graphics do you have? Are your drivers up to date? |
@akien-mga I can confirm that @arnoldochavez problem existed on an old testing laptop I have and his solution worked. The drivers are up to date according to Intel (Version: 15.22.58.2993) |
@karroffel Seems to be an issue with some non-supported default environment stuff on GLES2 for ~2010-ish "Intel HD Graphics" IGPs (no number, those are before Intel started branding them 2000, 3000, etc.). @Zimakili has those specs (#20588 (comment)) so that's 5th gen "Arrandale"/0046 with barely OpenGL 2.1 support: https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Fifth_generation Not sure for @arnoldochavez, could you give precise specs about GPU and CPU? |
For my work office PC with "Intel HD Graphics 4400" changing default environment background mode to custom color solves the crash problem. |
Sorry for the late response @akien-mga, there are the specs: Report Date: 9/3/2018 |
HP Elitebook 2560p, core i5, 4Gb RAM, Graphic HD 3000 The same happened to me. The Godot 3.1 start fine, but the graphic card crash when try to start a new proyect or any proyect. Now I solved comenting the line: [rendering] in the file called project.godot. |
Editing title as it seems specific to |
Exported android app freezes at splash screen (Samsung Galaxy J5 and J3) or white screen with some artifacts is shown (Nvidia Tegra K1 tablet). It seems to be related to ProceduralSky applied in environment (when custom color is used android app runs fine). (#22656) |
… crashes on mobile for #21551 but not sure on intel.
This is probably fixed now, but just in case give it a test again.. |
with |
I have a crash with the environment too. |
Just downloaded the beta and I can confirm it now works fine! |
On Radeon 6630M (and Dell's official drivers), I am having this crash in beta 1. |
Reopening as it's still not fixed for some hardware. |
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) |
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. |
All the things I mentioned in #24962 + When I run Godot 3.1 beta 2 and when I run Godot 3.0.6 |
When I run Godot 2.1.5 console is blank. |
@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. |
This issue is about GLES2, not GLES3 driver issues. |
@akien-mga: They coincide though, maybe they're related? |
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. |
I posted that error because those who can run Godot properly and switch GLES are not having this error, only those who are having this problem get this error. Editing project: C:/Users/Vikram/Documents/GodotBeta/1 (C:::Users::Vikram::Docum
P.S: And yes I also think that they both coincide. |
I can create a new issue explaining everything and make a video because it is all related I guess. Just tell me what should I do because I love Godot Engine and I hate this error/ issue/ problem/ bug/ etc etc etc....... |
@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. |
I switch to a desktop pc and can no longer test with the laptop. |
@reduz My issue (#24962) got closed because it is same as this issue. So I (newbie) thought maybe this is the place to post it. After editing project.godot and then switching from GLES3 to GLES2 I got this OpenGL ES 2.0 Renderer: ATI Mobility Radeon HD 4300 Series
And my project is running. I hope this helps. |
I cannot use GLES2 (crashes) with default_env.tres, AND I get the errors on GLES3. |
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. |
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:
The text was updated successfully, but these errors were encountered: