0
Cannot Reproduce

Oversight of automated coroutine stop. 1.4.0f10

Crystalius 12 months ago updated by Lazlo Bonin (Lead Developer) 12 months ago 4

Sending macro for Lazlo via Discord


Error: 

NotSupportedException: Stop may only be called on coroutines.
Bolt.Flow.StopCoroutine ()
Bolt.EventUnit`1[Bolt.EmptyEventArgs].StopListening (Ludiq.GraphStack stack)
Bolt.FlowGraph.StopListening (Ludiq.GraphStack stack)
Bolt.SuperUnit.StopListening (Ludiq.GraphStack stack)
Bolt.FlowGraph.StopListening (Ludiq.GraphStack stack)
Bolt.FlowStateTransition.OnExit (Bolt.Flow flow) (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.State/Runtime/FlowStateTransition.cs:81)
Bolt.State.OnExit (Bolt.Flow flow) (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.State/Runtime/State.cs:194)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
Bolt.Flow:StartCoroutine(ControlOutput, ICollection`1)
Bolt.EventUnit`1:Run(Flow)
Bolt.EventUnit`1:Trigger(GraphReference, EmptyEventArgs)
Bolt.<>c__DisplayClass14_0:b__0(EmptyEventArgs)
Bolt.EventBus:Trigger(EventHook, EmptyEventArgs) (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.Core/Runtime/Events/EventBus.cs:65)
Bolt.EventMachine`2:TriggerRegisteredEvent(EventHook, EmptyEventArgs) (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.Core/Runtime/Events/EventMachine.cs:42)
Bolt.EventMachine`2:TriggerEvent(String) (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.Core/Runtime/Events/EventMachine.cs:14)
Bolt.EventMachine`2:FixedUpdate() (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.Core/Runtime/Events/EventMachine.cs:99)

Bolt Version:
Unity Version:
Platform(s):
Scripting Backend:
.NET Version (API Compatibility Level):
GOOD, I'M SATISFIED
Satisfaction mark by Crystalius 12 months ago
+1

Hi Crystallius,

This macro depends on a bunch of variables and other macros that aren't available, so I can't really test it easily.

Can you try to isolate the issue in the transition that fails?

Cannot reproduce it in an empty macro. Tried using super unit with coroutines inside transition's code, everything works as it should. There must be something else in my project's macro that caused that.

Cannot Reproduce

Marking this as cannot reproduce for now, please comment again whenever you isolate it in a small project!