When upgrading SAM to version 2.0.0, a small additional step is needed to avoid/remove errors. This step is required because the Core.dll and EditorCore.dll files were renamed, which was done to reduce the chance of conflict with your own or other 3rd party asset file names (since these names are quite common). This step is usually best performed before upgrading SAM, however if you've already upgraded, don't worry! You can get rid of these errors very easily.
1) To get started, simply delete the Deep Space Labs/Core folder in its entirety. Do not remove this folder from your Trash or Recycle Bin (on your OS) just yet, as you'll want to confirm the upgrade process went smoothly first.
2) Re-import the SAM package via the Package Manager. This will re-import the Core folder with the new file names.
3) Try to clear the console log of errors. If you continue to see errors, it is most likely because you have Terra Slicer (our other Asset) installed. In that case, you will need to download and import Terra Slicer v2.0.0 using the Package Manager, as it also uses the Core files. After performing this step, clear your console log again. If you continue to see errors, try restarting Unity, then contact us via email or discord if the errors continue.
4) If your project is error free, we now want to ensure that there were no issues with the upgrade. To do this, find a Naming Convention asset in your project, if one exists, and confirm that it's settings are correct (and shown in the inspector). If they are, then the upgrade was successful and you can remove the old Core folder (and its files) from your Trash or Recycle bin. No other steps are necessary.
If your project does not use any Naming Convention assets, then you are also in the clear and should have no trouble continuing to use SAM. Congrats! You can skip steps 5 - 8 below.
5) If your project uses Naming Convention assets and you notice that their settings are no longer configured correctly, or if the inspector is telling you that the file is missing its script, do not fear! This is caused by Unity re-assigning the new Core files a different GUID than the one we have assigned them, which usually happens when your project contained a file with the same GUIDs when you first imported SAM. To fix this, locate the Core.dll.meta and EditorCore.dll.meta files in your Trash or Recycle bin, and open them via a text editor or IDE. Copy and paste each file's GUID somewhere, as you'll need it for the next steps.
6) Locate the DeepSpaceLabs.Core.dll file in your project and right click it. Use Show In Explore or Reveal In Finder (or your OS's equivalent command) to view the actual file on your hard drive. Open the DeepSpaceLabs.Core.meta file in a text editor/IDE, and then copy/paste the GUID from step 5's Core.dll.meta file into the GUID field of the DeepSpaceLabs.Core.meta file. Save the file and close the file.
7) Navigate back to your File Explorer/Finder window and enter the Editor folder. Follow the same procedure as before, but this time using the DeepSpaceLabs.EditorCore.dll.meta file (as well as the EditorCore.dll.meta file's GUID). Save the file after replacing the GUID.
8) After this, the Naming Convention asset should be restored, which you can confirm by selecting it and viewing it's inspector. You can also check any assets that have the Naming Convention asset assigned to them to make sure the reference is still valid. If something is still not working right, unfortunately you will need to recreate the Naming Convention asset(s) and re-assign them to the appropriate fields, using the Asset Creation menu (Assets -> Deep Space Labs -> Core -> Naming Convention (v2)), or by right clicking the folder where you want to create the asset(s) and choosing Create -> Deep Space Labs -> Core -> Naming Convention (v2).
If you are still seeing errors, then you are one of the advanced users using SAM's API! Amazing!
Unfortunately, a lot of the API has been changed with v2. We will be compiling a full list of these changes soon, but for now, if you are unable to locate replacements for the API members you are trying to access on the API Website, please don't hesitate to reach out to us via one of the methods listed on our Contact page (though we recommend our Discord Server above all else).