Pixel Crushers Forum

I'm working on localization support and trying to export our database into a sheet usable by a translator, but the CSV converter doesn't seem to work for me. This is what I tried:

- Export Database, CSV format, all boxes ticked (I've also tried exporting only conversations) -> test.csv
- Open CSV Converter, import from test.csv into a new "mergetest" db (default encoding, overwrite, sort by id)

In the new mergetest db all actors, quests and dialogue entries seem to have correct values from the original database and the dialogue entries are in identical places, but all links are broken and the entries are separated.

I tried the same export/import process on a new dummy database with a couple of simple conversations and it worked perfectly, so apparently the importer (or exporter?) doesn't like something in our real database. Any guesses or ideas on how to approach this?

edit: Forgot to say that we're using version 1.7.6. Also, the OutgoingLinks section in the exported csv seems to have valid data and I can't see any differences in the fields compared to the simple test case.

Hi,

In your real database, did anyone manually edit the IDs assigned to conversations or dialogue entry nodes?

Are there any errors or warnings in the Console window when you re-import using the CSV Converter window?

Would it be possible for you to send a copy of your dialogue database to tony (at) pixelcrushers.com?

If you have I2 Localization (which is in this week's Mega Sale, btw), the Dialogue System Extras page has an integration package that will also be in the upcoming version 1.7.7. Documentation will also be in the 1.7.7 release, but the integration window is pretty simple to use. (Window > Dialogue System > Third Party > I2 Localization) If you decide to look into it and have any questions, please let me know.

Problem solved - there was an empty conversation that only contained the start node and the ids in that conversation were invalid. I have no idea how that happened, but removing the conversation fixed it. And yes, there was an error message that I completely missed the first couple of times. Thanks for the tips.

Great! Glad you got it working. I'll add a check to the CSV Converter to make it clearer when it finds issues like this.