0
Fixed

GraphPointerException after exiting timer + toggle in super unit

Elin 3 months ago updated by Lazlo Bonin (Lead Developer) 3 months ago 5

I'm sorry to open up this thread again, but the problem is in 1.4.6f3 in Unity 2018.4 still present.
The error appears, as soon, as the timer node is finished.

Bolt Version:
1.4.6f3
Unity Version:
2018.4
Platform(s):
Scripting Backend:
.NET Version (API Compatibility Level):
GOOD, I'M SATISFIED
Satisfaction mark by Elin 3 months ago
Pending Review

Hi Elin, thanks for the report, I split your comment in a new thread as the previous issue had been fixed.

Can you show or send me a minimal graph in which the issue happens? That would speed things up for me!

Create an macro in in the project.
Add input, 2 output and timer node. Connect the tick and the completed port from the timer to the output.
Create Flow Machine on game object in hierarchy (it can be an macro or embed)
Drag in the created Super unit. Make input event a coroutine and hit play.
I'm using 2019.2 and 2018.4 and bolt 1.4.6

Working on Fix

Thanks! I understand what's happening now.

In the timer's internal update, flow exits the super unit on Tick.

But then, right after, it calls Completed, but the flow has already exited, so it gets confused.

I'll have to special case this somehow.

+2
Fixed (Unreleased)

Good news, was able to fix it pretty easily, will land in v.1.4.7.

I also did basically the same fix for the Cooldown unit.