Pixel Crushers Forum

Hello Guys,

i have an issue, that i cannot find a solution for. neither on the forum nor the rest of the internet.

-> im using the newest version of Dialogue System (1.6.5.1)

i'll explain it real quick, my company is developing an adventure game, by using adventure creator (http://www.adventurecreator.org/) together
with the Dialogue System.

Our writer is using ChatMapper to write the Dialogue and it's exported as an .xml file for me to import into unity (or essentially the Dialogue System).

Here comes the Problem, we are using a specific number of sequencer commands, to achieve audio playback as well as animation:

AnimatorPlay(Talk_D, SpriteChild_actorName);
AudioWait("pathToFolder\conversationID_dialogueID)->Message(Talked);
AnimatorPlay(Idle_D, SpriteChild_actorName)@Message(Talked);

Which works completely fine if i enter it as sequencer commands in the dialogue systems own dialogue editor, within unity :



Now our Writer added these Sequencer commands to our Dialogue entrys, within Chatmapper and exported them as an .xml file,
at this point the Sequencer Commands are still correct:



But what is really weird is, that if i import it into unity via the Chatmapper-Converter (from the Dialogue System), the Database
suddenly gets an additional sequencer command (the AudioWait() at the beginning), which of course causes the Dialogue to not work correctly:



I really hope it is just a setting thing, but to be honest i cannot find anything about it :/

thanks for reading and excuse my english i'm just a german student

Hi,

I can offer two solutions. First, this is the issue:

In Chat Mapper, your writer has added audio files to the dialogue entries' Audio Files lists. This allows the writer to play the conversation in Chat Mapper's Simulator and hear the audio.

However, the Dialogue System's Chat Mapper Converter automatically adds "AudioWait()" commands for every file in the Audio Files list. This causes duplicate AudioWait() commands because your writer has already added the same commands manually.

Solution 1: Remove the audio files from the dialogue entries' Audio Files lists.

• Pro: This should immediately fix the conversion issue.
• Con: Your writer won't be able to hear the audio files in Chat Mapper's Simulator.

Solution 2: I'll update the Chat Mapper Converter so it won't add duplicate AudioWait() commands if a corresponding AudioWait() command is already in the Sequence.

• Pro: Your writer will still be able to hear audio files in Chat Mapper's Simulator, and your writer will not have to make changes to the Chat Mapper project.
• Con: Will require a patch. If you want to use this solution, please let me know; in this case, I'll try to make the patch available today.

Hey, thank you for this fast solution!
But we had to remove the audiowaits manually, because the prototype had to be finished.

But if yo still offer the solution of a patch which does not add duplicate audiowaits that would be awesome for
future work!

It's already implemented, and it'll be in a patch coming out in the next day or two.