PlayCanvas renderer has no `TilesFadePlugin`, so tiles pop on level of detail changes

Open
#1,787 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

@mvaligursky is already working on this.

Since Nov 6, 2026.

  • #1786 by @mvaligursky — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript

Research direction

Read the existing TilesFadePlugin implementations in the three.js and Babylon.js renderers, along with TilesFadePluginBase in core, then review the PlayCanvas renderer in 3d-tiles-renderer/playcanvas. Issue #1786 adds the PlayCanvas fade plugin; this issue describes that work as already underway. Done means the PlayCanvas renderer has a TilesFadePlugin that fades tiles during level of detail changes.

Written by the indexing model from the issue text.

Description

The PlayCanvas renderer (3d-tiles-renderer/playcanvas, released in 0.5.4) has no fade plugin, so tiles pop in and out as the level of detail changes. The three.js and Babylon.js renderers both have a TilesFadePlugin, built on TilesFadePluginBase in core, and the PlayCanvas renderer has no 3d-tiles-renderer/playcanvas/plugins entry yet.

As discussed in #1764, plugins for the PlayCanvas renderer come as separate contributions after the renderer itself. #1786 adds the fade plugin.

Dominant language
JavaScript
Stars
2.5k
Forks
429
Avg merge
5d 22h
Merged PRs (30d)
12

Getting set up

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.

More from NASA-AMMOS/3DTilesRendererJS

All issues in NASA-AMMOS/3DTilesRendererJS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.