NodeCanvas 2.97 + Utility 6 issue

[com8u8Participant]

Hello, currently I am using Unity 6 along with NodeCanvas 2.97. Originally, I intended to upgrade to nodecanvas 3.4.1, but I found that version 2.97 is fully supported in the Unity 6 environment. Instead, upgrading to 3.4.1 will require replacing many components. Could you please tell me what specific tests I should conduct to ensure the full support of 2.97 in the Unity 6 environment, or which aspects are most prone to issues?

[GavalakisKeymaster]

Hello and sorry for the very late reply!

Probably the issues that you will encounter would be related to Unity related API changes. However most of them should be automatically upgradable by Unity, while other may not. Other than Unity related API changes there are no other tests really necessary to be made. If you resolve the potential API changes then things should work out correcty. However I would still highly recomend to update to NodeCanvas 3.x eventually since there are really a lot of great features (and some bug fixes along the way) that are definetely worth it 🙂

Best regards : )

[com8u8Participant]

Thank you for your reply. After a long period of testing, the current situation I have encountered is as follows: After upgrading to Unity 6, version 2.97 can run normally. However, in some aspects, such as animation control, it may be more laggy than before, causing graphical issues in the program. We also attempted to upgrade to version 3.41 separately, but encountered more problems. However, all these problems have been eventually resolved. Compared with version 2.97, the upgrade process is prone to causing the program to get stuck in the program flow. Could you please tell me in which aspects upgrading might cause the program to get stuck? And what should I pay attention to?

[GavalakisKeymaster]

Hello again and sorry for the rather late reply.

There were realy a lot of core things that changed in version 3.0.0 (for the better of course!) and kept changing (although more minor) up to current version 3.4.2. Version 3.x was a big leap. There wer though some things that could break. From the change log online:

Breaks (sorry)

• DialogueTree -> SubDialogueTree Variable Mappings will need to be re-set.
• Blackboard overrides on Prefab Instances will be reverted to the Prefab Asset. (Due to new serialization to properly support Variable Overrides).
• Bound Graph overrides on Prefab Instances will be reverted to the Prefab Asset. (Due to a Unity bug with [FormelySerializedAs] -> https://bit.ly/37T6CaE ). There is a way around this though. Please contact support if this is an issue for you.

 

Do any of these seem related to the breaks you encounter?

Let me know, thanks 🙂

[Author]

Posts