-
Notifications
You must be signed in to change notification settings - Fork 18
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
6-dof support with Xreal Air 2 Ultra #18
Comments
I would love this too, I waited for the ultra thinking it was compatible. If you need data or some with an ultra to work with I'd be open to helping in any way I can. |
Same. Happy to help and provide data. I have Ultras and would love to use them to their full potential in flight sims, which means using PhoenixHeadTracker.
…On 17 December 2024 06:26:09 CET, Droninator ***@***.***> wrote:
I would love this too, I waited for the ultra thinking it was compatible. If you need data or some with an ultra to work with I'd be open to helping in any way I can.
|
Just got the ultras be happy to contribute |
I tried using it with my Ultras and unfortunately PhoenixHeadTracker sees no data when I connect. I tried with original Airs too and it worked just fine, so there's clearly something Ultras-related. Is there anything we can try @iVideoGameBoss, even for just 3-dof? Maybe it's just that the sensors are not named the same way in the Ultras? |
I guess we should do this: https://github.com/iVideoGameBoss/PhoenixHeadTracker?tab=readme-ov-file#you-can-use-phoenix-head-tracker-with-gyro-data-from-other-devices I have zero experience in building stuff for Windows, but hopefully I can understand how it works later. |
Xreal Air 2 Ultra support 6-dof, and combined with PhoenixHeadTeacker, it could finally make flight sims with those glasses an experience similar to full-fledged VR headsets. Do you plan on adding support for that in the future?
They even support hand-tracking, but I assume this would require much more development than just adding the extra sensors data for 6-dof.
The text was updated successfully, but these errors were encountered: