Context Navigation

Changes between Initial Version and Version 1 of Ticket #15846, comment 9

initial	v1
1		Testing a LookSee 2 person meeting again in the vizvault with alignment markers placed on opposite sides of the room (corner of desk and corner of poster), the alignment remained good after taking the headsets of and waking them about 10 times. This is with v71 of the Quest headset runtime. Pressing and holding the controller system button to realign coordinates had no effect although it showed the realign icon. This was with LookSee v17.
	1	Testing a LookSee 2 person meeting again in the vizvault with alignment markers placed on opposite sides of the room (corner of desk and corner of poster), the alignment remained good after taking the headsets of and waking them about 10 times. This is with v71 of the Quest headset runtime. Pressing and holding the controller system button to realign coordinates had no effect although it showed the realign icon. This was with LookSee v17. I had the display sleep set to 15 seconds and headset sleep set to 1 minute on both headsets. After I left both sleeping 5 minutes I came back and the non-host had dropped the connection and could not reconnect (socket error 113, no route to host) and I saw that the host wifi had changed from RBVI to UCSF WPA. Changing the host headset back to RBVI wifi allowed the non-host to reconnect to the meeting and alignment of both headsets was preserved.
2	2
3	3	In summary the meeting alignment with LookSee v17 and Quest runtime v71 seems to be stable.