3.2.5 Errors & 2022

NodeCanvas Forums › Support › 3.2.5 Errors & 2022

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • April 3, 2022 at 6:38 pm #16193
    greymark
    Participant

    Just did a clean project + 3.2.5.  In 2020 all was fine.  In 2022, errors:

    Assets\ParadoxNotion\NodeCanvas\_DeprecatedFiles\Legacy_ConcurrentState.cs(14,18): error CS0101: The namespace ‘NodeCanvas.StateMachines’ already contains a definition for ‘ConcurrentState’

    Also, on Discord, a week or two ago,  I mentioned an issue with Flow & Node & Bridge together. I should have mentioned that this was also 2022.  I just tested this in 2020 and its fine.  2022 is the issue.

    I have Node & Flow and this warning pops up.  Thoughts?  Cannot add menu item ‘Tools/ParadoxNotion/More Tools…’ for method ‘NodeCanvas.Editor.Commands.VisitHome’ because a menu item with the same name already exists.

    UnityEditor.MenuService:GetMenuItemsFromAttributes ()

     

    April 3, 2022 at 7:58 pm #16194
    Gavalakis
    Keymaster

    Hello,

    Please try complete deleting the folder “CanvasCore”, “NodeCanvas” and “FlowCanvas” and re-import the asset anew and let me know if that works for you. The warning you mention has also been fixed in the latest version which went like just a few hours ago 🙂

    Let me know.

    Join us on Discord: https://discord.gg/97q2Rjh

    April 3, 2022 at 8:02 pm #16195
    greymark
    Participant

    Have you tested in Unity BETA 2022?  Today I created brand new projects in Unity 2020 and Unity 2022.  Then I imported your assets.  In 2020 everything worked great.  Only in 20222 did I get the errors.

    April 4, 2022 at 7:44 pm #16201
    Gavalakis
    Keymaster

    Hello,

    Please note that beta Unity versions are not supported since Unity may change things the next day, however I just try importing NodeCanvas from the Unity Asset store (package manager) on a new clean project of Unity 2022 Beta and there wasn’t any issues. Please note that once imported a message pops up by Unity to upgrade deprecated API within which I selected to do it.

    Do you still get the same error you posted at the top on a new clean Unity 2022 project?

    Let me know. Thank you.

    Join us on Discord: https://discord.gg/97q2Rjh

    April 4, 2022 at 9:40 pm #16202
    greymark
    Participant

    Your right.  I did a clean Unity 2022 project before creating the thread, but it appears I had not downloaded the latest version on one of my two dev machines.  The 3.2.5 compiled fine with both Flow and Node.  Sorry for the false alarm.

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