playcanvas / playcanvas/engine

Particles cause rendering corruption on Samsung devices with Chrome)

Open
#3,353 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: graphics
Dominant language
JavaScript
Stars
16.8k
Forks
2k
Avg merge
4h 32m
Merged PRs (30d)
222

Description

Project: https://playcanvas.com/editor/scene/1198009

Video (Samsung S7 (Chrome 91.0) on the left, Google Pixel 2 XL (Chrome 91.0) on the right)

https://user-images.githubusercontent.com/16639049/126500059-11bdb0c9-9c05-4896-b6dd-2df108e56bcd.mp4

This only happens (so far) if device pixel ratio is enabled and only with particles. It looks related to the lifetime of the particle which is at 1 sec.

Tried browser stack with Samsung S20+ which shows a similar issue. I believe that it's actually doing the same thing as the S7 above but the video compression from Browser Stack to remote screen is making it 'blocky' and screen tearing. The video framerate/compression is not keeping up with the flickering effect shown above on the S7:

https://user-images.githubusercontent.com/16639049/126500321-544b749b-a26c-4c2e-87a9-06621a7daca9.mp4

Nothing shown on the browser log

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked PlayCanvas scene and reproduce the corruption on a Samsung device using Chrome with device pixel ratio enabled and one-second particle lifetimes. Compare the result with the Pixel 2 XL recording and check whether browser logs remain empty. Done means particle rendering is stable on the affected Samsung devices without regressions on the comparison device.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.