Child of camera or controller in 0.9.0 stuttering
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
- A-Frame Version: 0.9.0
- Platform / Device: Android / LG X Power II / Samsung Galaxy S8
- Browser: Chrome m72
- Reproducible Code Snippet or URL: https://screeching-parade-1.glitch.me/
Code:
<html>
<head>
<script src="https://aframe.io/releases/0.9.0/aframe.min.js"></script>
</head>
<body>
<a-scene>
<a-box position="-1 0.5 -3" rotation="0 45 0" color="#4CC3D9"></a-box>
<a-sphere position="0 1.25 -5" radius="1.25" color="#EF2D5E"></a-sphere>
<a-cylinder position="1 0.75 -3" radius="0.5" height="1.5" color="#FFC65D"></a-cylinder>
<a-plane position="0 0 -4" rotation="-90 0 0" width="4" height="4" color="#7BC8A4"></a-plane>
<a-sky color="#ECECEC"></a-sky>
<!-- Camera + cursor. -->
<a-entity camera look-controls>
<a-cursor id="cursor" fuse="true"></a-cursor>
</a-entity>
</a-scene>
</a-scene>
</body>
</html>
I noticed the issue when I migrated to 0.9.0. Seems quite fine when I don't have a cursor (an entity) in front of camera in VR mode. I haven't noticed any console errors. Tell me if you want some additional information.
Video url: http://recordit.co/3VoWJqoBbc
Everything here looks fine except the cursor entity which looks like it's changing its relative position to the camera over time.
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 with the supplied reproduction URL in Chrome on an Android device and compare the camera in VR mode with and without the cursor entity. Investigate why the cursor changes its relative position and causes stuttering; done means the cursor remains stable and the stuttering is gone in the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ar-vr-xr, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100