Hello,
In ConversationView, the StopResponseMenuSequence method calls m_sequencer.Stop(); followed by m_sequencer.StopAllCoroutines();. This stops the DestroyAfterOneFrame coroutine in the Sequencer, preventing SequencerCommand from being destroyed.
Would calling m_sequencer.StopAllCoroutines(); before m_sequencer.Stop(); directly fix this issue?
StopResponseMenuSequence Method Issue
Re: StopResponseMenuSequence Method Issue
Yes, you're correct. I've switched the order for version 2.2.48.