The abilityTask(AbilityTask_WaitForInteractableTargets , UAbilityTask_WaitForInteractableTargets_SingleLineTrace) is copied from Lyra Project , and used in the Ability_Interact just like Lyra.
No, I haven’t figure it out. As long as I do not open that gameplay ability blueprint, it will not happen.
I think it is related to the uninitialzation of the gameplayabilitytask that editor created.
I had this problem too on a custom Gameplay Task, and managed to resolve it by making sure EndTask() was not being called twice for the same ability task. More specifically in my case, EndTask() called a function on another object, which in turn called EndTask() again before the task was even fully destroyed. I hope this helps!
When searching for this in code, there is a comment stating that if you are seeing this message that a ability was destroyed while being active.
If there is a Ability Task in my project, and If working with Live Coding, the editor will usually always crash on close with this “Assertion failed: GlobalAbilityTaskCount > 0” message. I can get this to happen in a fresh install of Lyra, and also in a blank project that has the Gameplay Abilities plugin enabled and a UAbilityTask class added. I have tested this on two computers. Live Coding and Ability Task do not play nice together.
When testing in the Lyra project, anything done to most of the classes within the LyraGame folder will cause this crash on editor close when compiling with Live Coding. It does not even need to be a code change. This includes LyraCharacter, LyraCharacterMovementComponent, and LyraCameraMode. It does not seem to break the project because it still can be compiled and packaged. If the LyraGame/Interaction/Tasks folder is removed, the crashing stops. And if any of the task are put back, the crashing returns
I think that the crashes I’m dealing with are mentioned at the very end of the Live Coding docs. It also mentions working with two new delegates that were added in 5.1, but there is no info on how, where, or if they should be used here. There not used anywhere in the Lyra project.
Hello, the 5.2 version I am currently using also has this problem, my solution is to remove the parameters corresponding to the constructor of the custom C++Task class, like this, and then test again without crashing after closing the editor. I hope it was helpful.
