search

oculus-samples / Unity-Discover

Discover is a showcase of the Meta Quest Mixed Reality APIs. This project demonstrate how to use Passthrough, Spatial Anchors, Scene API, Colocation and Shared Anchors.
MIT License
248 stars 59 forks source link

Issues Running via Link #11

Closed eswaranand1997 closed 5 months ago

eswaranand1997 commented 10 months ago

Had previously opened: https://github.com/oculus-samples/Unity-Discover/issues/7

Reporting back with requested details. Tested again on v60. Here's the results

testing on Quest Pro over Link and Quest 2. Link App version: Oculus App Version 60.0.0.162.352 (60.0.0.162.352) Headset Version: 60.0.0.193.366.548441753

When building to both devices to run natively, application works fine. When hosting a room, the device shows the current scene setup and asks for confirmation about the scene setup.

When running on PCVR Link in Unity Editor, this request does not pop up. After both users load in, they are not colocated.

Other scene api samples dont seem to work as well. The SceneManager and BouncingBall samples from the StarterSamples package also do not work properly over link. Scenemanager shows no volumes on Link while running natively, shows anchors and bounding boxes over the defined scene objects.

Here's the device logs from the QPro while running Discover in Editor. odh_logs_2023-12-29 23.52.07.199.txt

Some relevant warnings from editor

image image
tdmowrer commented 6 months ago

Hi @eswaranand1997 and apologies for the extreme delay in response here. Taking another look at this, I was going to ask for the Editor logs instead of device logs (which generally are more relevant to Link-related failures like this). I can see more of the problem in your second screenshot -- creating the "space user" failed, which subsequently caused xrShareSpacesFB to fail.

If you are still seeing this issue, it might help if you could provide the Editor logs as it might explain why that call is failing.

jasonmeisel commented 5 months ago

If you are still running into this problem with the latest version of Link, please re-open the issue.