playcanvas / playcanvas/engine

Mesh particle effect shows artifacts on first play on Samsung Exynos devices

Open
#4,602 0 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/project/975817/overview/samsung-mesh-particle-issue
Published build: https://playcanv.as/e/p/2e8igsHo/

  1. On a Samsung Exynos device press on animationUpdate button in the top right (particle effect is played on the engine animationUpdate event. This is to simulate when the collision event is fire when rigidbodies collide)
  2. See the particle effect give a frame of artifacts but only on the first time it is played. (repro rate is about 80%)
  3. Issue occurs on both WebGL 1 and 2
image

However, I noticed that if it is played on the frameend event, it is fine (at least from a remote device)

// initialize code called once per entity
OnFrameEnd.prototype.initialize = function() {
    this.entity.button.on('click', () => {
        this.app.once('frameend', () => {
            this.targetEntity.particlesystem.reset();
            this.targetEntity.particlesystem.play();
        });
    });
};

For the moment as this is likely a driver bug (see #3460), please use this as the workaround.

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 by reproducing the first-play artifact from the linked project on a Samsung Exynos device in both WebGL 1 and WebGL 2. Compare playback from the animationUpdate event with the frameend workaround, and review related driver behavior in issue #3460. Done means the first playback no longer shows artifacts, or the issue is narrowed to a documented driver limitation.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.