Pixel Crushers Forum

Hi Tony,

I sincerely hope I don't bother you with these kinds of posts already.

I updated to the version 2.x.
First, thanks for the upgrader tool – it worked perfectly and not one thing in my project broke.
I don't know if there are suddenly many more features or whether they are now just easier to discover; either way, it seems very promising! Great job!

As for the possible problems I encountered (besides those I mentioned the last time),

Articy Lua Functions

There's one script the Upgrader didn't fix.



It used to be Articy Lua Functions, to support getProp() and setProp().
Is the script still required to support those functions? If it is, then I'm afraid I can't find it in 2.0 components and the path the documentation refers to the 1.x version.

Articy Reconvert

The articy:draft importer via Tools/ … / Importer / articy:draft works fine, but the Reconvert option on the database ends with these errors (that's all there is in the stack trace):



The database still gets imported fine, but the converter window crashes and closes itself.

Stage directions

Sequence commands inside stage directions sometimes don't get imported.



Probably applies to only some specific sequence commands. Fade(in) got imported fine, but AnimatorBool(bool) did not.
Although if it's written inside the Sequence text property, it gets imported fine.

Random function

The random function currently doesn't seem to be supported:



Would you please consider adding support for it, since it seems to be a matter of swapping "random(1,3)" with Lua's "math.random(1,3)"?

Variables

http://pixelcrushers.com/dialogue_system/manual2x/html/articy_draft.html#articyVariables wrote:At runtime, the Dialogue System will create the variables are listed in Special Variables if they don't exist. You can define them ahead of time in articy so you can use them in your content and test them in articy's presentation mode.ntation mode.

The documentation suggests creating variables like Actor or Conversant ahead.

As far as I know, this isn't possible in articy:draft, since the variables must always be a part of a set which DS imports as "VariableSet.VariableName" – so you (again, as far as I know) can't create a "dotless" variable.

Thank you for your time!

---

As a side note, is there a simpler way to search through the DS documentation rather than using the search bar? It feels a bit inconvenient since all the technical files are mixed together with the written pages, so when I look for something and the search results look like this:

Picture

I'm usually much better off just searching for one of your older answers on the forums, or reading a few relevant chapters top to bottom.

An even when I'm actually interested in the autogenerated page, it's not always very informative…

Hi,

Thanks again for all the details. Not all of your suggestions from last week are in 2.0.0, but I'm aiming to get them into 2.0.1, along with the suggestions and bug fixes for the issues you mentioned above. I wish I could have got them into 2.0.0, but at some point I had to release. I'm prioritizing articy updates in the next release.

I will try to have fixes for these bugs by the end of tomorrow:

• Updater tool not updating Articy Lua Functions.
• Sequencer commands inside stage directions sometimes not imported.
• (If time allows:) Converting the random function.

Regarding the online documentation, I'll see if I can build in an option to only return hits that start with "Page". In the meantime, if you do a browser text search for "Page" in the search results, it'll usually jump you to more relevant content. I realize it's not ideal, but it may help in the short term.

Hi,

I'm having trouble reproducing the stage directions issue. Would it be possible for you to send an articy XML file with the issue to tony (at) pixelcrushers.com please?

Hi,

all right, no problem.