(Worth noting that the page framerate is not throttled at that point, which means the submit frame is returning immediately.)
-
-
En réponse à @Tojiro
Oculus home launches in the background whenever an app starts using the SDK, so the user doesn't have to open it, just switch apps
1 réponse 0 Retweet 1 j'aime -
En réponse à @Tojiro
Then you click on the "Gear" icon and "Settings"pic.twitter.com/NJxYtmMDiW
1 réponse 0 Retweet 1 j'aime -
En réponse à @Tojiro
Then click the "General" tab, then the "Unknown Sources" slider/checkbox/thingypic.twitter.com/gqowtjnrOs
1 réponse 0 Retweet 2 j'aime -
En réponse à @Tojiro
Then a dialog pops up that warns you that Oculus takes no responsibility if you melt your brain.pic.twitter.com/FJ6TFQUwp4
2 réponses 0 Retweet 3 j'aime -
En réponse à @Tojiro
Once you click that, the WebVR app you're running in the background starts broadcasting to the headset immediately and everything works fine
2 réponses 0 Retweet 3 j'aime -
En réponse à @Tojiro
So that's a bit better than expected, actually, in that the "unknown" app can query the device like normal, it just can't present to it.
1 réponse 0 Retweet 2 j'aime -
En réponse à @Tojiro
But once the user tries to present it's 6 clicks (If you know where you are going) to get it to do what you wanted it to do.
1 réponse 0 Retweet 2 j'aime -
En réponse à @Tojiro
And at least two screens of reasonably scary sounding language warning about "Security, comfort, content, health, and safety".
3 réponses 0 Retweet 2 j'aime -
En réponse à @Tojiro
Which is still going to be a significant deterrent for your average non-technical user. (And if you are reading this tweet, that's not you.)
7 réponses 0 Retweet 5 j'aime
@Tojiro that's too bad, but hey @OpenSource_VR is here ;) Would really love to see its support into chrome.
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.