• Unity

  • The type or namespace name could not be found

    англійська

  • Arnissan

    • Допис #1
    • Змінено
    • Цей допис на англійська
    Related Discussions
    ...

    What am I missing? This happens to all Spine example scripts on a fresh Unity 2019.3.12f1 project with just Spine runtimes (04.29) imported.

    VS 2019

    This does not happen in my 2019.3.9f1 project with an older version of the Runtimes:

    The latest runtimes work on 2019.3.9f1 so this issue seems to be specifically isolated to 2019.3.12

    • Kkloot

      • Допис #3
      • Цей допис на англійська

      I'm also getting tons of errors after upgrading unity to 2019.3.12 (everything works if I go back to 2019.3.11).

      Compiling the spine-unity-editor project results in the following:

      Using spine-unity 3.8 (updated 2020-04-29)

      • Harald

      • Допис #4
      • Цей допис на англійська

      Thanks for reporting and sorry for the trouble! Unfortunately we could not reproduce the problem using Unity 2019.3.12f1 and spine-unity-3.8-2020-04-29.unitypackage. In which way did you create the new empty project?

      Thanks for the hint, kloot, we will have a look at updating an existing project right now.

      • Kkloot

        • Допис #5
        • Цей допис на англійська

        Thanks for looking into it,
        I tried deleting the Assets/spine directory and install the package from scratch, but got the same errors.

        • Harald

        • Допис #6
        • Цей допис на англійська

        Unfortunately we can still not reproduce the problem. However, an inverse problem could be reproduced before 2019.3.12, after importing the latest unitypackage over an existing installation: errors stating double definition of class Animation etc were stated. So it definitely looks like a Unity cache related problem.

        The best guess I currently have is it might be the two package.json files which have recently been added to allow using spine-unity with git and the Unity package manager. Perhaps some cached files of the Unity project are incorrectly updated because of it.

        I have now removed the two package.json files from the unitypackage, a new 3.8 unitypackage is availabe for download here as usual:
        Spine Unity Download
        You could have a try whether removing the old Spine and Spine Examples directories and importing the latest package resolves your problem. Please let us know whether this resolves your problem.

        Sorry again for the trouble and thanks for reporting!

        • Kkloot

          • Допис #7
          • Цей допис на англійська

          The new update didn't fix it, but it turns out that this isn't a Spine issue but a Unity issue, basically you can't use 2019.3.12 if your solution makes use of a Assembly-CSharp-Editor-firstpass project:

          https://forum.unity.com/threads/visual-studio-2019-cant-compile-external-assets.882061/
          https://answers.unity.com/questions/1725203/visual-studio-cant-reference-to-firstpass-assembly.html?_ga=2.227159322.666949389.1588590325-402379053.1586429757

          8 днів пізніше

          Thanks very much for sharing the info, kloot!

          FYI: the issue seems fixed in the latest Unity version 2019.3.13f1.