Object stutters/bounces on click.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
I am having a problem with the sun in this pocket universe:
https://michaeljcole.github.io/n-body-wasm-webvr/
- A-Frame Version: 0.9.2
- Platform / Device: Version 77.0.3865.75 (Official Build) (64-bit) Linux, Firefox on Android
- Reproducible Code Snippet or URL: https://github.com/MichaelJCole/n-body-wasm-webvr
Moving the cursor to point at the sun (turns green) should cause 10 "debris" to be spawned and start their spinny lives.
The sun is created here
That code says stars get some extra events.
The declared events (turning green) don't prompt the bounce.
The debris-listener doesn't change the location of the star.
When the debris listener fires on Chrome the sun bounces down then back. It's an anti-immersion artifact :-)
On Firefox for Android, when this happens there is a single frame with just the green sun. All the other bodies in the parent collection are not rendered. Only the green sun, dropped halfway down to the plane but not resized. The elements outside that collection (sign, plane, camera) appear undisturbed.
This was a fun demo to put together. Creating scenes in Aframe is much more fun than passing arrays in WebAssembly :-)
Any ideas how to prevent this stutter?
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 reproducing the behavior at the linked demo URL, then inspect src/nBodyVisualizer.js and the parent collection in src/index.html. Compare the click/debris event behavior across Chrome and Firefox for Android; done means the sun and other bodies render without the bounce or single-frame disappearance while debris still spawns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ar-vr-xr
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100