Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
upgrade version of `webvr-polyfill` dependency
See original GitHub issueI’m filing this to separate the issue of upgrading webvr-polyfill from fixing the source-map JS error raised in issue #54.
From Slack:
caseyyee [10:48 PM] @cvan ok, looks like with the polyfill, all the desktop mouse stuff was removed and they just use orbit controls on desktop. it doesn’t even return any polyfilled vrdisplays so it’s basically strictly for mobile only
cvan [10:06 PM] the new one has updates for the Sensor API cvan [10:06 PM] devicemotion is being deprecated cvan [10:06 PM] and it fixes a few 1.1 compliance issues
caseyyee [10:54 PM] Yeah, that was my thought. Provide some kind of sensible desktop usage. maybe some FPS controls. is there any major reason to use the new polyfill? I can update the polyfill and add back some default controls as a update. so do that after we push to the asset store.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Confirmed with Reilly that the
rotationRatechange is in m66, not m65, tracking immersive-web/webvr-polyfill#307@delapuente given #125, let us know if you have the bandwidth to work on this. if not, we’ll get it done in the next milestone between @caseyyee and myself. thanks!