Camera is super sensitive to motion on Chrome Beta 66 on Android

[andree-rehnberg]

Description:
This issue makes the camera jump around like crazy, being super sensitive to any motion whatsoever.
I assume this issue is related to issue #3458 but instead of the camera moving slowly it moves far too quickly.

Here is a video showing the issue, the video was recorded with the phone held with stable hands.
https://vimeo.com/260723899

• A-Frame Version: 0.8.0
• Platform / Device: Chrome Beta 66 / Oneplus 5 (Android 8.0.0)

[dmarcos]

This is because DeviceMotionEvent.rotationRate units have changed from degrees per second to radians on Chrome m66

[jsantell]

Updating to the latest A-Frame contains an updated webvr-polyfill which fixes these issues -- not sure what A-Frame release contains these changes, though (but introduced after 0.8.0)

[raoelhulst]

Any idea when this will be solved? Thanks in advance.

[dmarcos]

@raoelhulst The fix that @jsantell has mentioned has shipped already. Update A-Frame to 0.8.2

[dmarcos]

@jsantell do you think we can close this issue?

[jsantell]

yeah, m65 will be replaced with m66 soon and polyfill has been updated with all issues

[raoelhulst]

Thanks man! It works 👍 .

[a5507203]

@dmarcos Is there any way to modify web-polyfill to newest version in Aframe 0.5.0? Since I have already built an large AFrame project with 0.5.0, a lot of thing need to change if i swap to new version of aframe. Thanks in advance.

[ngokevin]

You can try to build yourself. Clone the repo, checkout v0.5.0 tag, update package.json, npm run dist. YMMV

[revlity]

I am using A-frame 0.6.1. How can I fix this without updating to 0.8.0.

[jsantell]

What @ngokevin said is the only way, using the 0.6.1 tag:

You can try to build yourself. Clone the repo, checkout v0.5.0 tag, update package.json, npm run dist. YMMV

[jonwaterschoot]

I've been away for a while from A-Frame. Wanted to test some of my older experiments, but saw this issue. I went to the homepage of A-Frame and noticed the same issue with some of the examples there.
Using Chrome on a new ZTE Axon 7.

[dmarcos]

@jonwaterschoot With A-Frame 0.8.2 and Chrome m66?

[gabrieljbaker]

I noticed this on my Samsung s8 + last night. Aframe .8.2 and chrome m66.

[a5507203]

You can modify the web-vr at previous version of Aframe (just need to add a if condition). Look at the source code of the latest web vr, search keyword 'chrome'. It has a variable corresponding to version of chrome. gabrieljbaker <[email protected]>于2018年5月25日 周五00:46写道：

…

I noticed this on my Samsung s8 + last night. Aframe .8.2 and chrome m66. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3476 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARIG8G5kJyOyty3Po5eIsGEdxEHE6Bt9ks5t1sfVgaJpZM4Svx9I> .

[jayson04]

Hi @ngokevin I am beginner in git. Do you have a video instruction on how to make my own build like what you commented on May 3. Thank you.

[dmarcos]

This is fixed on A-Frame master

[ClosetGeek-Git]

Why is this issue still present on the A-frame demos at aframe.io? I'm still having this issue on the demos, and when I download and edit aframe version to 0.8.2+ (including 0.9.1) the only change is that gyroscope seems disabled and camera seems stuck in a diagonal view. What is the solid solution to these issues?

Pixel 3, tested using current versions of Chrome and Firefox Focus with the same results

[dmarcos]

What Chrome version? What demos? https://aframe.io/aframe/examples/ work fine for me in Chrome m74 and m76 (Canary),

[tinchoforever]

Samsung S8 & Chrome m74 here....
All examples.

[dmarcos]

Make sure you are on A-Frame 0.9.2. Examples work fine for me on Chrome m74 and Pixel 2 & 3: https://aframe.io/aframe/examples/

[dmarcos]

Also make sure you have the devicemotion APIs enabled. More info: #3976 (comment)

[marcusx2]

@dmarcos How do I fix this problem? Sorry, I don't even use aframe but when looking up on google about this problem this is the only lead I found. I tried downloading this project and searching for a fix, but coudln't figure it out. The Gyroscope api works fine but I can't use it because it only works on Android. So I am left with this DeviceMotionEvent.rotationRate, but the rotations are crazy, moving superfast everywhere. It's still broken.

[jsantell]

@marcusx2 this chunk of code in cardboard-vr-display controls the device motion in aframe, maybe a good place to start

[dmarcos]

@marcusx2 What is the problem? Do the A-Frame examples work for you? Make sure you are using A-Frame 1.0.4