All the bound FSM trees have disappeared

Forums 💬 NodeCanvas ⚙️ Support All the bound FSM trees have disappeared

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #17898
    e-cone
    Participant

      Hello!
      I was using NodeCanvas for quite some time now. Everything worked fine until I decided to upgrade Unity from 5.5.2 to 5.6.
      Then suddenly all the bound FSM trees disappeared, and console logged following “GameObject (named ‘Room1’) references runtime script in scene file. Fixing!” for each FSM owner. When I pressed Play twice – FSM trees re-appeared, and I saved them as assets. I continued working with bound FSM trees and suddenly after new code compilation they’ve disappeared completely. FSM trees I saved as assets are very outdated right now. Is there any way to recover bound FSM trees?

      #17902
      anglo
      Participant

        I’ve had the same problem.

        #17901
        Gavalakis
        Keymaster

          Hello,

          @e-cone
          Hmm.. When you did the upgrade to U5.6, what version of NodeCanvas you were using?
          Support for Unity 5.5+ has been added in NodeCanvas 2.6.2+ (released 5 months ago), which version came along with a button to “Upgrade Project” from previous NodeCanvas versions and which button is shown in inspectors of Bound Graph Owners if required. Have you came along this button and thus run this upgrade before?

          Let me know.

          @anglo
          I have replied to your other post about similar problem.

          #17900
          e-cone
          Participant

            @Gavalakis, this project is rather old, so I didn’t upgrade NodeCanvas there since last year. Version I’m currently working with is 2.5.6.

            #17899
            Gavalakis
            Keymaster

              Hello again,

              Unfortunately NC 2.5.6 (quite old) does not support Unity 5.5 or 5.6 (I am not sure how it even worked in 5.5 in the first place).
              Support for Unity 5.5+ has officially been added in version 2.6.2 (released 5 months ago).
              I suggest that you update your NodeCanvas to latest version from the asset store while still in a working version of Unity you had, and only after that update Unity to 5.6, so that everything is updated in the correct order.

              Thanks.

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