search

toji / chrome-webvr-issues

Stub repository for tracking bugs related to Chrome's experimental WebVR support
53 stars 12 forks source link

Oculus Touch controllers don't populate hapticActuators #123

Closed jbaicoianu closed 6 years ago

jbaicoianu commented 7 years ago

controller.hapticActuators is an empty array for touch controllers. Would be nice to be able to make Touch controllers pulse!

toji commented 7 years ago

It's definitely on my TODO list. :) Probably best to expect it after the holidays, though.

carstenschwede commented 7 years ago

This would really be great. Looking forward to it.

toji commented 6 years ago

Closing all bugs in this issue tracker.

This repo was created to track issues in the experimental builds WebVR Chromium builds, which are now deprecated. Chrome Canary for Windows now has much more secure (and hopefully more performant) support for WebVR behind a flag, and Android has had WebVR support as an Origin Trial and behind a flag for a while now.

If this is a performance or correctness bug and you suspect it's still happening, please test against the latest Canary build of Chrome to verify and then file a bug at https://crbug.com. If this is an issue with the API, please review the latest WebXR explainer to see if it's been resolved and file a bug there if not.

Thanks for your interest in VR on the web! We've got an exciting year ahead of us! --Brandon