NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
GlobeControls: Understand why controls seem less responsive / slower depending on framerate
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
Even though pointer events are being used.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GlobeControls implementation and tracing how pointer events are processed relative to frame updates. Reproduce the responsiveness difference at different framerates, then identify the cause and define what consistent interaction should look like. The issue is old and provides no file or test reference, so expect to explore the controls and rendering flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100