Daniel Everland
New member
If your Behavior Designer folder lies within an assembly definition you've created, you'll be unable to create any external behaviors. To fix this Behavior Designer has to be setup properly with its own assembly definitions, which it is not when using 1.6.1 from the asset store. I have confirmed, though, that this is not a new issue. I could reproduce in my repo since February 8th. I'm currently using 2018.3.6f1
Steps to Reproduce
1. Create new project
2. Import Behavior Designer 1.6.1 from Asset Store
3. Create an assembly definition in root folder
4. Create external behavior using Assets>Create>Behavior Designer>External Behavior Tre
> A nullref will be thrown
Steps to Reproduce
1. Create new project
2. Import Behavior Designer 1.6.1 from Asset Store
3. Create an assembly definition in root folder
4. Create external behavior using Assets>Create>Behavior Designer>External Behavior Tre
> A nullref will be thrown
Code:
NullReferenceException
BehaviorDesigner.Editor.AssetCreator.CreateAsset (System.Type type, System.String name) (at <6224ec08a63b4190a0704159812b1ad4>:0)
BehaviorDesigner.Editor.AssetCreationMenus.CreateExternalBehaviorTree () (at <6224ec08a63b4190a0704159812b1ad4>:0)