Skip to content
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

Position synchronization mystery glitch using networked-aframe #2581

Closed
evhan55 opened this issue Apr 13, 2017 · 2 comments
Closed

Position synchronization mystery glitch using networked-aframe #2581

evhan55 opened this issue Apr 13, 2017 · 2 comments

Comments

@evhan55
Copy link

evhan55 commented Apr 13, 2017

Description:

Hello! I am using A-Frame and networked-aframe to hold VR office meetings with my colleagues. networked-aframe generates an avatar for every connected user, and we expect to see each other's avatars in the same relative positions across instances. networked-aframe keeps tracked of synched positions/rotations for all the avatars.

However, when we first connect to the office, the positions do not at first appear synched.
After entering the inspector, and then clicking 'Back to scene', however, then the avatars are mysteriously synched. I checked first with @haydenjameslee, the creator of networked-aframe, and he was the one who discovered this inspector workaround. He is not currently sure if the issue is with networked-aframe or A-Frame, so I am posting here just in case.

Steps to Reproduce:

  1. Mute your computer's audio
  2. Visit https://elevr-office-net.glitch.me in two browser tabs
  3. Click 'Allow' (optional)
  4. In one tab, move the avatar/camera to one corner of the room
  5. In another tab, move the avatar/camera to another corner of the room
  6. In each tab, you should NOT see the opposite avatar where you think it should be
  7. Now, in both tabs, enter the inspector with ctrl+alt+i and then click 'Back to scene'
  8. Repeat steps 4 and 5
  9. This time, in each tab, you should see the opposite avatar where you think it should be
@evhan55
Copy link
Author

evhan55 commented Apr 13, 2017

Cross-posted here: networked-aframe/networked-aframe#12

@evhan55
Copy link
Author

evhan55 commented Apr 13, 2017

Oh! This seems to be solved because I had two a-camera components by accident.
Reducing to just one seemed to do the trick.

Glitch link is down at the moment but asking the glitch team to help me reinstate it.

Thank you!

@evhan55 evhan55 closed this as completed Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant