DirtyHippy
New member
Note: 2018.4.13
1) Fix tooltips so they don't get clipped on the left side. This happens on both my primary and secondary monitor.
2) Remember the location in an external tree (in each tree) that you were last looking at rather than resetting to the default position if you inspect something else and then come back.
3) Add bookmarks for large trees. Right now I use external trees even for things that aren't reusable simply because it makes it easy to jump right to the subset I want when editing. It would be nice at run-time for these to work too somehow. It gets very tedious debugging behaviour trees and having to scroll each time to where you want to look especially for larger trees with hundreds of nodes.
4) Add free-form commenting to the trees including changing the font size (so I could put, for example, a larger header next to each subtree so when I am debugging the full tree I can look at the headers as I try to find what I am looking for).
5) Add comment frame (i.e. let me drag a box out around a subset of functionality so I can frame it). No need to worry about nested nodes in that frame (and moving them with it). Just something simple for framing commenting or logical boundaries.
6) I would love the ability to add a comment for tree variables - basically just some meta in case I forgot what it was used for.
7) Move the shared variable tasks out of the "Unity" category. This is just an opinionated nitpick. They aren't unity specific tasks. They are behaviour designer specific tasks. I search most of the time anyway so for me it doesn't matter much.
8) I've wished several times I could run a node before a conditional abort pulls me out of a subtree. Some kind of reset that allows me to say "oh, I'm being aborted, I better do some stuff before I bail out to reset my state". I can envision how aborts are implemented, and I know this isn't how the tree logic works. But still - it would be pretty sweet.
9) Layout is weird. I'm guessing there are issues with pixel rounding, but if you are zoomed out it doesn't give you as much granularity placing nodes as when zoomed in which can lead to weird inconsistencies (unless you do all node placement fully zoomed in, which I have gotten into the habit of doing).
In any event, excellent tool. Really clean and powerful!
1) Fix tooltips so they don't get clipped on the left side. This happens on both my primary and secondary monitor.
2) Remember the location in an external tree (in each tree) that you were last looking at rather than resetting to the default position if you inspect something else and then come back.
3) Add bookmarks for large trees. Right now I use external trees even for things that aren't reusable simply because it makes it easy to jump right to the subset I want when editing. It would be nice at run-time for these to work too somehow. It gets very tedious debugging behaviour trees and having to scroll each time to where you want to look especially for larger trees with hundreds of nodes.
4) Add free-form commenting to the trees including changing the font size (so I could put, for example, a larger header next to each subtree so when I am debugging the full tree I can look at the headers as I try to find what I am looking for).
5) Add comment frame (i.e. let me drag a box out around a subset of functionality so I can frame it). No need to worry about nested nodes in that frame (and moving them with it). Just something simple for framing commenting or logical boundaries.
6) I would love the ability to add a comment for tree variables - basically just some meta in case I forgot what it was used for.
7) Move the shared variable tasks out of the "Unity" category. This is just an opinionated nitpick. They aren't unity specific tasks. They are behaviour designer specific tasks. I search most of the time anyway so for me it doesn't matter much.
8) I've wished several times I could run a node before a conditional abort pulls me out of a subtree. Some kind of reset that allows me to say "oh, I'm being aborted, I better do some stuff before I bail out to reset my state". I can envision how aborts are implemented, and I know this isn't how the tree logic works. But still - it would be pretty sweet.
9) Layout is weird. I'm guessing there are issues with pixel rounding, but if you are zoomed out it doesn't give you as much granularity placing nodes as when zoomed in which can lead to weird inconsistencies (unless you do all node placement fully zoomed in, which I have gotten into the habit of doing).
In any event, excellent tool. Really clean and powerful!