Reply To: Some Feature Suggestions

[Gavalakis]

Hello!

Thank you for taking the time to write these suggestions.
Please let me address those in order:

Avoid argument data loss on refactoring.
This is a really good point. I will try retain arguments when re-assigning methods if their name/type match automatically.

Search by method/property name.
Jump to next graph error.
There are already a few more utilities coming in the new version (eg a specialized graph debug console that clicking errors, automatically focuses relevant nodes in graphs). Search utilities are definitely next in the convenience utilities line 🙂

Error icon near the unity object in hierarchy inspector.
The new Debug console in the upcoming version is going to certainly help in this, since by clicking the errors in that new console, it automatically opens up the relevant graph AND focuses the relevant node. I think it’s really handy and hopefully you will find it so too!

Nodes render performance.
Node rectangle overlap with view rectangle, is already checked. Actually, nodes (as well as connections) that are outside of view, are completely not rendered at all. With that said there have been some improvements in the next version, where I found out that the graphical grid was causing a lot of performance overhead when the graph is zoomed out, and that is now thankfully fixed!

Use Time.unscaledDeltaTime instead of Time.deltaTime.
Hmm. Just to confirm. Are you referring to the Time.timeScale usage in the BehaviourTree.OnGraphUpdate method?

Once again, I will take a look at your first suggestions once after the new version is out!
If you have any more, by all means they are very welcome.

Thanks!

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