Pixel Crushers Forum

I have one more issue with the new converter/update. We ordered the dialog options by positioning them in Articy from top to bottom. We're using Jumps, Hubs and Dialog fragments in Articy. That worked perfectly until the update. Now the dialog options are not in the Articy order anymore but somehow ...

Hi Tony,

thanks for your response. I will check that.

Marcus

Dear Tony, first, thanks for DialogueSystem. We're using it in our game Unforeseen Incidents and it saves us a lot of work and troubles. We're using Articy Draft to write the dialogue. Since we have a complex text-heavy game and are working with professional voice actors, we have our own workflow to...

Thank you!

Since we're working with Articy Draft and have a big project it's not so easy to always see when one would need to prevent the system from copying the values back to DS. We now solved it this way: The DialogueManager with the ACBridge has an additional script that ensures scripts from dialogue lines...

Hi Tony, thanks for your response. Our problem is indeed that a) changes to variables directly after cutscenes are not possible and need to happen one line later Line A Line B calls AnyCutscene Line C changes variable Line D does not work, whereas Line A Line B calls AnyCutscene Line C Line D change...

Weirdly, it works if we put the Script in one line later:

Player: "Line A"
Player: "Line B"
Player: "" / Sequence: AC(TheCutscene)
Player: "Line C"
NPC: "Line D" / Script: Variable["VariableName"] = true;
Player: "Line E"

Hi, I have a problem with Dialogue System and Adventure Creator. I'm changing a variable within a dialogue. Usually, that works. When the dialogue ends, the Adventure Creator variables get updated, everything's set up properly, However, when I call a cutscene in the dialogue that changes the variabl...

Thank you!! I'll probably go with having multiple variables since my approach to wiring up the dialog fragments got a little more complicated than I described it before. At least the usage of multiple variable sets (one for each dialog) comes in handy. The big advantage is that now, I can use the Ar...

I was already considering adding a boolean field to my articy:draft dialog template, something like a "displayOnlyOneTime" checkbox and then rewriting the XML parser so that it includes a LUA command like the one mentioned above for each dialog entry that has this box checked. BUT I need t...