-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Objects in colocation don't apear in the same space in a room. #12
Comments
Hi @Tony-j77, When each user is done with the colocation step, do you see the anchor in the same physical location? Just to make sure also, you don't see the other user as an avatar right? If you can provide the logs of both devices that would be helpful. Thanks |
Hello @AlexThiv, I played around with the sample again and it seems like it doesn't matter if I press 'join' or 'join remotely', I always get sent into the room remotely i.e. "joined remotely". Also, yes, I do see the other user as an avatar. Here's my process: In headsest 1, I enter a room name, then click 'host', then I see "colocation ready". In headset 2, I enter the same room name, I click "join" ... but it says "joined remotely". Is there something immediately noticeable that I am doing wrong? If there isn't, I'll get the logs to you asap. |
Ok that means that the shared anchor was either not localized (didn't find that the 2 users were in the same room) or that the first user failed to share the shared spatial anchor. Can you check that you accepted the permission to share the anchor and spatial data to the cloud? |
Hi @Tony-j77, I did some additional digging and figured out what is the issue you are running into. But we recently added a Scene feature flag for the android manifest and enabling that updating the manifest works without having to push and apk. You can see how we enabled it in this latest commit. If you get the latest it should fix your issue. Thanks again for raising this. |
Hi @AlexThiv , i currently am experiencing the same described issue. So i see the other players avatar (Grey Avatar not the Meta Avatar), and the anchor point is not at the same location. Things i allready done:
A little help to figure out the problem would be very much appreciated :) Thanks in advance :) |
@MunzeKonza93 can you verify in the logs if the application is entitled. If you have a unity log that says the app is not entitled, make sure to add both users to the organization. |
@AlexThiv i checked last few days documentation about seting up shared spatial anchor and did everything from the docu:
Now When Starting Discover on both devices Quest 2 and Quest 3 i can see the Meta Avatar of the other User but still Colocation is not working. I also installed the Discover Sample directly from the App Lab from the Devs and with that Version i also have the same problem. So still no solution for this issue. Maybe its not compatible btw. Quest 3 and Quest 2 ? EDIT:
The device setting ‘Share Point Cloud Data’ must be enabled for Shared Spatial Anchors to function. Users can find it under Settings > Privacy > Device Permissions > Share Point Cloud Data. |
@MunzeKonza93 I'm glad you figured it out. I updated the configuration details with these specific information for future users. commit bddb5e2 |
I'm trying the default mountain bike app on 2 Quest 3s and the shared spatial anchors are not aligned. The bike appears to be in different places for both users. I am using the 'host' and 'join' buttons and not the join in a separate room. Am I doing something wrong?
The text was updated successfully, but these errors were encountered: