[BUG] NodeCanvas / FlowCanvas bridge is broken.

NodeCanvas Forums Support [BUG] NodeCanvas / FlowCanvas bridge is broken.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #15490
    guyboots_thunderbro
    Participant

    Using the latest asset store release, January 11th release:

    [19:35:12:375] Assets/ParadoxNotion/_NC_FC_Bridge/NC Nodes/FlowScriptState.cs(57,26): error CS1061: ‘FlowScriptState’ does not contain a definition for ‘TryReadAndUnbindMappedVariables’ and no accessible extension method ‘TryReadAndUnbindMappedVariables’ accepting a first argument of type ‘FlowScriptState’ could be found (are you missing a using directive or an assembly reference?)

    #15491
    Gavalakis
    Keymaster

    Hello,
    Are you using both the latest Bridge version, as well as the latest NodeCanvas/FlowCanvas versions from the asset store please?

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

    #15495
    guyboots_thunderbro
    Participant

    Yes. I’m using the latest versions of both NC and FC from the asset store, as well as the latest version of the bridge from the download page.

    #15498
    Gavalakis
    Keymaster

    Hello,
    I just tried for confirm and downloaded all the latest versions (asset store and website and I don’t see any problems). Hmm.
    Can you please open up IGraphAssignableExtensions.cs file and confirm that there is indeed a method inside called “TryReadAndUnbindMappedVariables”? (it is an extension).
    Also please try removing previous versions completely and re-import the new versions anew. Maybe for some reason the previous version file is still there and the new one not overwriting it.

    Please let me know.
    Thanks

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

    #15500
    guyboots_thunderbro
    Participant

    I do not have a method by that name in IGraphAssignableExtensions.

    I’ve gone through several older project prototypes on older versions of NC/FC + Bridge and FlowScriptState is using “this.TryReadMappedVariables” instead of “this.TryReadAndUnbindMappedVariables();” in all of them.

    FlowScriptState is the only file using “TryReadAndUnbindMappedVariables”. The “OnExit” functions in several other files in NodeCanvas are all using “TryReadMappedVariables” — SubDialogueTree, nestedBTState, NestedFSMState, etc.

    Was “TryReadAndUnbindMappedVariables” a new introduction? What version did it show up in? Is it possible that somehow my asset store version is out of date? I’m on 3.1.8, January 08th 2021 version according to the asset store, but the version number in my graph canvas says “@NodeCanvas Framework v3.16”

    #15504
    guyboots_thunderbro
    Participant

    [Sigh]

    Sorry. It looks like Unity’s built-in package manager absolutely lost its mind at some point, and was reporting that I had the latest version of everything installed. As it turns out, I didn’t, but a re-install of Unity seems to have sorted out the package manager… for now.

    False alarm. Just… Unity-stuff.

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