Editor crash on Behavior Tree rename when using "Run Behavior" node

Development Programming & Scripting AI
, , ,
1

Alright…finally figured out the legit repro steps here:

  1. Create a new behavior tree called “TestA”
  2. Create a new behavior tree called “TestB”
  3. Hookup a “Run Behavior” node in “TestA” that references “TestB”
  4. Save “TestA”
  5. Rename “TestA” to "TestAAA"
  6. Open the renamed behavior tree “TestAAA”
  7. Make any edit (like just knudge a node position) and save that behavior tree.

BOOM! Crashes every time!!! That bolded step seems to be the main culprit. Makes working with the “Run Behavior” node near impossible. It’s CRAZY unstable. To be honest, I think there are other ways to repro this bug, but this is the easiest.

[2016.12.19-19.06.51:942][256]LogSourceControl: Attempting ‘p4 fstat -Or C:/UnrealEngine/Prizefighter/Content/Global/AI/BehaviorTrees/Base_Turret_AIBT.uasset’
Ensure condition failed: ToPin->LinkedTo.Contains(this) [File:C:\UnrealEngine\UnrealEngine\Engine\Source\Runtime\Engine\Private\EdGraph\EdGraphPin.cpp] [Line: 292]
UEdGraphPin::BreakLinkTo Pin ‘Out’ on node ‘Selector’ not reciprocally linked with pin ‘In’ on node ‘Run Behavior’
[2016.12.19-19.06.51:967][256]LogOutputDevice:Error: Ensure condition failed: ToPin->LinkedTo.Contains(this) [File:C:\UnrealEngine\UnrealEngine\Engine\Source\Runtime\Engine\Private\EdGraph\EdGraphPin.cpp] [Line: 292]
[2016.12.19-19.06.51:967][256]LogStats: FDebug::EnsureFailed - 0.000 s
UE4Editor.exe has triggered a breakpoint.

2

Hello ,

I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide any small steps that may have been left out of your original post?
  3. Could you provide screen shots of your behavior tree?
  4. Does this still occur for you in the latest release of the engine (4.14.1 as of post)?
3

Hello ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

Thanks,