Hello!
#1) Let's start with the simple one:
Allow Ctr+C and Ctr+V to copy paste Variable strings from the Behaviour Designer editor window.
This drives me crazy every time I have to re-type it into notepad to be able to correctly remember the correct typing
#2) The 2nd is more important but more difficult to explain:
When using a Behaviour-Tree-Reference-Task I'm able to set kind of a variable mapping. What actually happens is that all(?) instances of the relevant variable in the references BT are replaced with the mapped one (but the variable still exist in the variables list).
My problem occurres when referencing another BT inside the first referenced BT
Like: [Main BT] - [Ref1 BT] - [Ref2 BT]
This is the most simple test case but of course this applies to any reference depth > 1
Again I set a variable mapping from the already mapped var in [Ref1 BT] to the one I want to override in [Ref2 BT]
What should happen:
The variable from [Main BT] will replace all instances of the mapped var in [Ref1 BT], then all instances of the mapped var in [Ref2 BT] will also be replaced by this var from [Main BT]
What does happen:
The mappings are not propagated recursively from [Main BT] to [Ref2 BT] but instead its only [Ref1 BT] to [Ref2 BT] and [Main BT] to [Ref1 BT]. For this use case [Ref2 BT] ends up with a 'dead' variable as the orignial - unmapped [Ref2 BT] var is just a placeholder that needs to be mapped to a var that actually holds a value (the one from [Main BT])
What should be changed:
The mapping should run recursive by first replacing the vars in [Ref1 BT] including(!) the vars in the Behavour-Tree-Reference-Task. Then propagate down from [Ref1 BT] to [Ref2 BT] to [RefN BT].
This is imo a very important feature as I often use very abstract BTs which bit act like compound Tasks. In these cases I want to have a specific scope for my vars. And because I often end up having multiple levels of referenced behaviour trees this leads to the described problem.
Kind regards
#1) Let's start with the simple one:
Allow Ctr+C and Ctr+V to copy paste Variable strings from the Behaviour Designer editor window.
This drives me crazy every time I have to re-type it into notepad to be able to correctly remember the correct typing
#2) The 2nd is more important but more difficult to explain:
When using a Behaviour-Tree-Reference-Task I'm able to set kind of a variable mapping. What actually happens is that all(?) instances of the relevant variable in the references BT are replaced with the mapped one (but the variable still exist in the variables list).
My problem occurres when referencing another BT inside the first referenced BT
Like: [Main BT] - [Ref1 BT] - [Ref2 BT]
This is the most simple test case but of course this applies to any reference depth > 1
Again I set a variable mapping from the already mapped var in [Ref1 BT] to the one I want to override in [Ref2 BT]
What should happen:
The variable from [Main BT] will replace all instances of the mapped var in [Ref1 BT], then all instances of the mapped var in [Ref2 BT] will also be replaced by this var from [Main BT]
What does happen:
The mappings are not propagated recursively from [Main BT] to [Ref2 BT] but instead its only [Ref1 BT] to [Ref2 BT] and [Main BT] to [Ref1 BT]. For this use case [Ref2 BT] ends up with a 'dead' variable as the orignial - unmapped [Ref2 BT] var is just a placeholder that needs to be mapped to a var that actually holds a value (the one from [Main BT])
What should be changed:
The mapping should run recursive by first replacing the vars in [Ref1 BT] including(!) the vars in the Behavour-Tree-Reference-Task. Then propagate down from [Ref1 BT] to [Ref2 BT] to [RefN BT].
This is imo a very important feature as I often use very abstract BTs which bit act like compound Tasks. In these cases I want to have a specific scope for my vars. And because I often end up having multiple levels of referenced behaviour trees this leads to the described problem.
Kind regards