-
Notifications
You must be signed in to change notification settings - Fork 332
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
Starting position in Echo Arena #738
Comments
have you tried going through the setup for standing area for setting the floor offset to the headset again in SteamVR settings? It didn’t work for me either but it’s not really noticeable when you get in-game is it |
Nope, it's not that big of a deal but I thought I'd want to know if I were the dev.
I can try redoing the setup, but like you said it's fine otherwise. I often switch chaperone profiles using advanced open VR settings but the issue was new with the changes pushed to deal with the bounds not appearing.
On Wednesday, August 16, 2017 at 8:14 PM Todd Sullivan <notifications@github.com> wrote:
have you tried going through the setup for standing area for setting the floor offset to the headset again in SteamVR settings?
It didn’t work for me either but it’s not really noticeable when you get in-game is it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This is an issue due to the quick-fix for the chaperone in version 1.1.13 to prevent further accidents. I'll have a proper fix in version 1.2 without the re-centering issues. As a temporary workaround you can go back to version 1.1.12, but you should set the chaperone to always-on if you do that. |
I thought of a fix that doesn't require waiting until version 1.2, therefore I released version 1.1.14 which should fix both the chaperone issues and this re-centering issue. |
The position you start during Echo Arena is sometimes really high and 45 degrees left facing. This is new since the latest update, and noticeable when first entering the game (Main Menu) and after your player resets/loads into the pod.
It's reminiscent of the issue with Robo Recall that existed with loading into the elevator. Below is a twitch link where you can see it happening a decent bit (I'm not that tall). You can skip to around the 54-minute mark and there are plenty of goals before/after to scrub too.
https://www.twitch.tv/videos/167525724
The text was updated successfully, but these errors were encountered: