-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support VRCFaceTracking v5.2.3 #5
Comments
Yes version 5.3 is broken and it can be only accessed using OSCQuery. Please use 5.1.1.0 for now until they fix. There shouldn't be any major changes between the two versions right now.
You should be able to install 5.1.1 side by side with 5.3.0, that's what I do currently. |
I've updated the readme to reflect that. |
Figured it out how to run/install 5.1.1 even though the certificate has expired. Download the MSIX file, rename the extension to .zip and export it in a folder. Then you should be able to run VRCFaceTracking.exe in that folder to launch VRCFT v5.1.1 |
omg wow okay ill try that thank you so much! |
I've also fixed up the issue in a PR, hopefully it gets merged soon |
Situation :
It seems the vrcft reciever is empty on the user root.
I also added a prefab to the avatar but while its osc reciever is set to 9000 - and vrcft is sending on 9000 - and also i see a 1 m/s message coming IN on vrcft on 9001... I have yet to see any of the paramaters values be driven? or any parameters to load on the vrcftreciever auto added to my root.
Expected behavior:
I think it should be driving the values of each of these
other things of note:
ADDITIONAL FINDINGS UPDATE:
so from talking to people in the resonite discord, the one perosn who know who has it working is on 5.1.1.0
mine is on 5.3 and there is no way to downgrade.
could this be the issue? all outputs monitored in protokol regaurdless of if we send "force relevancy" or if we send your command of
"vrc_parameters"
will send this instead due to the vrc_parameters file not being loaded:
The text was updated successfully, but these errors were encountered: