1.5.8 NC Bug in Unity4.5.2

Forums 💬 NodeCanvas ⚙️ Support 1.5.8 NC Bug in Unity4.5.2

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #19582
    unigames
    Participant

      Hi,Gavalakis
      Thank you for your work in NC 1.5.8!
      But I can’t use script control actions in unity after updated NC to 1.5.8.
      All the items of menu are unavailable.
      My Unity version is 4.5.2f1.
      Is this a compatibility problem ?

      #19591
      Gavalakis
      Keymaster

        Hello,

        You are welcome 🙂
        Hm. That must be a MAC issue with Unity’s Menu Seperators if I recall correctly.
        Can you please try and remove the code in EditorUtils.cs at line #936 under GetMethodSelectionMenu and let me know if it works?

        The code to remove is this:

        Thanks!

        #19590
        alexk
        Participant

          I had the same issue on Mac. Removing the code fixed it.

          #19589
          alexk
          Participant

            I had the same issue on Mac. Removing the code fixed it.

            #19588
            Gavalakis
            Keymaster

              Great.

              Glad to know that was the issue. Thanks

              #19587
              alexk
              Participant

                I wonder if it’s also Mac related, but when I try to switch to ‘External Inspector’, the ‘NC Inspector’ window that opens is empty.

                #19586
                Gavalakis
                Keymaster

                  The External Inspector will show the inspector of whatever node you have selected into the NodeCanvas Editor Window.
                  Is it empty even if you have selected a node?

                  #19585
                  alexk
                  Participant

                    Yes, it’s empty all the time, no matter what node I click on in the NodeCanvas window. Having experienced the bug originally mentioned in this post, it seems that the External Inspector problem may be something similar (both Mac-specific and that could be resolved by fixing a small piece of incompatible code). Thanks for following up about it.

                    #19584
                    alexk
                    Participant

                      I’m also using Unity 4.5.2f1.

                      #19583
                      Gavalakis
                      Keymaster

                        Hmm. Seems to be a Mac issue as well considering that it’s working find on my Windows PC.
                        I will take a loot at it for finding what might be the issue exactly.
                        Thanks

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