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

Rigged Meshes causing crash on android (PowerVR GPU) #101668

Closed
alikabeer32 opened this issue Jan 17, 2025 · 4 comments
Closed

Rigged Meshes causing crash on android (PowerVR GPU) #101668

alikabeer32 opened this issue Jan 17, 2025 · 4 comments

Comments

@alikabeer32
Copy link

alikabeer32 commented Jan 17, 2025

Tested versions

  • Reproducible in 4.3.stable.flathub

System information

Android 14 - Godot 4.3.stable.flathub - PowerVR GE8320 GPU

Issue description

I'm new at this but I will try to mention everything I can so please bear with me.

  • I'm developing on Linux 24.04
  • I'm using 4.3.stable.flathub (I updated yesterday)
  • It works fine in my Godot editor on my PC.
  • Issue occurs on Samsung F04 (PowerVR GE8320 GPU)
  • Worked fine on Samsung S23 Ultra (Adreno 740 GPU)

Issue seems similar to #93406

It was supposedly fixed in #94835
But I'm still facing this.

I have a simple mesh of 12 vertices parented to a single bone.

When I launch on my phone (after exporting apk) it takes a long time to load. The game runs. But when I close and try to start the game again, it crashes. Until I clear cache and data. Exactly as mentioned in #94835

I'm using GL compatibility.

Any other detail I missed, please let me know.

Steps to reproduce

  1. Just launch a new project in godot 4.3.stable.
  2. Import any simple rigged mesh, even if it's one bone.
  3. export to android apk.
  4. Install on your phone (ideally one with PowerVR GE8320 GPU).
  5. It will launch fine. Close and launch again.
  6. Crash.

Minimal reproduction project (MRP)

bugtest.zip

Just export this project as apk

@shahriarlabib000
Copy link
Contributor

Could you try on 4.4.beta please

@alikabeer32
Copy link
Author

Could you try on 4.4.beta please

Yes I'm on it.

@alikabeer32
Copy link
Author

alikabeer32 commented Jan 17, 2025

Could you try on 4.4.beta please

Yes it did fix the issue. Thanks. So that bug fix wasn't supposed to be in 4.3? Sorry idk how this works.

@AThousandShips
Copy link
Member

Then this is a duplicate of:

And will be in a future release of 4.3.x, if you see the PR that solved this has a cherrypick:4.3 tag on it, this means it will be added to a future version of 4.3.x

Thank you for reporting

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