This page has been translated automatically.
视频教程
界面
要领
高级
实用建议
UnigineEditor
界面概述
资产工作流程
设置和首选项
项目开发
调整节点参数
Setting Up Materials
Setting Up Properties
照明
Landscape Tool
Sandworm
使用编辑器工具执行特定任务
Extending Editor Functionality
嵌入式节点类型
Nodes
Objects
Effects
Decals
Light Sources
Geodetics
World Objects
Sound Objects
Pathfinding Objects
Players
编程
基本原理
搭建开发环境
Usage Examples
UnigineScript
C++
C#
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine Tools
GUI
双精度坐标
应用程序接口
Containers
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Objects-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
IG Plugin
CIGIConnector Plugin
Rendering-Related Classes
注意! 这个版本的文档是过时的,因为它描述了一个较老的SDK版本!请切换到最新SDK版本的文档。
注意! 这个版本的文档描述了一个不再受支持的旧SDK版本!请升级到最新的SDK版本。

Exporting Nodes

Any part of the scene (both a single node or a group of nodes including all children) can be exported from UnigineEditor and saved to a .node, .mesh or .fbx file.

Exporting Nodes to a NodeReference#

Any node (or nodes) from the World Hierarchy can be exported to a node reference. Exporting a node to a node reference may be required, for example, if you want to implement instancing of nodes in your project.

To export a node to a .node file, right-click the target node in the World Hierarchy window and choose Create a NodeReference in the drop-down list.

Exporting Node to NodeReference

Another way to export a node (nodes) is to select it in any available way and choose Edit -> Convert To NodeReference in the Menu Bar. In both cases, the selected node will be converted to NodeReference, and the .node file named after the node will be created.

If you select several nodes, they will be exported to a single .node file as child nodes of the dummy node.

The exported node will be saved in local coordinates (relative to the zero of coordinates or to the parent node, if any).

Exporting Nodes to a Mesh#

Exporting nodes to a mesh may be required, for example, when you have several mesh-based nodes, and you want to get them as a single mesh.

Nodes of the following object-related types can be exported to the .mesh file:

To export a node to a .mesh file, right-click the target node in the World Hierarchy window and choose Export to -> UNIGINE Mesh file (.mesh) in the drop-down list.

Notice
The exported mesh will be saved in the world coordinates.

Exporting Node to Mesh

The exported mesh can be used, for example, to create a mesh-based node.

Exporting Nodes to FBX#

Exporting nodes to an .fbx file provides a wide range of use cases for artists: for example, after exporting the scene you can bake lightmaps with the 3rd-party tool (for example, V-Ray).

Nodes of the following types can be exported to the .fbx file:

Notice
If you export a node of any other type, an empty .fbx file will be created.

  • When exporting a static or dynamic mesh that has more than one surface with the same material, a separate mesh for each surface will be created and saved in the FBX container.
  • When exporting a node reference, the node stored by the reference (in the .node file) will be exported.

To export a node to an .fbx file, right-click the target node in the World Hierarchy window and choose Export to -> FBX in the drop-down list.

Exporting Node to FBX

You can export both a single node or nodes hierarchy tree branch. However, exporting to FBX is available only if one node in the hierarchy is selected. To export the hierarchy tree branch, select and export the parent node: the child nodes will be exported as well. If you need to export the whole scene or its part, the nodes should be added as children to a dummy or layer node in the hierarchy.

Notice
If you export the hierarchy tree branch, only nodes that are on the list of the supported types will be exported.

The exported node will be saved in local coordinates (relative to the zero of coordinates or to the parent node, if any).

Notice
  • When exporting a static or dynamic mesh that has more than one surface with the same material, transformation of each created mesh is saved in the parent coordinates. In this case, the parent of the meshes is the static/dynamic mesh that is exported.
  • When exporting a node reference, transformation of this node reference is saved rather than transformation of the node stored by the reference.
Last update: 2021-11-30
Build: ()