-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hypersensitive accelerometer and gyro #2100
Comments
Same issue here, but overall awesome work! |
This issue can be fixed by replacing the code found in browser/vendor/borismus/webvr-polyfill.js with the code found here: https://github.com/waskosky/webvr-polyfill/blob/master/build/webvr-polyfill.js This is related to something that changed in newer versions of Chrome only. I learned about the specific issue here: aframevr/aframe#3476 When I discovered how much work it would be to update webvr-polyfill.js entirely to the latest version, I forked version 9.41 and updated that one instead with the necessary changes. I am hesitant to make this a pull request because I would say this is NOT the correct solution long term, since webvr-polyfill.js really needs to be updated to the latest version 100%. |
Thank you for your reply. Any way this can be implemented in the online version of Patches? (Patches.vizor.io) |
Since it seems like they have no one checking this github page, I assume you might have to get in contact with one of the people who would have access to update the Patches site, such as maybe someone mentioned here: https://www.crunchbase.com/organization/vizor-io It looks like their company might actually be rebranded as "Pixelface" now, and that the previous CEO left the company in November 2018 https://www.linkedin.com/in/kaarlo/ Actually this person seems to have current access https://github.com/esaruoho |
Fixes "Hypersensitive accelerometer and gyro" vizorvr#2100
Chrome, Android 9, Samsung Galaxy S8,
Webvr is very jittery, as if sensor data was multiplied ten times. Native vr acts normally.
The text was updated successfully, but these errors were encountered: