Open caseyyee opened 8 years ago
I would also think that using a browser with webvr enabled, but without any devices found, should have the default controls that are surfaced when using a non-webvr browser.
I'm in the process of refactoring a bunch of stuff between boilerplate and polyfill. Everything that should work in both polyfilled and native mobile WebVR should probably go into the boilerplate. So it might make sense to move mouse/touch/keyboard panning into the boilerplate.
On Sat, Feb 20, 2016 at 5:11 PM dbuck notifications@github.com wrote:
I would also think that using a browser with webvr enabled, but without any devices found, should have the default controls that are surfaced when using a non-webvr browser.
— Reply to this email directly or view it on GitHub https://github.com/borismus/webvr-boilerplate/issues/82#issuecomment-186714562 .
would be greate if mouselook was specific to the individual canvas element, rather than document.body.
+1
+1 for this!
I would think that the behavior we want would be the same as when using cardboard devices. The headset orientation and position being applied while still being able to pan with the mouse/touch.