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

Particle system broken on Samsung Galaxy S10 #3460

Closed
CMRDX opened this issue Sep 7, 2021 · 17 comments
Closed

Particle system broken on Samsung Galaxy S10 #3460

CMRDX opened this issue Sep 7, 2021 · 17 comments

Comments

@CMRDX
Copy link

CMRDX commented Sep 7, 2021

We are currently experiencing that the PlayCanvas particle system behaves incorrectly on specific Samsung devices, namely Galaxy S10, Galaxy S10+ and Galaxy S10e with Android 11 and Chrome 93.0.4577.62

The corresponding Forum post can be found here (including videos and a link to our test project):
https://forum.playcanvas.com/t/particle-system-broken-on-samsung-galaxy-s10/21787

@mvaligursky
Copy link
Contributor

Possibly related to #3415

@yaustar
Copy link
Contributor

yaustar commented Sep 7, 2021

FYI: Cannot reproduce on a Galaxy Fold 3

@yaustar
Copy link
Contributor

yaustar commented Sep 7, 2021

I couldn't reproduce this on the Browserstack S10+ or any of the Samsung devices in our remote device lab.

Wondering if it's specific to the Exynos CPU and not the Snapdragon variant.

@CMRDX Are your devices the Snapdragon or the Exynos variant?

@CMRDX
Copy link
Author

CMRDX commented Sep 7, 2021

The device seen in the Video (S10e), as well as the S10+ is featuring a Exynos 9820 2.73GHz.
rn_image_picker_lib_temp_d859749c-cb0a-459d-b8d2-f43db297eb33

@yaustar
Copy link
Contributor

yaustar commented Sep 7, 2021

That may explain why my Fold 3 doesn't have the issue, it's using a Snapdragon 🤔

@leonidaspir
Copy link
Contributor

leonidaspir commented Sep 7, 2021

I've tried it on a Samsung S10 with the same CPU and I am getting the same issue on the project provided on the forum.

@yaustar
Copy link
Contributor

yaustar commented Sep 7, 2021

@CMRDX or @leonidaspir Can you try running this with WebGL 1 forced, ie: https://launch.playcanvas.com/1225034?debug=true&webgl1=true

This runs a different code path and will help narrow down the issue.

@leonidaspir
Copy link
Contributor

Works as expected when running with WebGL1.

@CMRDX
Copy link
Author

CMRDX commented Sep 8, 2021

@yaustar We got the same result as @leonidaspir. Seems to work as expected when enforcing WebGL 1.

@yaustar
Copy link
Contributor

yaustar commented Sep 8, 2021

Thanks, that helps with extra information/debugging.

We are working on getting a device to replicate the issue.

@yaustar
Copy link
Contributor

yaustar commented Sep 17, 2021

Tried on multiple Exynos CPUs #3415 (comment)

No joy in reproducing the issue :(

@marcusx2
Copy link

marcusx2 commented Dec 6, 2021

I'm taking the opportunity to report how the particles show up on a Samsung Galaxy S10 I got my hands on.

https://playcanvas.github.io/#/graphics/particles-snow
Capture d’écran 2021-12-06 à 15 53 22

https://playcanvas.github.io/#/graphics/particles-spark
Capture d’écran 2021-12-06 à 15 53 34

@yaustar
Copy link
Contributor

yaustar commented Jan 13, 2022

Reported not rendering correctly on RedMi 9 Prime device: https://forum.playcanvas.com/t/dat-cube-my-first-game-with-playcanvas-underdev/23757/7?u=yaustar

@yaustar
Copy link
Contributor

yaustar commented Jan 13, 2022

Reported not rendering correctly on Xiaomi Note 8 Pro https://forum.playcanvas.com/t/i-have-particlesystem-mobile-problem/23531/3?u=yaustar

@yaustar
Copy link
Contributor

yaustar commented Mar 22, 2022

As we think this is a hardware driver issue, we've created a workaround that forces using the CPU on ARM based Samsung devices: #4147

I expect this to go out with engine 1.53

@yaustar
Copy link
Contributor

yaustar commented Apr 18, 2023

Looks like this isn't limited to Exynos CPUs but it's related to the GPU used which is Mali based.

See thread: https://forum.playcanvas.com/t/particles-not-rendered-on-amazon-fire-tablet-hd-8/30660

@yaustar
Copy link
Contributor

yaustar commented Apr 20, 2023

Closing this as this is no longer reproducible. See PR #5255

@yaustar yaustar closed this as completed Apr 20, 2023
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

5 participants