Seeking Beta Testers for Version 2.0
Re: Seeking Beta Testers for Version 2.0
Thanks, @TowerCrow! Check your PMs on Friday for a beta download link.
Re: Seeking Beta Testers for Version 2.0
How is it going with that beta version test release?
Re: Seeking Beta Testers for Version 2.0
Coming today!
Re: Seeking Beta Testers for Version 2.0
Beta version 2.0b2 is now available on the beta download link. It fixes two issues:
- Standard UI Quest Log Window incorrectly showed abandon button for completed quests.
- Dialogue Editor window's Quests/Items list "+" button always added item without option to add quest.
Re: Seeking Beta Testers for Version 2.0
Beta testers:
@nathanj just found a serious issue in beta versions 2.0b1 and 2.0b2. The 1x To 2x Updater detects if your project's serialization mode is Mixed or Force Binary. If so, it temporarily changes it to Force Text so it can update them. If the updater isn't able to switch a dialogue database asset to Force Text for some reason, it will corrupt the database. To determine if your database is corrupt, close the Dialogue Editor window and inspect the database. If fields such as Version, Author, and Description show up in the Inspector as a strange string of numbers & letters instead of readable text, then it's corrupt.
The current workaround is to manually use menu item Edit > Project Settings > Editor -> Asset Serialization > Mode > Force Text before running the updater.
Later today, I'll have an update on the beta page that fixes this issue.
@nathanj just found a serious issue in beta versions 2.0b1 and 2.0b2. The 1x To 2x Updater detects if your project's serialization mode is Mixed or Force Binary. If so, it temporarily changes it to Force Text so it can update them. If the updater isn't able to switch a dialogue database asset to Force Text for some reason, it will corrupt the database. To determine if your database is corrupt, close the Dialogue Editor window and inspect the database. If fields such as Version, Author, and Description show up in the Inspector as a strange string of numbers & letters instead of readable text, then it's corrupt.
The current workaround is to manually use menu item Edit > Project Settings > Editor -> Asset Serialization > Mode > Force Text before running the updater.
Later today, I'll have an update on the beta page that fixes this issue.
Re: Seeking Beta Testers for Version 2.0
After further research, this is an old bug in Unity that has nothing in particular to do with the Dialogue System, but it's something I'll include in a "more info" button on the upgrader tool. Assets created in Unity 4 with binary serialization and then imported into Unity 5+ can't be changed to text serialization. This is because Unity 5 can't read Unity 4's binary serialization format. (Unity 4 uses 32-bit values, Unity 5 uses 64-bit)
The workaround is to switch the asset to text serialization in Unity 4, then open it in Unity 5+. A few of the Dialogue System's older third party support packages were exported from Unity 4 in binary serialization mode. For version 2.0, I've been updating these packages so they'll import properly.
The workaround is to switch the asset to text serialization in Unity 4, then open it in Unity 5+. A few of the Dialogue System's older third party support packages were exported from Unity 4 in binary serialization mode. For version 2.0, I've been updating these packages so they'll import properly.