When in version 3.x, you can check at anytime to make sure you are on the latest version of the asset by pressing the check for updates button in the settings provider for the asset. If you have the check for updates on load enabled in the settings which will auto-run this check when you load the project up and only display a message if the asset has an update available. This system checks the GitHub page for updates, stores such as the Unity Asset Store can be delayed by 1-3 business days or longer due to their review process.
You’ll first need to add the asset to your account to access it. If you’ve already done this the “Add to My Assets” button will display something like “Open In Unity”.
Then, in Unity. Access the “Package Manager” via the “Window” tab in the navbar. From there switch to the “My Assets” view for the packages dropdown. From there you’ll be able to select the Audio Manager and download/import the latest version. Then all you need to do is import all the files in the package and you’ll be good to go.
Sometimes updates don’t import correctly due to script changes that Unity’s package system doesn’t detect, like old scripts that need to be removed. If you encounter issues from an update, try a clean install of the asset with no asset files imported and that should fix any issues caused. I’ll try to do the clean up for the asset in editor scripts, but there is no guarantee that it’ll work al the time.
For GitHub you’ll need to navigate to the latest release and download the package provided in the assets for the release. There will always be a .unitypackage file provided in each release. Then you just import that package into your project. You can also just download the source and copy/paste it into your project for a similar result.
Sometimes updates don’t import correctly due to script changes that Unity’s package system doesn’t detect, like old scripts that need to be removed. If you encounter issues from an update, try a clean install of the asset with no asset files imported and that should fix any issues caused. I’ll try to do the clean up for the asset in editor scripts, but there is no guarantee that it’ll work al the time.
For itchio, just download the asset .unitypackage and import it into your project.
Sometimes updates don’t import correctly due to script changes that Unity’s package system doesn’t detect, like old scripts that need to be removed. If you encounter issues from an update, try a clean install of the asset with no asset files imported and that should fix any issues caused. I’ll try to do the clean up for the asset in editor scripts, but there is no guarantee that it’ll work all the time.
When installing a new version over an existing install there is a chance some error occur from older code. Every effort will be made to mitigate issues between updates in the same major version with editor classes. If you are still getting errors related to the asset or it starts mis-behaving, a clean install may be needed. If there are still issues after a clean install then do get in touch with me ([email protected]) and I’ll take a look at the issues you are facing.
Its a good idea to make a new branch or a copy of the project before you make these changes just as a backup in-case stuff goes wrong unexpectedly.
To add to an existing install, just import the package to the project and that should be it once the script have re-compiled.
To do a clean install, remove all code for the asset (ideally without the project open to avoid compilation errors). Then either import the new version into a clean project and copy the files over to your project or import the package in the project directly. You may need to reset the per user settings as well if you get errors after that.