Terragen Import-Export Reference - Revision history

Matt at 01:52, 22 January 2020

2020-01-22T01:52:23Z

Matt at 01:41, 22 January 2020

2020-01-22T01:41:24Z

Matt at 01:37, 22 January 2020

2020-01-22T01:37:03Z

Matt at 01:34, 22 January 2020

2020-01-22T01:34:24Z

Matt at 01:31, 22 January 2020

2020-01-22T01:31:14Z

Matt: Editing the Import section

2020-01-22T01:30:18Z

Editing the Import section

Matt: A bit of a rewrite of the Export section

2020-01-22T01:25:06Z

A bit of a rewrite of the Export section

Matt: Formatting

2020-01-22T01:05:49Z

Formatting

JavaJones at 03:49, 13 November 2018

2018-11-13T03:49:39Z

Matt: VDB export

2018-11-13T01:40:41Z

VDB export

← Older revision		Revision as of 01:52, 22 January 2020
Line 20:		Line 20:

	=== Import ===		=== Import ===
		+
		+	===== Cameras, Lights and Markers =====

	[[FBX Reference]]<br />		[[FBX Reference]]<br />

@@ Line 54: / Line 54: @@
 ===== Terrain Geometry =====
-Export FBX, OBJ, LWO and TGO via [[Micro Exporter]]. See the [[Micro Exporter]] node page for information on using the Micro exporter node to export terrain geometry. The Micro exporter is able to export geometry for procedural terrains including displacement and overhangs, which is not possible when exporting terrain as a heightfield.
+Export FBX, OBJ, LWO and TGO via [[Micro Exporter]].
 ===== Heightfields =====

@@ Line 47: / Line 47: @@
 === Export ===
-===== Cameras and Lights =====
+===== Cameras, Lights and Markers =====
 [[FBX Reference]]<br />

@@ Line 39: / Line 39: @@
 ===== Heightfields =====
-[[Terragen .TER Format]]
+[[Terragen .TER Format]] via [[Heightfield Load]].
 Many DEM formats via [[Geog Heightfield Load]].
-Most of the [[Supported Image Formats]] can be also read as heightfields.
+Most of the [[Supported Image Formats]] can be also read as heightfields by [[Heightfield Load]].
 === Export ===

@@ Line 41: / Line 41: @@
 [[Terragen .TER Format]]
-Many DEM formats via the [[Geog Heightfield Load]].
+Many DEM formats via [[Geog Heightfield Load]].
 Most of the [[Supported Image Formats]] can be also read as heightfields.

@@ Line 27: / Line 27: @@
 This describes how Terragen can import animation data from .chan and .mov files.
-===== Image Files =====
+===== Images/Textures =====
 This [[Supported Image Formats|page]] lists the image formats Terragen can open.
-===== Object Files =====
+===== Objects =====
 [[Wavefront OBJ Import]]
@@ Line 36: / Line 37: @@
 [[Terragen TGO Format]]
-===== Terrain Formats =====
+===== Heightfields =====
 [[Terragen .TER Format]]
 === Export ===
@@ Line 51: / Line 56: @@
 Export FBX, OBJ, LWO and TGO via [[Micro Exporter]]. See the [[Micro Exporter]] node page for information on using the Micro exporter node to export terrain geometry. The Micro exporter is able to export geometry for procedural terrains including displacement and overhangs, which is not possible when exporting terrain as a heightfield.
-===== Heightfield =====
+===== Heightfields =====
 Export [[Terragen .TER Format]].

@@ Line 3: / Line 3: @@
 This reference describes Terragen's import and export capabilities. This introduction gives a quick overview of what can be imported and exported from Terragen. For more information please refer to the '''Import''' and '''Export''' sections below.
-TG can import and export FBX files. Currently TG can import and export cameras, lights and markers, including animation. It can also export terrain geometry via the [[Micro Exporter]]. Please see the [[FBX Reference]] for more information about FBX import/export.
+Terragen can import and export FBX files. Currently Terragen can import and export cameras, lights and markers, including animation. It can also export terrain geometry via the [[Micro Exporter]]. Please see the [[FBX Reference]] for more information about FBX import/export.
-TG can import and export several object formats. It can import and export Wavefront OBJ and Lightwave LWO2 formats. You can also export objects to the native TGO object format, as well as open them of course.
+Terragen can import and export several object formats. It can import and export Wavefront OBJ and Lightwave LWO2 formats. You can also export objects to the native TGO object format, as well as open them of course.
 You can export terrain geometry using a [[Micro Exporter]] node. A Micro exporter can be connected to a [[Render]] node and it then exports all rendered terrain geometry. You can export terrain geometry to FBX, OBJ, LWO2 and TGO formats.
@@ Line 13: / Line 13: @@
 Animation data can be imported from .chan/.mov and FBX files. You can also export camera data to .chan and FBX formats.
-TG supports importing and exporting heightfields in a number of heightfield/DEM formats, including many image formats. It can load georeferencing data from GeoTIFFs.
+Terragen supports importing and exporting heightfields in a number of heightfield/DEM formats, including many image formats. It can load georeferencing data from GeoTIFFs.
-TG can read and write many image formats at various bit depths.
+Terragen can read and write many image formats at various bit depths.
-You can't export an entire TG scene and have it open intact in another application. For example it would not be possible to export TG shaders etc. and have them work in other applications. Generally speaking the idea is that you can export enough from TG that you can set up scenes and animation in another application and then import relevant parts, such as camera motion, back into TG. You can then use TG to render the landscape/environment, for example, and composite elements rendered in other applications with output from TG. TG has already been used in this fashion in a number of complex and high profile projects and integrated into studio pipelines.
+You can't export an entire Terragen scene and have it open intact in another application. For example it would not be possible to export Terragen shaders etc. and have them work in other applications. Generally speaking the idea is that you can export enough from Terragen that you can set up scenes and animation in another application and then import relevant parts, such as camera motion, back into Terragen. You can then use Terragen to render the landscape/environment, for example, and composite elements rendered in other applications with output from Terragen. Terragen has already been used in this fashion in a number of complex and high profile projects and integrated into studio pipelines.
 === Import ===
 [[FBX Reference]]<br />
-This describes TG's import/export capabilities for FBX files.
+This describes Terragen's import/export capabilities for FBX files.
 [[Importing Animation Data from .chan/.mov Files]]<br />
-This describes how TG can import animation data from .chan and .mov files.
+This describes how Terragen can import animation data from .chan and .mov files.
 ==== Image Files ====
-This [[Supported Image Formats|page]] lists the image formats TG3 can open.
+This [[Supported Image Formats|page]] lists the image formats Terragen can open.
 ==== Object Files ====
@@ Line 43: / Line 43: @@
 [[FBX Reference]]<br />
-This describes TG's import/export capabilities for FBX files.
+This describes Terragen's import/export capabilities for FBX files.
 '''Terrain Geometry'''<br />