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

GLES2: 3D scenes crash on Android (Mali T830, no OES_texture_float) #26902

Closed
ProbDenis opened this issue Mar 11, 2019 · 16 comments
Closed

GLES2: 3D scenes crash on Android (Mali T830, no OES_texture_float) #26902

ProbDenis opened this issue Mar 11, 2019 · 16 comments

Comments

@ProbDenis
Copy link
Contributor

Godot version:
Godot 3.1 RC1

OS/device including version:
Samsung Galaxy Tab A (2016), Android 8.1.0,

Issue description:
I'm getting crashes when trying to run 3D games/demos on Android in GLES2. The only debug output I'm getting is "R float texture not supported". GLES3 seems to work.

@akien-mga
Copy link
Member

Can you share a project that reproduces it?

@akien-mga
Copy link
Member

Are you using a CurveTexture?

@akien-mga
Copy link
Member

akien-mga commented Mar 11, 2019

Could you also enable Debug > Settings > Verbose Stdout and see if you get more details in adb logcat?

And maybe use the app OpenGL ES CapsViewer to get the list of extensions supported by your GPU. The app lets you upload them to a database that you can then link here.

@ProbDenis
Copy link
Contributor Author

I can reproduce it with the "Platformer 3D" demo. With Verbose STDout I'm getting the following output:
debug_output

@ProbDenis
Copy link
Contributor Author

Here's the report from OpenGL ES CapsViewer:
http://opengles.gpuinfo.org/displayreport.php?id=3450

@akien-mga
Copy link
Member

akien-mga commented Mar 11, 2019

Can you check adb logcat? There might be more details around those OpenGL errors.

It would also be useful to know the OpenGL ES extensions supported by that device, as reported by OpenGL ES CapsViewer. It doesn't seem listed yet in http://opengles.gpuinfo.org/
Edit: You just provided that.

@akien-mga akien-mga changed the title GLES2: 3D scenes crash on Android GLES2: 3D scenes crash on Android (Mali T830, no OES_texture_float) Mar 11, 2019
@akien-mga
Copy link
Member

akien-mga commented Mar 11, 2019

Could you try this patch? akien-mga@5976a52 (#26943)

You'll need to build the editor binary from that commit, and here's a matching debug APK (only armv7 lib included, but should work on your arm64v8 device, just make sure to tick armv7 in the export preset): Android debug APK (armv7)

@akien-mga
Copy link
Member

Here's another debug APK for #26943 with both armv7 and arm64v8.

@ProbDenis
Copy link
Contributor Author

Hm, this build made it even worse. It crashes immediately with no debug output at all. Still works with GLES3 though.

@ProbDenis
Copy link
Contributor Author

adb logcat is spamming the console with messages so fast that it's difficult for me to know what to look for, but I found this message:
OpenGLRenderer: Incorrectly called buildLayer on View: WorkspaceCellLayoutChildren, destroying layer...

@akien-mga
Copy link
Member

I see that my Samsung Galaxy S3 also doesn't support OES_texture_float, I'll see if I can reproduce the issue and debug further.

@akien-mga
Copy link
Member

Could you try https://framadrop.org/r/zpwgiaKLyL#vqtCStJXshsSLTwiBLv7IOvc3xgu6H9Edt9XwUd1g4g= ? It works well for me on the Samsung Galaxy S3. It's a target=debug build so it should provide a backtrace in adb logcat if it crashes.

Note that it might not fix all potential crashes on loading a 3D scene on that device, just the part we saw so far about R float texture not being supported.
If you're still testing with the 3D platformer, you might into another crash as described in #26943. Try also to change the physics engine to GodotPhysics, as I had a crash in Bullet on my higher end phone with that demo.

@ProbDenis
Copy link
Contributor Author

ProbDenis commented Mar 12, 2019

I'm still getting crashes, though maybe different crashes. This is the part of the log that might be interesting:

https://www.dropbox.com/s/wifizejds5k5wky/log.txt?dl=0

@akien-mga
Copy link
Member

Yeah that's the same crash I'm getting in #26943 (comment)

I think it's unrelated to what was fixed with #26943, so it might be worth opening a new issue about it. That new crash is specific to scenes with Skeleton.

@akien-mga
Copy link
Member

Fixed by #26943.

I'll open another issue for the Skeleton crash.

@akien-mga
Copy link
Member

I opened #26972 for the other crash.

@akien-mga akien-mga self-assigned this Mar 12, 2019
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

3 participants