11-21-2021 I have been testing oculus quest 2 controllers with A-frame.
They were white in color but last night the suddenly changed to black? Why?
See:
Oculus quest 2 controller models do not properly loaded in A-Frame
Latest is in this GitHub issue:
https://github.com/aframevr/aframe/issues/4960
Seems to be an issue with the Oculus Quest 2 itself reporting the wrong profile.
Affects A-Frame, Babylon.js and Firefox Reality Browser environment (and probably som other things too).
Related
A-Frame by default provides the "enter VR" button at the bottom right of the screen. This is working fine on my desktop, and also in Firefox Reality on my Oculus Quest. But in Wolvic, instead of opening in the VR mode, I see 2 views/screens.
I got the same behaviour for several examples on glitch.com, this is 1 example: https://glitch.com/~aframe-vaporwave
Any idea what's causing this and/or how to fix this?
The example you pointed out uses a very old version of A-Frame (0.5.0) based on the old WebVR API that browsers no longer ship. Make sure you're using 1.3.0 or newer that comes with WebXR support.
All the A-Frame examples should work on Wolvic:
https://aframe.io/aframe/examples/
Can also use the official glitch A-Frame support as starting point:
https://glitch.com/~aframe
I have been struggling for a while to get my A-Frame scenes to display in my VR headset through SteamVR. Simply put, my goal is to find a way to get A-Frame projects to properly display on my headset, but instead my headset receives no feed from the A-Frame scene and displays a solid grey or black color. Here's the odd part: sometimes, I can get the A-Frame scene to show up on the SteamVR VR View window on my desktop, but when I put my headset on, the display is still greyed or blacked out. Unfortunately, no errors were encounter (so far) in the console log of the browser I tried running the A-Frame scenes in.
Important to mention, the HTC Vive Headset and OptiTrack Equipment do work. They work for Unity programs and other VR applications. They are just not working with WebVR, WebXR, and A-Frame programs.
Usually what occurs is when I open up the A-Frame scene in a web browser tab manually or by using http-server and ngrok, the scene runs fine on the desktop monitor. However, it then proceeds to open up SteamVR and attempts to connect to my headset. SteamVR will usually say Playing Firefox or Playing Chrome. Sometimes the A-Frame scene appears on the VR View of the SteamVR application, but every time I try this the headset display is blacked or greyed out. That's as far as I can get.
Equipment:
HTC Vive Pro Eye (w/ OptiTrack Active Tag Attachment and Wireless Adapter)
OptiTrack IR Cameras (not using base stations)
HP Z4 Desktop Workstation Computer
Here's what I've tried so far:
Enabling web xr and vr flags in browsers like Chrome, Chromium, Firefox, Edge, and Firefox Nightly (However, for browsers like Chrome, I couldn't find the web vr or xr flags anywhere)
Disabling xr sandbox in the web browsers that provided the option to enable/disable xr sandbox
Trying beta versions of SteamVR
Using a mixed reality HP headset (The one that comes with the backpack VR computer) with Edge
Trying different release versions of A-Frame
Tried using Supermedium, which some have recommended, but I don't think opens A-Frame scenes...
I would paste error and code snippets, but for this scenario it wouldn't make sense since no errors pop up and it's very unlikely that the issue is from the HTML/JavaScript A-Frame code. Thank you for taking the time to read and consider this issue! If you need any other details I'll provide them here so just let me know.
Or is it just me. My own project using tracked hands was working fine yesterday, then today the hands stopped working. After reversing changes since then and still failing, I rechecked one example that was working correctly on Jan. 20: https://aframe.io/aframe/examples/showcase/hand-tracking/ - now, it is not showing hands, or allowing the controls to be used. The hands do show outside of VR when the controller is set down or inside VR when the Menu is invoked. On my device, Hand tracking is on, and the experimental 'WebXR experiences with hand and joint tracking', in chrome://flags, is enabled, both of which I believe are required and were enabled when this was working previously. Turned everything off and on several times, removed batteries, re-paired controllers and did a factory reset of the headset, all per instructions from Oculus support - to no avail. They said they will contact me after asking for invoice info. However it would be good to know if this is some other issue. Can anyone confirm that the above example is, or is not, failing in Quest 2, or is there some other update or change that might be affecting this?
Same for me on Quest 1.
The Three.js examples with Handtracking are working.
Try https://threejs.org/examples/?q=webxr#webxr_vr_handinput_cubes
I recognized that the oculus browser now says "...wants to enter with handtracking" So something changed in the oculus browser that has to be updated in the jslibraries.
But that will change again with chromium 88
I am on oculus browser 13.4.0.3.15 with chromium 87.0.4280
There must have been one cause I had the same problem.
Found this seemingly related fix in the A-Frame code, mostly bone name changes.
And that's what helped me.
<script src="https://aframe.io/releases/1.2.0/aframe.min.js"></script>
I was calling for a previous version of the framework.
Hi I'm new here and I want to make a WebAR application using A-Frame. I know the basics and all that but one major problem I'm having is being able to walk around in the scene using ARCore running in Chrome. Is this even possible? I found a WebVR application from 6 years ago that solved the problem of positional tracking but the code's so depreciated it doesn't work anymore. I would prefer using ARCore for tracking but if nothing else marker based tracking will work too.
Edit: here's the depreciated code on github https://github.com/AVGP/goggle-paper
Doesn't use ARCore but instead marker based tracking. Better than nothing I suppose.
As of today, support for ARCore via the web (and thus A-Frame) is only available on Chrome browser with some Android devices.
Here are some great examples of working projects that you can build from:
https://github.com/chenzlabs/aframe-ar
https://aframe-ar.glitch.me/
New features such as image tracking are only available on Chrome Canary (experimental). See this example for image marker tracking:
https://arimg.glitch.me/
And associated documentation:
https://github.com/immersive-web/marker-tracking/blob/main/explainer.md
Running into an issue with A-Frame 0.3.0 running in GearVR on the Samsung Internet app.
When it loads it displays the A-Frame scene on a card hovering in space like an ordinary stationary web page - the content in the web page rotates with head tracking, but the card remains stationary in space.
When I click on the various 360/180 display modes, the image of the flat web page appears to simply map to a sphere and responds loosely to head rotation - there are swirly patterns at the poles so I'm pretty sure it's just a 2D mapping of the web page. Like it's trying to display it as a 360 video.
Is there a hidden setting? I've enabled WebVR in the Samsung browser. Or is there a directive I need to include in A-Frame? The scene runs fine in cardboard through chrome on android. thx
Ryan Betts from Slack said:
You have to type 'internet://webvr-enable' into the address bar to enable it.
Here is the documentation by Samsung: http://developer.samsung.com/technical-doc/view.do?v=T000000270L where it says:
To enable WebVR visit the internet://webvr-enable URL in the Samsung Internet for GearVR browser (visit internet://webvr-disable to disable WebVR support).
ngokevin's answer is correct, you have to enable. If that done correctly, a working demo using 1.0 API will be able to go into correct mode. Note that can't access correct 'mode' using the fullscreen mode options meant for VR/360 video formats. Try https://toji.github.io/webvr-samples/03-vr-presentation.html If this example doesn't work then have not enabled. If this runs but another page doesn't it would be an issue specific to that page and WebVR API usage.
Remember that webvr support in Gear VR is still experimental and really doesn't work very well yet.
For me the Gear VR is extremely jerky and makes you dizzy when looking around and the quality just isn't very good on the sky images.
I'm using a new Gear 360 camera to take my sky images and when I look at them through the regular Gear VR 360 photo viewer app they look awesome but once you go into webvr and look at those same images they're really really blurry.
Hopefully Gear VR can get the kinks worked out soon and hopefully just replaces that stupid Samsung browser with the new Oculus Carmel browser so these webvr apps will work correctly.