Articy Draft Localization Export

[Magnatales]

First of all, congrats on this amazing tool! But I have a question.

I tried the articy draft localization setup given in the tutorial given in the docs and everything went smoothly but the thing I'm worried about is if I'm exporting Articy Draft to Unity and then Articy Draft again with the Dialogue System for Unity importer, that basically means I have 2 databases, right? One imported with AD and the other imported with DSFU

Isn't that a problem? Or both databases are connected and it's in reality only one?

[Tony Li]

Hi,

Articy:draft has its own plugin for Unity. This plugin is not required for the Dialogue System.

The Dialogue System imports articy XML files directly and creates its own dialogue database asset. It doesn't use articy's Unity plugin at all. In fact, I recommend removing articy's Unity plugin if you don't need it, since it slows down the editor. If you do need articy's Unity plugin for reasons apart from the Dialogue System, that's fine. Just keep in mind that the articy Unity plugin will handle its own data entirely separately from the Dialogue System.

If the Dialogue System's articy importer is creating a new database every time you import, tick the Overwrite checkbox. This will make it update the existing dialogue database instead.

[Magnatales]

Thank you for your time!

[Tony Li]

My pleasure!