Errors upgrading to 2020.3.19f and 2.2.20

Announcements, support questions, and discussion for the Dialogue System.
Post Reply
gblekkenhorst
Posts: 81
Joined: Wed Jun 24, 2020 5:06 pm

Errors upgrading to 2020.3.19f and 2.2.20

Post by gblekkenhorst »

My studio wants to update to Unity 2020.3.19f, and I thought I'd look into updating Dialogue System and Adventure creator at the same time, but it's throwing a lot of errors - it seems to be all over the plug in. I tried the 1 to 2 updater (I can't tell what version we were using before) and I tried deleting the plug in folder before reimporting again.

Image
User avatar
Tony Li
Posts: 21984
Joined: Thu Jul 18, 2013 1:27 pm

Re: Errors upgrading to 2020.3.19f and 2.2.20

Post by Tony Li »

Hi,

Did you back up your project before updating? If so, you can check these locations for the version number:
  • Assets / Dialogue System / _README.txt (for version 1.x)
  • Assets / Plugins / Pixel Crushers / Dialogue System / _README.txt (for version 2.x)
You only need to use the 1x to 2x Updater tool if you're updating from version 1.x.

As a first test, try importing DS version 2.2.20 into a new, empty Unity 2020.3.19 project. If it doesn't work, then you probably have a bad copy of the Dialogue System. Try downloading it again from the Asset Store. Note that the Package Manager window is broken in some versions of Unity (details) so you may need to delete the Dialogue System package from your local Asset Store cache directory first.

If it works in a new, empty project, delete these two folders from your main project:
  • Assets / Dialogue System
  • Assets / Plugins / Pixel Crushers
(I'm assuming you have a backup that was made before all of this, in case you need to check back on older files.) Then import the Dialogue System and any third party support packages you need to use, such as the Adventure Creator Support package.
gblekkenhorst
Posts: 81
Joined: Wed Jun 24, 2020 5:06 pm

Re: Errors upgrading to 2020.3.19f and 2.2.20

Post by gblekkenhorst »

By the way, this worked! I've run into an error but I'm not sure it's related to the upgrade, so I will make another post.
Post Reply