Pixel Crushers Forum

Hi, I noticed a strange issue and spent some time investigating, but I've hit a wall.

So I export my db in csv format. Then I import that csv as a new db. Then, in my scene I simply swap the old db for the new one in my DialogueSystemController object. But all of the sudden, I saw weird camera issues. Switched back to old db and the issues are gone.

I traced it back to this: in the original db, the default sequence is different, because the DisplaySettings.conversationOverrideSettings.useOverrides is true. But with the new db useOverrides is false. I don't know where this could be changed, as conversationOverrideSettings is hidden in the inspector and seems mostly internal.

Why is this happening? It doesn't seem to be something actually saved in the db export, so I'm not sure what I can do to get proper round-trip functionality between the db and csv files.

You're correct; that info isn't currently retained in the CSV export. I'll add it.

What are you using the CSV export for? I may be able to suggest alternatives for specific use cases such as localization.

Mostly as an interchange format so we can have large numbers of conversations sketched out, give them to a writer, and they can fill in the blanks, so to speak. We want a format that we can easily give to a writer without requiring them to install unity or other tools.

CSV isn't a great tool for writing conversations. But in version 2.2.21 I'll make sure CSV exports/imports the override info.

If your writer will need to generate a lot of content, maybe ask what they'd prefer to write it in. They might prefer the JLC text format or a tool such as Chat Mapper, articy:draft, or Twine. If they're coming from a screenwriting background, DS version 2.2.20 just introduced Celtx import.