Page 1 of 1

SendMessage not working on Unity 2017.2.0f3

Posted: Fri Mar 30, 2018 11:45 pm
by nishant
Hi,
I had integrated your Dialogue System in my project few years back. Recently I upgraded my project to Unity 2017.2.0f3 and I guess it broke the dialogue system. Basically I have a dialogue with a sequence as follows.

'SendMessage(WakeUp,,GenericCharacter) ; AudioWait(Audio/Dialog/AI/Activating lumin therapy_01,DialogueAudioRegistrator);Delay(10.0)'

Audio is playing, but WakeUp method is not triggered. This used to work when I had implemented it.

Any idea what might have gone wrong ?

Thanks.

Re: SendMessage not working on Unity 2017.2.0f3

Posted: Sat Mar 31, 2018 8:51 am
by Tony Li
Hi,

Nothing has changed in the SendMessage() sequencer command. Are there any warnings in the Console window (or output log, if you're playing a build)? Maybe it's reporting that it can't find a GameObject named "GenericCharacter"? Or that the method signature for WakeUp has changed? For example, maybe WakeUp now requires a parameter.

Re: SendMessage not working on Unity 2017.2.0f3

Posted: Mon Apr 02, 2018 11:07 am
by nishant
Hi,
I double checked. Nothing has changed. The gameobject is present in the scene with same name. The script is present on that gameobject which has method 'WakeUp' with same method signature. I even tried to pass random text instead of gameobject's name hoping for error to pop-up but it didnt. It seems like SendMessage is not getting called.

Re: SendMessage not working on Unity 2017.2.0f3

Posted: Mon Apr 02, 2018 4:15 pm
by Tony Li
Please temporarily set the Dialogue Manager's Debug Level to Info. Then reproduce the problem. Look in the Console output for this line:

Code: Select all

Dialogue System: Sequencer.Play( SendMessage(WakeUp, , GenericCharacter)@0 )
Then look immediately after that line. The next line (or nearby) should be:

Code: Select all

Dialogue System: Sequencer: SendMessage(WakeUp, , GenericCharacter (UnityEngine.Transform), )
However, there may be a warning instead. If so, the warning should indicate the problem.

If that doesn't help, please feel free to send a reproduction project to tony (at) pixelcrushers.com. I'll be happy to take a look.