Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
mike.golembewski's avatar
2 years ago
Solved

Cannot add Meta Avatars SDK (v29.7.0) to a clean project in Unity. [Solved!]

Hello!

I am currently unable to set up the newest Meta Avatars SDK (v29.7.0).  Every time I try to install, it raises the same three errors :

  • Library\PackageCache\com.meta.xr.sdk.core@68.0.3\Scripts\BuildingBlocks\MultiplayerBlocks\Shared\NetworkedAvatar\Scripts\EntityInputManager.cs(31,17): error CS0103: The name 'BodyTracking' does not exist in the current context
  • Library\PackageCache\com.meta.xr.sdk.core@68.0.3\Scripts\BuildingBlocks\MultiplayerBlocks\Shared\NetworkedAvatar\Scripts\EntityInputManager.cs(33,17): error CS0103: The name 'BodyTracking' does not exist in the current context
  • Library\PackageCache\com.meta.xr.sdk.core@68.0.3\Scripts\BuildingBlocks\MultiplayerBlocks\Shared\NetworkedAvatar\Scripts\EntityInputManager.cs(34,17): error CS0103: The name 'BodyTracking' does not exist in the current context

Does anyone else seem to be having similar issues?  Any insight as to why this might be happening, or if there are any steps to be taken to resolve this, would be greatly appreciated.

Thanks, 

Mike.

 

[UPDATE : If this happens, first try going to the Packages folder in the Project tab, selecting the 'Meta XR Core SDK', right-clicking it and reimporting.  Over a bunch of tests, this seems to fix the issue fairly reliably.]

For additional context, here are the steps I've taken leading to the issue :

  1. Starting from a clean base URP project in Unity 2022.3.42f1, I switched the build settings to Android, and configured a keystore for build signing.
  2. I installed Photon Fusion (2.0.3) and Photon Voice (2.56), and configured these to work with a photon cloud app.  I then tested and confirmed that these were working as expected.
  3. I installed the Meta All-In-One SDK (v68.0.3) via the package manager, then applied all suggested project changes (graphics and lighting settings, manifest creation, etc...).  I confirmed that these were working as expected.
  4. I configured the Oculus Platform Settings with a valid App ID and confirmed that the values were correct.

I then added the Meta Avatars SDK (v29.7.0) via the package manager.  The package was installed, but when it compiling, the previously mentioned errors were thrown, preventing completion.  To repeat the error (also thrown from lines 33 and 34):

  • Library\PackageCache\com.meta.xr.sdk.core@68.0.3\Scripts\BuildingBlocks\MultiplayerBlocks\Shared\NetworkedAvatar\Scripts\EntityInputManager.cs(31,17): error CS0103: The name 'BodyTracking' does not exist in the current context

 

  • OK!  I think I've found a working solution here.  I'm pretty sure the issue has to do with the order in which the packages are installed.  The Avatars SDK must be installed first, followed by the All-In-One SDK.

    I was able to get the Meta Avatars SDK (29.7) to work in a project with Meta All-In-One SDK (68.0.2) by:

    1. Starting with a clean (no meta packages) project.
    2. Adding the Meta Avatars SDK (29.7) via the package manager.
    3. Adding the Meta All-In-One SDK (68.0.2) via the package manager.

    I was also able to 'upgrade' a project by :

    1. Removing the existing Meta Avatars SDK (24.1) via the package manager.
    2. Removing the existing All-In-One SDK (68.0.1) via the package manager.
    3. Adding the Meta Avatars SDK (29.7) via the package manager.
    4. Adding the All-In-One SDK (68.0.2) via the package manager.

    This worked for me - right up until I quit the browser and restarted.  At that point, the errors came back (along with some console flooding for good measure).  This was repaired, though, after I cleared the library package cache and restarted,  It's been working well since, although it seems that a number of features have been removed as of the latest version (networking and colocation building blocks, interaction building blocks, etc,,,).

15 Replies

Replies have been turned off for this discussion