-
Notifications
You must be signed in to change notification settings - Fork 2
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
Roll axis is not functioning well #3
Comments
It seems the problem in the firmware MPU 6050. I came across it. There is no problem in RazorIMU, as with the tracker Arduino + GY 85 this problem does not have. |
In Unity works fine! |
@r57zone but in the getdata file yaw pitch roll data seems perfectly fine? It sure is weird |
And also when i tried the same freepie codes with Vridge(riftcat) and trinusvr, it worked flawlessly. Unfortunately I dont want to use a phone as a screen. Are you really sure it is mpu6050 that causes the issue? It sounds improbable to me... |
@AltugOS GetData should also show that there is a problem. |
@r57zone I will send you a video proof that getdata works flawlessly as soon as I can. Like i said, when i use other programs than tovr, its perfect. When i use only tovr, its perfect. When i use tovr-steamvr, roll axis gets weird. I also have an idea for troubleshooting. I will try to control freetrack data using keyboard within the freepie script. |
I have the same problem. Did you find the solution? |
There is a problem with RazorIMU + MPU6050 combo. In steamvr, roll axis line is fixed to the default front direction. So it works fine when i look forward but when i look sideways, roll axis does not work as intended (for example rolling to the right when looking 90 degrees to the left results in a pitch up like motion). I have also tried to route the data through FreePIE and using FreeTrack driver and got the same result. BTW the values are fine in getdata examples, so the problem is between TOVR output and SteamVR input. any help would be appreciated.
The text was updated successfully, but these errors were encountered: