11000+款5星资源
8.5万+用户参与评分
10万+社区成员鼎力支持
每款资源都经过 Unity 审核
显示 1 - 10 of 77
用户评论
排序
So, this asset in general is very promising. However, it is currently suffering of three major drawbacks that frankly do not allow it to be suitable for production.
1. Crashes all the time (Editor, not Runtime). Really, I'm not exaggerating. As we speak, I can consistently make it crash on Unity 6000.0.23f1 just by creating and then deleting a "Self" node. This is just an example. It crashes at the simplest actions, 80% of the times, on empty projects with no custom nodes.
2. The support does not exist. I've had at least one trivial query still waiting for a response from two weeks ago.
3. The documentation is extremely poor. The entirety of the "Full Node" page is just a recreation of a SwitchBool (a trivial scenario) and then that's it.
There seems to be a lot of potential here, but it is all unmet.
I am getting the impression that it *used* to be very good, but at some point a breaking change (either Unity or this asset) affected the stability of the entire thing, and such an issue was never addressed properly because now the developers already moved to other projects.
As it is right now, I cannot use this for production, and cannot recommend it. Maybe in the past it was great, but at present it is not a good purchase.
这条评论是否有帮助?
3
13
来自发布商的回复:
回复时间 a year ago
Hello.
1) The crashes were first introduced only in Unity v6 (which has been released quite recently) caused due to a change made in respects to undo, and therefore they were indeed very frequent since everything is undo recorded. These crashes are now fixed as of FlowCanvas version 3.3.1 released today.
2) Support is definetely existant, but please use the forums (or direct contact if you prefer) for support. All support enquiries in the forums are always answered promptly.
3) The documentation for the "Full Node" is indeed quite simple because creating custom nodes is also simple as well :) You can always also open up existing nodes to see how they are created (since source code is provided for all of them).
Best regards.
J
Unity's best Visual Scripting solution.
4 years ago
JessHarvey基于上一个版本 3.2.1
Refreshing to pick up an asset as well put together as this.
Great workflow and very well made. Source code is excellent, well commented, and very easy to work with. Picked it up and spent a few days bending FlowCanvas into weird shapes and integrating it with a myriad of other plugins, our internal architecture, and our idiosyncratic workflow requirements, with zero friction at all.
Love it, highly recommended!
这条评论是否有帮助?
7
1
I used Bolt before, but this is so much better: It has OnAwake(), functions, macro, tweenings, signals and a lot of useful nodes. Everything makes sense. It supports other assets, you just need to add classes of new asset into "Preferred Types" and you can easily control asset from FlowScript. FlowCanvas has good support, discord community, nice documentation, forum and developer is helpful.
Flowcanvas is really powerfull and you can build really good game architecture with it.
You won't regret buying it.
这条评论是否有帮助?
7
0
for me its the best VisualScripting tool/ i use it for 2 years.after i used bolt. strong in pair with nodecanvas becouse you can use FC macros there /
i choosed this VS tool cos it in balance with easy of use ,stability, speed and features/ unode is too hard for me. bolt little bit easier and slower. so FC is perfect for me/but choose yourself
这条评论是否有帮助?
2
0
M
Blown Away!
5 years ago
MCLiving88基于上一个版本 3.1.0
This app works so smoothly. It's easy to pick up and use. It looks and feels so good. If you are looking for visual scripting, this is the one!
这条评论是否有帮助?
1
0
u
Best Visual Scripting ever... I feel home again (UE4 user)
5 years ago
unity_Zf3d_qzQMfmU3Q基于上一个版本 3.1.0
I love the way it is.
=> suggestion: please offer an option to hide the shadow and alpha (Color.WithAlpha) features, it's making the graph slow and lagging in the displays of 2K resolution and above. I had to remove these features manually.
这条评论是否有帮助?
8
0
T
Very proactive
6 years ago
TomateSalat基于上一个版本 3.0.8
I've to update that review. In my previous one I've pointed out that collision events require colliders which (imho) made not much sense.
At the moment this is still the case. BUT:
1. The dev of FlowCanvas saw this comment, found me on Discord and explained me why it is like it is. So really proactive!
2. I was able to explain why I don't like this behavior and I think he got my point. Actually he send me about one hour a unitypackage with the changes.
I would say this is really outstanding! I think the changes will also make it to an official update and so my previous review lost its validity.
Thank you very much for the support :-)
这条评论是否有帮助?
12
0
高品质资源
11000+款5星资源
深受用户信赖
8.5万+用户参与评分
强大的社区支持
10万+社区成员鼎力支持