-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Issues using holoport to navigate #19
Comments
VRChat did an unexpected update to Holoport that appears was lightly tested. (they are really busy) Holoport needs to be updated to support trigger volume configurations such as those in The Great Pug. And this feels like a valid statement considering it worked fine since 11/14/17. |
What are trigger volume configurations? and what are they used for in the pug? Would it not be possible to work around the issue untill VRChat fixes the cause? |
They are used to indicate where one can safely hold/place pickups without them respawning. I do not have time at the moment to implement more workarounds to paper over VRChat's bugs. I'll reassess this should it not be fixed around/shortly after the Quest build launches. The Holoport update was silently implemented into the main client as a result of changing it for Quest. I think it was not mentioned in the patch notes because either: |
Please view this Canny item and voice your support for fixing Holoport: |
I have received word that a solution to this has been found, and should be in a future VRChat update. |
Nice, hopefully the fix will come out soon (and without breaking anything else) |
@TheLastRar Has this improved with the new patch? |
The new VRChat patch seems to have resolved the issue with holoport. |
Describe the bug
While I don't use holoport, I been told by a couple players that they can't use holoport to navigate the pug, having to disable it or physically walk + rotate to navigate around.
Expected behavior
Able to navigate using holoport without issue.
Screenshots
If applicable, add screenshots to help explain your problem.
Are you in VR or Desktop mode?
VR
Additional context
This used to work before, as I used to use holoport and never ran into this issue In the past. So something changed since when I stopped using holoport to now.
The text was updated successfully, but these errors were encountered: