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

Problem with Materials in Android #63218

Open
Tracked by #63198
ismailgamedev opened this issue Jul 19, 2022 · 7 comments
Open
Tracked by #63198

Problem with Materials in Android #63218

ismailgamedev opened this issue Jul 19, 2022 · 7 comments

Comments

@ismailgamedev
Copy link

ismailgamedev commented Jul 19, 2022

Godot version

3.4.4

System information

Smasung Not10+ Gles2

Issue description

There is no problem when I test it on the computer, there is no problem on my teammate's phone, but I tested it on 2 Samsung phones and the materials on them are like disco balls.All of the animated objects I added have this problem, they were all downloaded from different sites
SmartSelect_20220715-014844_Hunting Simuilator

Screen_Recording_20220720-000341_Hunting.Simuilator.mp4

Steps to reproduce

All of the animated objects I added have this problem, they were all downloaded from different sites.

Minimal reproduction project

No response

@Calinou
Copy link
Member

Calinou commented Jul 19, 2022

@ismailgamedev Please upload a minimal reproduction project to make this easier to troubleshoot.

Also, try disabling octahedral compression on all animated objects in the Import dock, click Reimport and export your project to Android again.

Smasung Not10+ Gles2

That device is available with both Snapdragon (in USA and China) and Exynos (in Europe and Latin America). Which SoC does it have? This is important to know, as they use different GPUs with different graphics driver bugs. You can check this information in the device's settings.

@ismailgamedev
Copy link
Author

@ismailgamedev Please upload a minimal reproduction project to make this easier to troubleshoot.

Also, try disabling octahedral compression on all animated objects in the Import dock, click Reimport and export your project to Android again.

Smasung Not10+ Gles2

That device is available with both Snapdragon (in USA and China) and Exynos (in Europe and Latin America). Which SoC does it have? This is important to know, as they use different GPUs with different graphics driver bugs.

Samsung not10+ Exynos

@ismailgamedev
Copy link
Author

@ismailgamedev Please upload a minimal reproduction project to make this easier to troubleshoot.

Also, try disabling octahedral compression on all animated objects in the Import dock, click Reimport and export your project to Android again.

Smasung Not10+ Gles2

That device is available with both Snapdragon (in USA and China) and Exynos (in Europe and Latin America). Which SoC does it have? This is important to know, as they use different GPUs with different graphics driver bugs. You can check this information in the device's settings.

I tried what you said but it didn't work

@ismailgamedev
Copy link
Author

unknown-4
it should look like this

@ismailgamedev
Copy link
Author

ismailgamedev commented Jul 19, 2022 via email

@ismailgamedev
Copy link
Author

[SOLUTION] The solution for this is issue is to change the following value in the project settings: Project Settings >> Rendering >> Quality >> Skinning: Disable both values "Software Skinning Fallback" and "Force Software Skinning". It now looks fine on mobile device too.

@lawnjelly
Copy link
Member

Unfortunately this isn't a solution, it is a workaround.

If there is a bug in the software skinning path, we would really benefit from an MRP (minimum reproduction project) so we can debug and fix it. Particularly anything using blendshapes could be a problem, if I remember right. pouleyKetchoupp originally did the software skinning but I'm sure me and @clayjohn and others can debug / fix problems. 👍

BTW forcing hardware skinning is a great idea right until your players try and run the game on hardware that doesn't support it, which is why there is a fallback! 😁

@lawnjelly lawnjelly reopened this Jul 26, 2022
@lawnjelly lawnjelly added this to the 3.x milestone Jul 26, 2022
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

4 participants