-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
Phone freeze on opening Scene with imported 3D model [GLES2] #25365
Comments
You need to enable |
@akien-mga About the rim option, is it also expected? GLES2 dont support rim? |
I guess not, but it shouldn't prevent the scene from loading, so that would be worth a bug report. |
@akien-mga Already test the rim, now the scene can be loaded and displayed with Beta 3 but the mesh not rendered instead. Check my referenced issue. |
Also reporting that this issue still reproduced with Beta 3 build. |
@reduz Unfortunately, this issue still reproduced in RC1 (haven't tried RC3 yet, will try it later), but instead of freeze my phone, it now crash the game. |
@reduz Today I tested it in Godot 3.1 stable it still crash, and if I test it several time in a row, sometimes it also freeze my phone. |
Godot version:
Godot 3.1 Beta 2 (GLES2)
OS/device including version:
Development:
OS: Windows 10
GPU: nVidia GeForce 520M
Test:
Asus Zenfone 5 (2014)
OS: Android
GPU: PowerVR SGX544MP2
GLES: 2.0.0
Issue description:
Just open project below, export, and install on android, play.
There are 3 scene in the game.
Scene C is a 3D scene with a box, plane, and environtment. This scene can be opened in my phone.
Scene A&B is the same as Scene C with addition an imported 3D model. It is a low poly model with skeletal animation. If i open this scene my phone freeze. The debugger not printing any error it just disconnected because my phone is freeze.
I also discover other issue while making this project.
is this expected behaviour?
If not then I'll make a separate issue.
Steps to reproduce:
Minimal reproduction project:
CharacterTest.zip
The text was updated successfully, but these errors were encountered: