A brand new laptop, Unity 5.5.0f3 and a very recent NC 2.6.?. The projects were unitypackages from a prior version of Unity we loaded on the new device.
Assets/ParadoxNotion/NodeCanvas/Framework/Design/Editor/Windows/GraphEditor.cs(284,18): error CS1501: No overload for method SmoothDamp' takes4′ arguments
Any ideas? Didn’t want to touch anything since nothing really stood out to me and I didn’t to overthink the issue.
Did the unity script API upgrader run automatically? If not, run it from the “Assets/Run API Updater” menu item. 2.6.2 relies on some automatic API upgrades. In my case it didn’t run when I imported the new package into a larger project.
If you can’t get the API updater to run (e.g. the menu item is disabled), my workaround was to import the package into an empty project, let the API updater do its job and then copy the node canvas folder over to the actual project.
@emmcd
Did you resolve the issue running API updater?
It looks like though that you don’t have the latest version of NC (2.6.2) because SmoothDamp specifically was changed to work the same in all Unity version above 5.3 Have you downloaded and imported latest NC from the asset store?
Please let me know.
Thanks.
Okay, the place we’re at is it appears that the upgrade was the right play. It hasn’t completed a full compile as we now to address the remaining issues with Embersoft with the FinalIK & AStar packages. Will let know as progress is made. I am assuming the are not backwardly compatible with a previous version of Unity 5.4.3?? Let me know.
Late Update…there does not appear to be any any BT or sub-tree which has successfully loaded. A repeated message of such and such Graphowner being used in runtime and not updated to 2.6.2. Below on BT owner is bar with “Update Project” display. It is an NC message I believe but the first time I seen it..
The “Update Project” appearing in the inspector is indeed a NodeCanvas button. Please backup your project first and then hit the “Update Project” button so that your project’s existing graphs are updated to work correctly with the latest NC version 2.6.2.
After this is done everything should work fine once again.
Please let me know if you encounter any issues after you Updated the Project.
I wish it were that simple but thanks for the procedural clarification. Right now, however, we are pulling a tactical retreat to Unity 5.4.3. As that was the last OS functioning well. What was experienced was a perpetual fatal error regarding memorystream corruption. It would occur on the second play event, over and over again. We have Unity bug report with regards to that occurrence. Not sure if this is mere cooincidence, but, after the removal of NC 2.6.2, as an experiment, and then entering play mode 15 – 20 times, Unity didn’t crash. So, to my prior question is 2.6.2 backwardly compatible with 5.4.3. WE are assuming not.
Cheers and I will keep you apprised as thing progress.
Author
Posts
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic.
Login
Register
By registering on this website you agree to our Privacy Policy.