-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
HIFI: manual URL location gets ignored #1279
Comments
What is this means exactly: "when added onto the URL"? Can you give more details and step to reproduce ? |
hifi://5.161.126.31:60002/-2,0,3/0,0,0,1 and just pasting the URL into the places search bar |
Well, the server seems to be private. So I can't test this specific URL. But I did the test using an ip: port with the exact same path and I'm landing at the right spot 100% or the time. What kind of random destination did you get? Regarding private place... sadly, they get displayed in the Places app list, they were not supposed to. And there is still not any preference to not published... (Current limitations) |
Yeah, I cannot reproduce it here either. |
i input this url hifi://5.161.126.31:60002/-2,0,3/0,0,0,1 i will open up the server for you to test |
I made this test: Maybe there is something else you do or use? Or maybe this needs more attempt to reproduce it? It could be also the explanation why I sometime land under the floor on some of my domain. (a problem introduced and not completely solved long time ago when High Fidelity change something about the position of the avatar. Were you in Desktop or in VR when you experienced that? |
I wonder if it has anything to do with the avatar. Maybe it tries to put the base of the avatar somewhere, and there is something broken about the model making that part of the code fail. (I cannot reproduce the issue on hifi://5.161.126.31:60002/-2,0,3/0,0,0,1 either.) |
we have found out after trying to make a private world with a location that the location when added onto the URL gets ignored and you get sent to a random destination we did use a location taken from a spot in the world.
if you register a location with places in the directory service it works fine but otherwise couldn't get it to take me to the specified location.
The text was updated successfully, but these errors were encountered: