Unreal Crashes everytime I hit save all. Started after behavior trees

Development Programming & Scripting AI
, , , ,
1

I can’t seem to be able to save anymore. Everytime I work on something the engine crashes without any notice. It was working good today, but it all started when I implemented behavior trees. I’m 4.4.

This is the error:

Fatal error!

Address = 0xee8653dc (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee78f302 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee750994 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee879be7 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee7b2c3d (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee823886 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee760cc5 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee7a2c08 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xee7742a2 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-CoreUObject.dll]
Address = 0xe57e6ff2 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-Core.dll]
Address = 0xe57e717d (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-Core.dll]
Address = 0xe57f41eb (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-Core.dll]
Address = 0xe5a22c16 (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-Core.dll]
Address = 0xe5a1c1dd (filename not found) [in D:\unreal4444\Unreal Engine\4.4\Engine\Binaries\Win64\UE4Editor-Core.dll]
Address = 0x776d59ed (filename not found) [in C:\Windows\system32\kernel32.dll]
Address = 0x7790c541 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]
Address = 0x7790c541 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]

Crash in runnable thread TaskGraphThread 0

2

If you go into the Documents Folder > Unreal Projects > Your Project > Content and manually remove any of the Behavior Tree assets that you’ve created before the problem does this allow it to open and save again?

Also, do you have a version of your project before you added behavior trees?

3

Yes, I can save now, but that means I can’t use my old behavior trees @_@. I’m using 4.4 I think I’ll just redo the whole thing.

4

Are you able to provide the crash logs and dmp files for this? (Documents > Unreal Project > Your Project > Saved > Log > Crash and DMP file) (May be best to clear this out and have it crash again to get the two files that are fresh) If you can, can you provide the project or the Behavior tree assets for testing? This is definitely something I would like to report for a developer to look into more since you were not able to save with the behavior tree assets in place.

If you decide to send the project and you do not want to post it here you can send a download link via the forums in a PM.

Thank you!
Tim

5

O’right I sent you a pm.

6

Sorry for the delay in getting back to you on this one. But testing the folder and files you’ve sent. Are you still getting the crash from your behavior tree assets with your project?

7

I deleted the whole thing and started over. I’m limiting my behavior trees to view nodes, and making most of the work in blueprints. My project.stopped working though when I upgraded to 4.4.1 from 4.4.0. I already reported elsewhere.

Just one question. Is it true that epic will be releasing RTS template this month? My project could really use one!

8

Hello Valkon,

We are wondering if you are still experiencing your behavior tree issue or if you were able to resolve this with any future build. We are currently on version 4.6 and suggest that if you are still experiencing your issue to try and update. There were a lot of great fixes and implementations in 4.5 and 4.6 that could potentially resolve your issue. Let us know if this is the case or if you need further assistance.

Cheers,