Version Control and Dialogue Database

[3Gregg]

Hi,

My team is running into an issue with our Dialogue Database and version control where when we swap between branches, the dialogue database doesn't update. We will make a change on one branch (e.g. add a conversation) and then when we swap to a branch without it, it will stay there. The opposite also happens, where we won't have new conversations that we need.

Any idea what is going on here? We've lost some of our conversations due to this.

Thanks!

[Tony Li]

Hi,

Is the Dialogue Editor window open when you switch branches? It caches content in memory to speed up editor performance. If you change out the underlying asset while the window is open, it can cause a discrepancy between what's on disk and what's in memory. If that's what's happening, the solution is to close the window and select File > Save Project (just to be safe) before committing or pulling.

[3Gregg]

Ahhh I see that'd do it. Ok we'll add that to our best practices.

Thanks again Tony! You have a crazy fast response time

[Tony Li]

Glad to help!