Content Migration

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

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

In the 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".

Legacy ObjectTerrain (which was considered as deprecated since 2.7) is finally removed with this release. The same is true for the WorldOccluderTerrain. After migration each of them shall be converted to a NodeDummy. After migration you'll be able to re-create your terrain as the Landscape Terrain object using the assets you had used for ObjectTerrain.

There were a number of changes introduced to the material file format. In case your project uses custom base and manual materials the following modifications are required.

Parameter definition has changed with the <parameter/> tag replaced by a set of type-specific tags to be used instead:

• <float/>
• <float2/>
• <float3/>
• <float4/>
• <int/>
• <int2/>
• <int3/>
• <int4/>
• <combiner/>

Both color and slider types were removed, now each of them can be used as a type alias to define a parameter of a certain type with the corresponding widget:

<parameter name="name" type="slider">1.0</parameter>

<slider name="name">1.0</slider>

The list of available type aliases includes the following:

• mask24 (type = int, widget = mask24)
• mask32 (type = int, widget = mask32)
• uv (type = float4, widget = uv)
• color(type = float4, widget = color)
• slider(type = float, widget = slider)

<parameter name="name" type="slider">1.0</float>

<slider name="name">1.0</slider>

Now all parameters can be controlled via expressions (UnigineScript), so a new expression argument was added replacing the expression type used before. All parameters having the deprecated expression type should be replaced with float4 type in combination with the expression argument as follows:

<float name="name" expression="1">time</float>

<parameter name="name" type="expression">
	vec4(time, 0,0,1)
</parameter>

<float4 name="name" expression="1">
	vec4(time, 0,0,1)
</float4>

The flags argument was removed, with the following new separate arguments added instead: min_expand, max_expand, expand.

<parameter name="name" type="slider" flags="max_expand">
	0.5
</parameter>

<slider name="name" max_expand="1">
	0.5
</slider>