This page has been translated automatically.
Interface Overview
Settings and Preferences
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
Setting Up Development Environment
Usage Examples
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
Double Precision Coordinates
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
CIGI Client Plugin
Rendering-Related Classes
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

Copying Assets From Other Projects

If you want to copy a single asset that does not require any other files (e.g. texture or rendering settings) from another project, you can do it in any of the ways listed here.

Composite assets (e.g. a material requiring a texture, or a node that requires several materials linked to plenty of textures) should be migrated from one project to another carefully. To simplify migration of such assets between the projects it is recommended to keep all linked assets (e.g. a node with all meshes, materials and textures it requires) in the same folder. In this case you can simply copy such folder from the data folder of the source project to the data folder of the destination project.

Do not modify or delete *.meta metafiles because they are necessary for keeping links and dependencies between assets.

As you open the destination project in the UnigineEditor, all assets from the new folder will be imported automatically with all links and dependencies preserved and you'll be able to use them.

Last update: 2018-08-10
Build: ()