Saving database externally
Posted: Wed Nov 23, 2016 5:55 am
As you may remember we wanted to change the database at runtime and got the excellent importing function.
Now the database has grown considerably and the time to import the Articy XML is becoming an issue for writers on their laptops. It is a great benefit for them to change things without running Unity and messing with the source control so I'd like to keep the feature.
While I can disable the importing for the testers who have older .xml files than in project, I would like to cache the resulting database so that it will be read from the disk only once.
Do you have an idea if this can be done without an external program while running the build? So I import the xml, get the db and then save the .asset to some player specific directory for future use?
Now the database has grown considerably and the time to import the Articy XML is becoming an issue for writers on their laptops. It is a great benefit for them to change things without running Unity and messing with the source control so I'd like to keep the feature.
While I can disable the importing for the testers who have older .xml files than in project, I would like to cache the resulting database so that it will be read from the disk only once.
Do you have an idea if this can be done without an external program while running the build? So I import the xml, get the db and then save the .asset to some player specific directory for future use?