ruiying
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Downloads
Posts posted by ruiying
-
-
Sorry @Alex_HTC I was working on and talking about a VIVE Flow, not a Focus 3.
VIVE OpenXR plugin works all fine on Focus 3, but I got the issue on the Flow.
-
I’m not seeing the eye tracker option listed under setting->input !? (I'm talking about a VIVE Flow)
I assume the dial ring around the lens is for adjusting the IPD. Am I right? (for VIVE Flow)
-
Thank you @Alex_HTC
Changing system IPD woundn't make much difference.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
the right eye won't see anything at all.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
if put the cube on the central line, no matter how near or far away I put the cube, each eye only sees small part of the object.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -
I've been using VIVEPORT video, but it won't see images. So I turned image/(s) to video.
-
It looks like two eyes positioned TOO far away from each other.
-
On 11/1/2023 at 9:43 PM, Alex_HTC said:
@ruiying
Which problem above? Here are some of the problems/solutions suggested
1) signing issue with creating an apk
This appears to be an issue with the way that unity looks for the keystore file. A user reported that deleting that file allowed it to work again. This seems to be an issue with unity that can be resolved by deleting (or moving) the "D:\Android\Home\.android\debug.keystore" file, so it can create one that it recognizes it. I linked to a few threads that point this out
2) Confusion about sdk and/or input
try building against a known-good branch like the openxr_hand_tracking branch here https://github.com/ViveDeveloperRelations/MinimalRepo/tree/openxr_hand_tracking
3)Trying to load multiple scenes
-These will all have different camera rigs and likely cause issues. if you want to try our samples as-given then use one scene at a time.
-It's worth noting that unity only loads one scene at a time if multiple are selected, so you'd need to de-select one and/or try to load scenes at runtime with your own code for that.
4) Occlusion on one eye - this can happen for a variety of reasons, including you being too close to the UI. There was not enough detail to tell what was being referred to.Thanks for your detailed reply Alex
I was referring to eddylai's last post talking about eye swap. But my issue looks more like wrong eye separation. I tried the general XRRig and VIVE’s VRSRig.
-
Ran into the same issue. Any update?
-
Thank you very much. I'd like to let you know
if you have branches or staff in uk want to do more research about the problem, our lab is open to you to do the job. We are at Portsmouth
-
-
YES, Vive trackers work perfect as soon as cameras are off.
-
Thanks for your reply
Our Vicon system using T10 near infrared cameras
Vive headset and controllers have been working fine with both of our motion capture systems. We are using first generation of headset and controllers.
I guess you might be using different sensors in trakcers and new generation of your product...
-
We tried the trackers with both OptiTrack Flex13 and Vicon system. While the cameras of motion capture system are on the Vive trackers turned very unstable...if you wave around trackers they can be tracked at some point but lost tracking very quickly.
Isn't there any work around to solve this problem? any suggestion please...
Thanks
Ruiying
what SDK for VIVE Flow
in VIVE Flow
Posted
@Alex_HTCWe are not using eye tracker on the flow. The dial ring around the lens is for chaning IPD I assume.
