look-controls component generates very shaky moves on older devices
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
When using older devices, on version 0.9.2, the scene moves very slowly but remains steady when moving the phone, which seems fine to me. On version 1.0.4, the scene reacts well to the phone moving but the display is super shaky, it's impossible to get a steady image even without touching the phone. Is there a way to get the previous behaviour back or to be able to completely deactivate the device motion when the device is unable to follow and just use the dragging to move the scene?
What is weird is that the phone has the DeviceMotionEvent and DeviceOrientationEvent but they just don't work properly, and I don't know how to detect this...
- A-Frame Version: 1.0.4
- Platform / Device: Android webview on ASUS X008D, X008AD, Z00VD, Samsung Galaxy A3
- Reproducible Code Snippet or URL: shaky 1.0.4 : https://aframe.glitch.me/
- Working version : 0.9.2 https://brick-apple-diadem.glitch.me/
I noticed a change between versions so I consider it both an A-Frame issue and a support request so I also posted it on stackoverflow but without success at the moment : https://stackoverflow.com/questions/62347897/a-frame-look-controls-very-unstable-on-older-devices
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
Reproduce the shaking with the linked A-Frame 1.0.4 and 0.9.2 examples on the listed older Android devices, then investigate the look-controls component and its DeviceMotionEvent and DeviceOrientationEvent handling. Done means establishing a reliable behavior for devices with unstable motion sensors, including whether dragging can be used instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100