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.

Sign up for GitHub

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

Jump to bottom

room id 1000 range #3

Closed
gfodor opened this issue Apr 9, 2015 · 2 comments
Closed

room id 1000 range #3

gfodor opened this issue Apr 9, 2015 · 2 comments
Assignees
@amberroy

Comments

@gfodor
Copy link
Contributor

gfodor commented Apr 9, 2015

Is there a reason we used a max room id of 1000, and aren't worried about collisions?
@amberroy
Copy link
Contributor

Reason was to be on the same order of magnitude as the number of Altspace rooms, thinking it was a placeholder until there was an API to get the actual Altspace room id. Now that this approach (Firebase room id not related to Altspace/photon room id) seems to be working, agree we should increase the max. Thanks for flagging this @gfodor

@amberroy amberroy self-assigned this Apr 10, 2015
@GavanWilhite
Copy link
Contributor

Resolved with new sync utility

stevenvergenz pushed a commit that referenced this issue Feb 1, 2017
@GavanWilhite
Merge pull request #3 from AltspaceVR/feature/use-pixel-units
8072af7 
Replace autoscale parameter with usePixelScale
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amberroy amberroy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gfodor @amberroy @GavanWilhite