Forum Discussion
AreVisemesValid is updated inside the Update function in OVRFaceExpressions.cs at line 213.
It is computed as the logical AND of the following two conditions:
- OVRPlugin.GetFaceVisemesState(OVRPlugin.Step.Render, ref _currentFaceVisemesState) == OVRPlugin.Result.Success
- _currentFaceVisemesState.IsValid
The first function, OVRPlugin.GetFaceVisemesState, is defined in OVRPlugin.cs at line 10308.
Inside it, the following call at line 10315 returns Failure_Unsupported:
Result res = OVRP_1_104_0.ovrp_GetFaceVisemesState( stepId, -1 /* OVRP_CURRENT_FRAMEINDEX */, out cachedFaceVisemesState );
Because this call returns Failure_Unsupported, AreVisemesValid always becomes false.
Since OVRP_1_104_0.ovrp_GetFaceVisemesState is implemented inside a DLL, I cannot inspect its internal implementation.
Although the Meta Movement SDK claims to support visemes, the current situation is that they cannot actually be used. This appears to require a fix. I am looking for an alternative approach.
Please help.
→ Find helpful resources to begin your development journey in Getting Started
→ Get the latest information about HorizonOS development in News & Announcements.
→ Access Start program mentor videos and share knowledge, tutorials, and videos in Community Resources.
→ Get support or provide help in Questions & Discussions.
→ Show off your work in What I’m Building to get feedback and find playtesters.
→ Looking for documentation? Developer Docs
→ Looking for account support? Support Center
→ Looking for the previous forum? Forum Archive
→ Looking to join the Start program? Apply here.
Recent Discussions
Accessibility Request Support for Power Wheelchair Joystick and Bluetooth Mouse Inputs Meta Quest 3
Hello Meta Developer Community, My name is Rodrigo Sologaistoa. I am a biologist pursuing a master’s degree in bioinformatics, and I work at the Biomolecule Simulation Laboratory at the Institut Pas...