-
Notifications
You must be signed in to change notification settings - Fork 99
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
Certificate on older versions. #245
Comments
Download the .msix file from the releases page, extract it as a .zip file, then run the executable from there. |
This worked. Also fixed the bug I was having. Makes me wonder what changed between 5.1.1.0 and the current 5.3.x that causes the eye tracking to spontaneously switch to random wandering. |
Random wandering is not a functionality implemented from within VRCFT. This is likely caused by a pause in eye tracking data being sent to vrchat's native eye tracking system. I've seen this caused by modules being unable to get/send eye tracking data to vrchat for extended periods of time. As for why the application is difficult to install on older versions: Microsoft's app installer format enforces a valid code signing certificate. Older versions of vrcft utilize a now-expired certificate and, as such, are prevented from installing in the normal manner. Hope this helps. |
Thanks for the replies. |
My first recommendation would be to send logs |
[VRCFaceTracking.Services.ActivationService] Information: VRCFT Version 5.2.3.0 initializing... |
I see you're running VIVE hardware. May I ask specifically which headset/tracker combo you're utilizing? |
Vive Pro Eye and the Vive Face tracker. |
That is indeed very odd. Do you notice anything odd about the timings around when this issue occurs? USB disconnect sounds, errors printed in logs, eyes freezing up? |
No.. It happens immediately with the avatar. I can do a OSC disable and enable in VRC and it will function for less than 1s, then the eyes will stop tracking. Just the eye rotation, I should add. Eye lid, and face never stop tracking. |
Huh, does this issue persist regardless of the avatar? |
I don't have a large selection of avatars to compare to, but IIRC it does seem related to specifically the updated 2024 version of this avatar. I'm mostly working on a repaint of it, so I have the source files; but otherwise I'm very early in my understanding of avatar construction. |
The legacy version of the same avatar does not exhibit this behavior, but I believe the creator updated the tracking system between the versions. |
Hmm. I wonder if this could be an avatar setup issue. Could you try some public known working avatars? There are quite a few in https://vrchat.com/home/world/wrld_b24fbb7c-9369-4cff-9242-32a35d44a8e8/info |
I can try a sample. I've been in contact with the creator, and they're confused by it. It was another user that suggested that the downgrade to 5.1.1.0 got it working. But I figured I'd bring it up here since there seemed to be a need to use the previous version, and either help get it more accessible, or help figure out the why. |
I also have the avatar open currently in unity, if there's anything I could check on the setup that might explain it |
In general, a requirement to use an older version of the app is a flaw on the avatar creator's part. We only modify the way parameters are sent in compliance with our documentation and unified expressions spec, so avatars breaking due to updates are considered noncompliant |
I'm trying to debug an issue with an avatar and having eye tracking work and disable itself. Other users have indicated that using 5.1.1.0 worked for them. However, the certificate alongside 5.1.1.0 is no longer valid, and the previous version won't install.
I tried to download the source code and compile it, but it requires "deployment" instead of allowing to run locally and complains a lot about app manifest issues.
Sorry if this sounds like 2 issues but how do I either:
Install 5.1.1.0 from the download or
Compile 5.1.1.0 for local running without needing to deploy it to the MS Store.
The text was updated successfully, but these errors were encountered: