24 red errors after import nodeCanvas in Unity 2018.6f1

Forums › 💬 NodeCanvas › ⚙️ Support › 24 red errors after import nodeCanvas in Unity 2018.6f1

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • September 20, 2018 at 12:47 pm #17140
    randalthor
    Participant

      Hi,

      Like in the topic i get many errors after importing nodeCanvas into Unity.

      They are looking like these examples:

      Assets/ParadoxNotion/NodeCanvas/Modules/BehaviourTrees/Nodes/Leafs/NestedFSM.cs(36,16): error CS0029: Cannot implicitly convert type FSM' toNodeCanvas.Framework.Graph’

      Assets/ParadoxNotion/NodeCanvas/Modules/BehaviourTrees/Nodes/Leafs/NestedFSM.cs(37,26): error CS0030: Cannot convert type NodeCanvas.Framework.Graph' toFSM’

      Assets/ParadoxNotion/NodeCanvas/Modules/BehaviourTrees/Nodes/Leafs/NestedFSM.cs(40,68): error CS0029: Cannot implicitly convert type FSM[]' toNodeCanvas.Framework.Graph[]’

      Assets/ParadoxNotion/NodeCanvas/Modules/BehaviourTrees/Nodes/Leafs/NestedFSM.cs(46,39): error CS1061: Type FSM' does not contain a definition forprimeNode’ and no extension method primeNode' of typeFSM’ could be found. Are you missing an assembly reference?

      Can you help?
      I already closed and reopened Unity without a difference for the errors.

      September 20, 2018 at 5:16 pm #17142
      randalthor
      Participant

        I also tried it now with Unity 2018.2.8f1 without success and because i also have your other asset installed i checked that the framework folder is not doubled in the project.

        September 21, 2018 at 3:54 pm #17141
        Gavalakis
        Keymaster

          Hello,

          It looks like that there is another asset in your project (or part of your own code), that also uses the name “FSM”, but which is not encapsulated into a namespace, which as a result can create conflicts. It is advisable for all assets or code to be put into namespaces to avoid such conflicts and all NodeCanvas classes are indeed in their own namespace.

          If that other “FSM” named class is part of your own code, I would advice you to please put that class into a namespace.
          If that other “FSM” named class is part of another asset, then probably kindly asking the developer of that asset to put their classes in a namespace, would be the best solution.

          Thank you.

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