Open InsaneGrox opened 2 years ago
Even then, I'd need to create them in the same folder where VRChat stores them, which is not... What ChilloutVR is supposed to do... :(
Either way, there's face tracking already in place in ChilloutVR, so I don't know why you'd need VRCFaceTracking... You could ask the devs to add a startup argument (e.g. -cvr) to make it read a ChilloutVR-specific folder for config files.
eye tracking shapekeys like eye widen, individual blinking, and pupil dilation, that's why Im using vrcfacetracking As for generating configs, it's a dumb compatability measure, but it is neccecary for apps that read configs, this can be done manually so a tutorial on doing it would also suffice. (I manually did mine and it works)
The issue is that I can't just make CVROSC output config files to VRChat's cache folder! It's not good behavior! I don't know what VRChat does in its black box, doing this could actually cause it to misbehave or even crash, if it tries to load the config of a GUID that matches one from CVR. Who knows? 😕
The best bet would be to collaborate with the VRCFaceTracking team, to implement something that could override the source path for these config files.
I'll take a look into it.
The configs are working for me! The name seems to be set to _PLAYERLOCAL
which is not really an issue (for me).
My vrc osc app worked like a charm with the configs, except the minor difference that vrc uses the avatar ids on the json file names without the avtr_
prefix (which is weird since they use the usr_
prefix on the folder. VRC logic I guess xD Other than this all I had to do was changing the folder path.
Great work!
Some OSC apps like VRCFacetracking rely on the OSC avatar configs, and as such error when you try to use them.![image](https://user-images.githubusercontent.com/54233743/181918416-51b38348-ed36-4b91-9e70-df5976cecc92.png)