Other node tools I use, such as Behavior Designer or Animator Controller, are very fluent. Do I need to do some other settings?
Hi @meowt
This is odd. We are continuously working on improving runtime and editor performances but navigating in a graph of reasonable size should not suffer from such latency.
Could you provide us with more information?
It seems like you are showing a graph from the demo project so:
- Is it happening with all the graphs or only one specific?
- Is it happening from the first graph you open or are performance worsening the more you are using it?
- Could you provide us with details about the package version, editor version, machine specs?
The easiest way for us to investigate would be for you to open a ticket.
Thanks!
Thanks for your reply. I didn’t feel any delay in a newly created Behavior Graph. I think it’s the 30+ nodes that cause the delay in dragging. Maybe use more sub-Behavior Graphs to reduce the number of nodes in a Behavior Graph?
Thanks for the info, we are in the process of doing more editor and runtime performance profiling.
We will make sure to investigate that area.