Content Migration

You can upgrade content of your project to UNIGINE 2.13 in the automatic or manual mode.

Automatic upgrade of the project's content can be performed via UNIGINE SDK Browser.

As a result, the binary executable and configuration files, meshes, terrains, worlds, nodes, splines, materials, properties, tracks, settings files will be upgraded to new formats (if any). The <unigine_project>/migration.log.html log file will be opened in the web browser. However, you can uncheck Migrate Content during automatic upgrading and perform content upgrading manually. In this case, only binary executable files will be upgraded.

This mode should be used to upgrade content stored outside the project's data folder (such as mount points):

To upgrade the project's content in the manual mode, do the following:

1. Put the binary executable <UnigineSDK>/bin/usc_x64.exe to the <UnigineSDK>/utils/upgrade folder that contains the upgrade script.
   Notice

   Use usc_x64.exe from the SDK version you are migrating to.
2. In the command prompt, run the upgrade.usc with the required options:
   Shell commands

   usc_x64.exe upgrade.usc path/to/additional_content_1 path/to/additional_content_2 ...

   If you have unchecked Migrate Content during automatic upgrading, add the path to the project's data folder to the list of arguments passed to the upgrade script. For example:
   Shell commands

   usc_x64.exe upgrade.usc <unigine_project>/data path/to/additional_content_1 path/to/additional_content_2 ...

   Here:
   • path/to/additional_content_* - paths to folders with content stored outside the data folder.

As soon as migration is completed, run the Editor to have the project assets "indexed".

The basemat file format no longer contains information about the material’s version. If you have got custom base materials in your project, delete the version attribute from the base_material tag in the files to avoid console warnings.

Before:

<base_material version="2.10.0.0"  name="custom_base" parameters_prefix="m" editable="0">
...
<base_material>

Now:

<base_material name="custom_base" parameters_prefix="m" editable="0">
...
<base_material>