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.

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

Can't move in vr #59

Open
Werschon opened this issue May 24, 2019 · 5 comments
Open

Can't move in vr #59

Werschon opened this issue May 24, 2019 · 5 comments
Labels
external_issue issue with external libraries or hardware

Comments

@Werschon
Copy link

Hello pottedmeat7, I can't get WalkInPlace to work. I want to use my two trackers to walk in The Talos Principle VR with my own feet. So I created a datamodel and when I click on 'show data model' the graph shows me that my trackers and my headset are moving but when I want to move in vr nothing happens.
HMD_movement
Trackers_movement

These are my settings:
Settings

Then I tried to fiddle around with the ovrwip controller. As I understand it, ovrwip is a digital controller that receives the input from the trackers and forwards them to one of my Vive controllers, is that correct? And I have to use the steam mapping system to make sure that the input is indeed forwarded to one of the vive controllers, right?
So I checked my ovrwip controller and it seemed like the input should go to my left vive controller:

SteamVR

So by my understanding everything should work, but unfortunately it does not. Did I miss some important step? Or is it because I use a Pimax 5k+? I also noticed that the graph does not show the movements of my controllers:

Controller_movement

Could this be the issue? Would be nice if you could help me, thanks.

@pottedmeat7
Copy link
Owner

Looks like the tracking data did not get any output for the HMD. There should be some data similar to the tracker model there. Must be an issue with Pimax 5k+ sending incomplete openvr tracking data, may run through thier own software instead.
By default the HMD model is required, however you can disable tracking HMD entirely on the disable device page. This will match just the trackers but is not working ideally ATM, it wont be as instant or smooth movement. The next release you will be able to customize the size and duration of the tracker real-time samples which will help make tracker only movement better. I would recommend HMD tracking also but looks like its not possible with pimax 5k+ ATM.

@Werschon
Copy link
Author

Thanks for your fast reply. Without HMD tracking it finally works, although not really good. But this is strange, the tracking graph page shows that the HMD is moving:

HMD_movement

But the datamodel shows just this flat line

@pottedmeat7
Copy link
Owner

pottedmeat7 commented May 24, 2019

Those are just rotations. Looks like the pimax maps over rotations but the velocity is not, actually this is similar to previous issues with the Rift tracking. Did you try to select "Rift/Other" from the dropdown next to "Enable WIP"? Maybe then you will get the Y_VEL values needed for the HMD model.

@Werschon
Copy link
Author

I tested both options ('Vive/Rift' and 'Other') but unfortunately Y_VEL still remains a flat line.

@pottedmeat7
Copy link
Owner

pottedmeat7 commented May 24, 2019

Ok, this seems like a problem with pimax, Y positional data may not be available to calculate velocity and only contains the rotational data.

@pottedmeat7 pottedmeat7 added the external_issue issue with external libraries or hardware label Jul 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external_issue issue with external libraries or hardware
Projects
None yet
Development

No branches or pull requests

2 participants