2.6.2 compatibility with 5.5.0f3

Forums 💬 NodeCanvas ⚙️ Support 2.6.2 compatibility with 5.5.0f3

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #18229
    zsoik
    Participant

      I just downloaded and imported NodeCanvas 2.6.2 from the asset store into a 5.5.0f3 project and I get tons of compile errors, mostly because of NavMesh/NavMeshAgent APIs.

      I then imported it into a blank project and after the import, the Unity API updater popped up and asked me to upgrade scripts because of outdated API usage. That worked, the NC barebones project is compiling properly.

      Copying the upgraded scripts to the actual target project left me without compilation errors.

      Don’t know if this is intended, if it is, I don’t know why the API updater wouldn’t show up in the first project.

      (Side note: How do I find out which NC version I currently have installed? I first thought that maybe the asset package was not downloaded properly and I accidentially had imported an older version)

      #18234
      Gavalakis
      Keymaster

        Hello,

        Actually this is intentional so that the package can be used in older Unity versions too, but you can run the Unity API updater manually at any time, through Unity’s top menu (Assets/Run API Updater…).
        I think though that in the next version, I will just go and put #if UNITY_5_x directives for those parts of the code for clarity.

        Regarding current version number, it’s only shown in the NodeCanvas editor, but that of course needs it to be successfully compiled first 🙂
        I will add the version number in the ReadMe file included from now on.

        Thanks!

        #18233
        jacobbijani
        Participant

          I had a similar issue, but there were a lot of compilation errors related to missing methods within “EditorUtils”. I had to make the following changes manually to get rid of the compilation errors.

          2.6.2 compatibility with 5.5.0f3 as well, installing fresh on an existing project.

          #18232
          Gavalakis
          Keymaster

            Hey Jacob. Sorry but I missed your reply here.
            That looks like a conflict with another class that probably exists in your project named “EditorUtils”, but which seems to not be part of a namespace, but rather part of the “global” namespace.

            #18231
            jacobbijani
            Participant

              yep, that looks right actually. thanks for the follow up.

              I’d also add a strong vote for using UNITY_5_x directives throughout instead of relying on the API updater. first, it gave me a bad first impression of your library (“is this thing broken?!”) and second, if the project has any syntax errors (for example, a namespace conflict as I had…) the auto updater will not run until those errors are fixed. this forced me to dig into your code and “fix” them myself before it could run.

              #18230
              Gavalakis
              Keymaster

                Hey,
                I agree with you. The next version will not rely on the AutoUpdater any more, but rather using directives.
                Thanks for your feedback.

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.