shown in other instead.
According to the standard workflow, content of the project is migrated to the newest version automatically via UNIGINE SDK Browser or manually using the upgrade script.
However, you can add non-migrated assets to the upgraded project via the UNIGINE Editor, as it allows upgrading assets to the current version of UNIGINE SDK. An outdated asset is upgraded in the following cases:
- When importing an asset via the Asset Browser.
- When importing a package with an asset.
- When copying an asset to the project's data folder. If the UNIGINE Editor is launched, the asset will be upgraded on the fly.
If the UNIGINE Editor is off, the asset will be upgraded on the next launch.
To toggle upgrading on and off and specify the migration folder, go to the Editor section of the Settings window:
The Migration Directory is a temporary folder for the outdated assets: they are copied into this folder and processed by the upgrade script. Then the upgraded assets replace the original ones.
Upgrading Mounted Assets#
The only way to upgrade the mounted assets (i.e. referenced by a mount point) via the UNIGINE Editor is to add the mount point to the project when the editor is off. In this case, the assets will be upgraded on the next launch. However, we recommend you to upgrade assets inside mount points manually by using the upgrade.usc script.