Loading Meta Avatars With Cross Play using Federated App Are Missing Their Heads
UPDATE (01/05/2023) As of January 5th users are being loaded via the Federated App Id but instead of missing their heads they now seem to be missing their hair. It would be funny if our product launch was not dependent on this getting fixed. UPDATE (01/03/2023) As of January 3rd Loading Avatars with Federated App Ids simply doesn't work. The User fails to load and I get the error log 'Spec Request Failed'. __________________________________ We've been experiencing problems with the Meta Avatar 2 SDK in our desktop app. I've narrowed it down to a problem with the way avatars are loaded using the federated app id, or cross play as its called in the documentation. Here are the steps to reproduce: Create a blank Unity project which allows you to load an avatar with both your app's regular app Id and its Federated App Id. Load an avatar using the federated app id: you avatar with the Federated app id, it loads fine. Now, in your Quest, edit your avatar. Now load the avatar again using your federated app id. 5. Now try loading the avatar again but this time using the regular app id... The problem persists. The avatar can be made to load correctly if you load the avatar regularly once, make a change to your avatar, save and then reload the avatar.
