Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Library UnityEngine.Animations.Rigging doesn't exist

Discussion in 'Animation' started by valentin56610, Jan 31, 2022.

  1. valentin56610

    valentin56610

    Joined:
    Jan 22, 2019
    Posts:
    146
    Good evening everyone

    I just imported the rigging package in Unity (2020.3.26f1 on MacOS) and ... I got this (see uploaded screenshots): Capture d’écran 2022-01-30 à 20.57.10.jpg Capture d’écran 2022-01-30 à 20.56.54.jpg

    It says the namespace doesn't exist, I thought I typed it wrong but ... nope, it should be like that, how am I supposed to solve it ?

    Cheers
     
  2. valentin56610

    valentin56610

    Joined:
    Jan 22, 2019
    Posts:
    146
    help? I literally cannot work because of this bug
    I tried restarting my computer and Unity already
     
  3. unity_NogeEf3OSGOpQA

    unity_NogeEf3OSGOpQA

    Joined:
    Jan 25, 2022
    Posts:
    1
    Hello,try pressing the "import" button in "Animation rigging" and restart visual studio.
    It helped me
     

    Attached Files:

  4. valentin56610

    valentin56610

    Joined:
    Jan 22, 2019
    Posts:
    146
    Issue got solved by itself without me doing anything
    Super weird ... nothing I did helped ..
     
    Last edited: Jan 25, 2023
    trombonaut likes this.
  5. vrezzoug

    vrezzoug

    Joined:
    Feb 25, 2021
    Posts:
    3
    Same on Unity 2021.3.12f1 with Animation Rigging package 1.1.1
     
  6. valentin56610

    valentin56610

    Joined:
    Jan 22, 2019
    Posts:
    146
    From my previous experience, you can only wait and hope it solves by itself, as it is what happened for me ..
     
  7. ujz

    ujz

    Joined:
    Feb 17, 2020
    Posts:
    28
    I had a similar issue with my VSCode not recognizing UnityEngine.Animations.Rigging. I tried many things (deleting .csproj, regenerating project files, reimporting packages, updating VSCode, creating Assembly Definitions, etc).

    Finally I came across this thread, which pointed out that there was a specific bug with csproj files in the VSCode package version 1.2.4. So I updated my Unity package for Visual Studio Code Editor to version 1.2.5, unchecked all boxes and regenerated project files as described in that thread, and it finally worked. Just leaving here for future reference.