Planetside Wiki - Recent changes [en]

Tex Coords From XYZ

2012-05-16T09:36:56Z

← Older revision		Revision as of 09:36, 16 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_174_image_0.png\|~~485pxpx~~\|Tex Coords From XYZ]]	+	[[Image:drex_module_174_image_0.png\|center\|Tex Coords From XYZ]]

−	~~Generates~~ world space texture coordinates from the input ~~functions~~. ~~Does not~~ compute normals.	+	'''Node Description and Purpose:'''<br />
		+	The Tex coords from XYZ node generates world space texture coordinates from displaced points from the input shader. It doesn't compute normals.
		+
		+
		+	'''Node Type:''' Other Shader<br />

−	~~<!-- imported from file: module_174.html-->~~

	[[Category:Other Shader]]		[[Category:Other Shader]]

Importing Animation Data from .chan/.mov Files

2012-05-16T09:19:50Z

← Older revision		Revision as of 09:19, 16 May 2012
(2 intermediate revisions by one user not shown)
Line 12:		Line 12:

	There are several ways to import data from chan files.		There are several ways to import data from chan files.
−
−	~~<u>Object nodes</u><br />~~
−	Some object nodes have an '''Import chan file''' button. For example the TGO Reader node has an '''Import chan file''' button on its Transform tab. This button loads a chan file and uses the file data to animate the '''Translate''' and '''Rotate''' parameters. The first value read from each line is the frame number. The next 3 values used to set '''Translate''' and the next 3 are used to set '''Rotate'''. There must be 7 values per line.

	<u>Camera nodes</u><br />		<u>Camera nodes</u><br />
Line 63:		Line 60:

	For more information about importing chan files using the Camera node please read the [[Camera_-_Import_Tab\|Import tab documentation]].		For more information about importing chan files using the Camera node please read the [[Camera_-_Import_Tab\|Import tab documentation]].
		+
		+	<u>Other nodes</u><br />
		+	A number of nodes have an '''Import chan file''' button. For example the TGO Reader node has an '''Import chan file''' button on its Transform tab. This button loads a chan file and uses the file data to animate position and rotation parameters. Which parameters those are depends on the node. As an example with the TGO Reader the '''Translate''' parameter is animated but for the Lake node the '''Centre''' parameter is loaded. Some nodes might not have a rotation parameter to animate, and in that case only the position is animated.
		+
		+	The first value read from each line is the frame number. The next 3 values used to set position and the next 3 are used to set rotation. There must be 7 values per line.

	===Coordinate spaces===		===Coordinate spaces===

LWO Reader

2012-05-16T08:55:20Z

← Older revision		Revision as of 08:55, 16 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_8_image_0.png\|~~485pxpx~~\|LWO Reader]]	+	[[Image:drex_module_8_image_0.png\|center\|LWO Reader]]
		+
		+	'''Node Description and Purpose:'''<br />
		+	The LWO Reader node loads objects from LightWave LWO files.
		+
		+
		+	'''Node Type:''' Object<br />
		+
		+
		+	'''Settings:'''<br />
		+
		+	<ul>
		+	<li>
		+	'''Population mode:''' This popup has two options:
		+	<ul>
		+	<li>
		+	<u>Individual Object:</u> This is the default for objects created individually, not part of a population. If you choose this option for objects that are part of a population the population instances will still render but the object itself will also show up at its original position.
		+	</li><li>
		+	<u>Member of a Population:</u> This is the default for objects created as part of creating a population. It means the objects only render as part of a population. If you choose this option for an individual object it won't render.
		+	</li>
		+	</ul>
		+	If you create an object as part of a population and then decide to use it on its own you may need to change the popup to <u>Individual Object</u> to get it to render.
		+	</li><li>
		+	'''Preview mode:''' This popup lets you choose how the object should be displayed in the 3D Preview. This popup sets the most detailed mode that the object can be displayed in. The Object Display Mode button in the 3D Preview controls the mode for the preview as a whole. For example if you set the '''Preview mode''' of the object to Wireframe but the 3D Preview object display mode is set to '''Show as bounding boxes''' then the object will only be drawn as a bounding box.
		+	</li><li>
		+	'''Visible to camera:''' If this is checked the object is visible to cameras such as the render camera. In other words it will show up in renders. If this is unchecked the object won't show up in renders. However if, for example, the '''Cast shadows''' checkbox is checked then the shadows cast by the object will still be visible.
		+	</li><li>
		+	'''Visible to other rays:''' When this is checked the object is visible to various rays which are traced during rendering, such as reflection, transparency and GI rays. As an example, if this was unchecked the object would not show up in reflections.
		+	</li><li>
		+	'''Cast shadows:''' This should be checked if you want the object to cast shadows.
		+	</li><li>
		+	'''Double-sided surface:''' If this is checked object surfaces are double sided. A single sided surface is only visible from the "front", which is the direction the surface normal is pointing. If you look at it from the other direction the surface isn't visible. Double sided surfaces are visible from all directions.
		+	</li><li>
		+	'''Use smooth normals:''' If this is checked the object normals are interpolated to make the surface appear smooth. If it's unchecked the surface will look faceted.
		+	</li><li>
		+	'''Flip normals:''' Check this to flip or reverse the object normals. You might want to use this on an imported object if it has gaps or strange dark patches when rendered.
		+	</li><li>
		+	'''Filename:''' This parameter shows the path to the file used by the object. You can use the file button at right to load a different file but this isn't recommended as the materials for the new file won't be loaded.
		+	</li>
		+	</ul>
		+
		+
		+	<u>Transform tab</u><br />
		+
		+	<ul>
		+	<li>
		+	'''Translate:''' This sets the position of the object.
		+	</li><li>
		+	'''Rotate:''' This rotates the object about its origin. The order of the values is heading, pitch then bank.
		+	</li><li>
		+	'''Scale:''' You can use this parameter to scale the object in the X, Y and Z directions.
		+	</li><li>
		+	'''Import chan file:''' Clicking this button allows you to import a .chan file for animating the object position and rotation.
		+	</li>
		+	</ul>
		+

	==Additional tabs for LWO Reader==		==Additional tabs for LWO Reader==
Line 7:		Line 62:
	* [[LWO Reader - Surface Shaders Tab]]		* [[LWO Reader - Surface Shaders Tab]]

−	~~<!-- imported from file: module_8.html-->~~

	[[Category: Object Nodes]]		[[Category: Object Nodes]]

LWO Reader - Angular Position Tab

2012-05-16T08:50:33Z

← Older revision		Revision as of 08:50, 16 May 2012
Line 20:		Line 20:
	Back to: [[LWO Reader]]		Back to: [[LWO Reader]]

−	[[Category: ~~LWO Reader\|~~ ]]	+	[[Category: Object Nodes]]

LWO Reader - Surface Shaders Tab

2012-05-16T08:49:29Z

← Older revision		Revision as of 08:49, 16 May 2012
Line 1:		Line 1:
	[[Image:drex_module_8_2_image_0.png\|465pxpx\|LWO Reader - Surface Shaders Tab]]		[[Image:drex_module_8_2_image_0.png\|465pxpx\|LWO Reader - Surface Shaders Tab]]

−	~~Back to~~: ~~[[LWO Reader]]~~	+	'''Description:'''<br />
		+	This tab lets you assign a surface shader to texture the object.

−	<~~!-- imported from file~~: ~~module_8_2~~.~~html--~~>	+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Surface shader:''' You can use this to assign a surface shader to the object.
		+	</li><li>
		+	'''Displacement tolerance:''' If you find that rough or spikey surfaces are showing problems at bucket edges, for example spikes having cut off tops, or gaps in ray traced shadows then increasing this value may help. However this can greatly increase render times. Relatively flat surfaces may render more quickly with smaller values.
		+
		+	The default value is 1. However this is an advanced setting and you should not change it unless you have specific problem you need to address. If you are having problems try starting with 2 and then increase it by small increments until they're resolved. A value of 4 would be considered a high value.
		+	</li>
		+	</ul>
		+
		+
		+	Back to: [[LWO Reader]]

−	[[Category: ~~LWO Reader\|~~ ]]	+	[[Category: Object Nodes]]

LWO Reader - Angular Position Tab

2012-05-16T08:48:39Z

← Older revision		Revision as of 08:48, 16 May 2012
Line 1:		Line 1:
−	[[Image:drex_module_8_1_image_0.png\|~~465pxpx~~\|LWO Reader - Angular Position Tab]]	+	[[Image:drex_module_8_1_image_0.png\|center\|LWO Reader - Angular Position Tab]]

−	~~Back to~~: [[~~LWO Reader~~]]	+	'''Description:'''<br />
		+	This tab has settings which use angles and distance to set the position of the object relative to the scene origin. These settings are an alternative to using the '''Translate''' setting in the Transform tab. The diagram below shows how all the parameters relate to each other and the origin.<br />
		+	<br />
		+	[[image:angular_position.gif\|center]]

−	<~~!-- imported from file~~: ~~module_8_1~~.~~html-~~->	+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Heading:''' This angle sets the rotation of the object around the scene origin, in the XY plane, increasing as you turn clockwise.
		+	</li><li>
		+	'''Elevation:''' This angle sets the vertical part of the position. You could think of it as the angle above or below the horizon. 90 is straight up, -90 is straight down.
		+	</li><li>
		+	'''Distance:''' This sets the distance from the origin, in metres.
		+	</li>
		+	</ul>
		+
		+
		+	Back to: [[LWO Reader]]

	[[Category: LWO Reader\| ]]		[[Category: LWO Reader\| ]]

OBJ Reader - Angular Position Tab

2012-05-16T08:46:43Z

← Older revision		Revision as of 08:46, 16 May 2012
Line 20:		Line 20:
	Back to: [[OBJ Reader]]		Back to: [[OBJ Reader]]

−	[[Category: ~~OBJ Reader\|~~ ]]	+	[[Category: Object Nodes]]

OBJ Reader - Surface Shaders Tab

2012-05-16T08:46:06Z

← Older revision		Revision as of 08:46, 16 May 2012
(One intermediate revision by one user not shown)
Line 2:		Line 2:

	'''Description:'''<br />		'''Description:'''<br />
−	This tab lets you assign a surface shader to texture the object. If there was a .mtl file associated with the OBJ file a [[Parts ~~shader~~ ]] with its associated nodes will be created and assigned to the '''Surface shader''' input.	+	This tab lets you assign a surface shader to texture the object. If there was a .mtl file associated with the OBJ file a [[Parts Shader]] with its associated nodes will be created and assigned to the '''Surface shader''' input.

	'''Settings:'''<br />		'''Settings:'''<br />
Line 8:		Line 8:
	<li>		<li>
	'''Surface shader:''' You can use this to assign a surface shader to the object.		'''Surface shader:''' You can use this to assign a surface shader to the object.
		+	</li><li>
		+	'''Displacement tolerance:''' If you find that rough or spikey surfaces are showing problems at bucket edges, for example spikes having cut off tops, or gaps in ray traced shadows then increasing this value may help. However this can greatly increase render times. Relatively flat surfaces may render more quickly with smaller values.
		+
		+	The default value is 1. However this is an advanced setting and you should not change it unless you have specific problem you need to address. If you are having problems try starting with 2 and then increase it by small increments until they're resolved. A value of 4 would be considered a high value.
	</li>		</li>
	</ul>		</ul>
Line 15:		Line 19:


−	[[Category: ~~OBJ Reader\|~~ ]]	+	[[Category: Object Nodes]]

TGO Reader - Surface Shaders Tab

2012-05-16T08:42:29Z

← Older revision		Revision as of 08:42, 16 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_196_2_image_0.png\|~~465pxpx~~\|TGO Reader - Surface Shaders Tab]]	+	[[Image:drex_module_196_2_image_0.png\|center\|TGO Reader - Surface Shaders Tab]]
		+
		+	'''Description:'''<br />
		+	This tab lets you assign a surface shader to texture the object. If the TGO file contains surface shaders these are assigned to the '''Surface shader''' parameter when the file is loaded.
		+
		+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Surface shader:''' You can use this to assign a surface shader to the object.
		+	</li><li>
		+	'''Displacement tolerance:''' If you find that rough or spikey surfaces are showing problems at bucket edges, for example spikes having cut off tops, or gaps in ray traced shadows then increasing this value may help. However this can greatly increase render times. Relatively flat surfaces may render more quickly with smaller values.
		+
		+	The default value is 1. However this is an advanced setting and you should not change it unless you have specific problem you need to address. If you are having problems try starting with 2 and then increase it by small increments until they're resolved. A value of 4 would be considered a high value.
		+	</li>
		+	</ul>
		+

	Back to: [[TGO Reader]]		Back to: [[TGO Reader]]

−	~~<!-- imported from file: module_196_2.html-->~~

−	[[Category: ~~TGO Reader\|~~ ]]	+	[[Category: Object Nodes ]]

TGO Reader - Angular Position Tab

2012-05-16T08:35:37Z

← Older revision		Revision as of 08:35, 16 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_196_1_image_0.png\|~~465pxpx~~\|TGO Reader - Angular Position Tab]]	+	[[Image:drex_module_196_1_image_0.png\|center\|TGO Reader - Angular Position Tab]]
		+
		+	'''Description:'''<br />
		+	This tab has settings which use angles and distance to set the position of the object relative to the scene origin. These settings are an alternative to using the '''Translate''' setting in the Transform tab. The diagram below shows how all the parameters relate to each other and the origin.<br />
		+	<br />
		+	[[image:angular_position.gif\|center]]
		+
		+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Heading:''' This angle sets the rotation of the object around the scene origin, in the XY plane, increasing as you turn clockwise.
		+	</li><li>
		+	'''Elevation:''' This angle sets the vertical part of the position. You could think of it as the angle above or below the horizon. 90 is straight up, -90 is straight down.
		+	</li><li>
		+	'''Distance:''' This sets the distance from the origin, in metres.
		+	</li>
		+	</ul>
		+

	Back to: [[TGO Reader]]		Back to: [[TGO Reader]]

−	~~<!-- imported from file: module_196_1.html-->~~

−	[[Category: ~~TGO Reader\|~~ ]]	+	[[Category: Object Nodes ]]

TGO Reader

2012-05-16T08:34:28Z

← Older revision		Revision as of 08:34, 16 May 2012
Line 1:		Line 1:
−	[[Image:drex_module_196_image_0.png\|~~485pxpx~~\|TGO Reader]]	+	[[Image:drex_module_196_image_0.png\|center\|TGO Reader]]
		+
		+	'''Node Description and Purpose:'''<br />
		+
		+	The TGO Reader loads an object from a TGO file. TGO is Terragen 2's native object format.
		+
		+
		+	'''Node Type:''' Object<br />
		+
		+
		+	'''Settings:'''<br />
		+
		+	<ul>
		+	<li>
		+	'''Population mode:''' This popup has two options:
		+	<ul>
		+	<li>
		+	<u>Individual Object:</u> This is the default for objects created individually, not part of a population. If you choose this option for objects that are part of a population the population instances will still render but the object itself will also show up at its original position.
		+	</li><li>
		+	<u>Member of a Population:</u> This is the default for objects created as part of creating a population. It means the objects only render as part of a population. If you choose this option for an individual object it won't render.
		+	</li>
		+	</ul>
		+	If you create an object as part of a population and then decide to use it on its own you may need to change the popup to <u>Individual Object</u> to get it to render.
		+	</li><li>
		+	'''Preview mode:''' This popup lets you choose how the object should be displayed in the 3D Preview. This popup sets the most detailed mode that the object can be displayed in. The Object Display Mode button in the 3D Preview controls the mode for the preview as a whole. For example if you set the '''Preview mode''' of the object to Wireframe but the 3D Preview object display mode is set to '''Show as bounding boxes''' then the object will only be drawn as a bounding box.
		+	</li><li>
		+	'''Visible to camera:''' If this is checked the object is visible to cameras such as the render camera. In other words it will show up in renders. If this is unchecked the object won't show up in renders. However if, for example, the '''Cast shadows''' checkbox is checked then the shadows cast by the object will still be visible.
		+	</li><li>
		+	'''Visible to other rays:''' When this is checked the object is visible to various rays which are traced during rendering, such as reflection, transparency and GI rays. As an example, if this was unchecked the object would not show up in reflections.
		+	</li><li>
		+	'''Cast shadows:''' This should be checked if you want the object to cast shadows.
		+	</li><li>
		+	'''Double-sided surface:''' If this is checked object surfaces are double sided. A single sided surface is only visible from the "front", which is the direction the surface normal is pointing. If you look at it from the other direction the surface isn't visible. Double sided surfaces are visible from all directions.
		+	</li><li>
		+	'''Use smooth normals:''' If this is checked the object normals are interpolated to make the surface appear smooth. If it's unchecked the surface will look faceted.
		+	</li><li>
		+	'''Flip normals:''' Check this to flip or reverse the object normals. You might want to use this on an imported object if it has gaps or strange dark patches when rendered.
		+	</li><li>
		+	'''Filename:''' This parameter shows the path to the file used by the object. You can use the file button at right to load a different file but this isn't recommended as the materials for the new file won't be loaded.
		+	</li>
		+	</ul>
		+
		+
		+	<u>Transform tab</u><br />
		+
		+	<ul>
		+	<li>
		+	'''Translate:''' This sets the position of the object.
		+	</li><li>
		+	'''Rotate:''' This rotates the object about its origin. The order of the values is heading, pitch then bank.
		+	</li><li>
		+	'''Scale:''' You can use this parameter to scale the object in the X, Y and Z directions.
		+	</li><li>
		+	'''Import chan file:''' Clicking this button allows you to import a .chan file for animating the object position and rotation.
		+	</li>
		+	</ul>

	==Additional tabs for TGO Reader==		==Additional tabs for TGO Reader==
Line 7:		Line 62:
	* [[TGO Reader - Surface Shaders Tab]]		* [[TGO Reader - Surface Shaders Tab]]

−	~~<!-- imported from file: module_196.html-->~~

	[[Category: Object Nodes]]		[[Category: Object Nodes]]

Importing Animation Data from .chan/.mov Files

2012-05-16T07:04:20Z

← Older revision		Revision as of 07:04, 16 May 2012
(2 intermediate revisions by one user not shown)
Line 1:		Line 1:
	Terragen 2 can import motion and camera data from .chan and .mov files. .chan files can be exported from Houdini and Nuke and Maya can export .mov files. There are also often plugins or scripts available for other applications which can export .chan files. "chan" will be used to refer to both .chan and .mov files in the rest of this document.		Terragen 2 can import motion and camera data from .chan and .mov files. .chan files can be exported from Houdini and Nuke and Maya can export .mov files. There are also often plugins or scripts available for other applications which can export .chan files. "chan" will be used to refer to both .chan and .mov files in the rest of this document.

−	chan files ~~are are a simple text format. Essentially they consist of multiple numeric values per line, with each value separated by a space. How~~ the ~~values are interpreted on import depends a bit on how the file is imported~~. chan ~~files are easy to generate if you want to create animation data from a script or spreadsheet or similar~~. ~~Please note that the data~~ is ~~expected to be in~~ the ~~Houdini coordinate system and is converted to the TG2 coordinate system on~~ import. ~~See below for~~ more information about that.	+	TG2's preferred format for chan files is the 8 channel Nuke .chan format. This is the format that works best with default import settings. For more information about that format please see the '''Writing chan files''' section below.

	===Importing from animation buttons===		===Importing from animation buttons===
Line 76:		Line 76:

	* Heading is anti-clockwise when viewed as a heading on a map, but it's actually clockwise when viewed along the the positive Y axis.		* Heading is anti-clockwise when viewed as a heading on a map, but it's actually clockwise when viewed along the the positive Y axis.
		+
		+	===Writing chan files===
		+
		+	chan files are are a simple text format. Essentially they consist of multiple numeric values per line, with each value separated by a space. How the values are interpreted on import depends a bit on how the file is imported. chan files are easy to generate if you want to create animation data from a script or spreadsheet or similar.
		+
		+	If you want to generate chan files for use with TG2 the preferred format is the 8 channel Nuke .chan variant. In this format there are 8 values per line, ordered like this:
		+
		+	<ol>
		+	<li>
		+	Frame number
		+	</li><li>
		+	X
		+	</li><li>
		+	Y
		+	</li><li>
		+	Z
		+	</li><li>
		+	Rotate X
		+	</li><li>
		+	Rotate Y
		+	</li><li>
		+	Rotate Z
		+	</li><li>
		+	Vertical field-of-view
		+	</li>
		+	</ol>
		+
		+	Each value is separated by a space.
		+
		+	Please note that the data is expected to be in the Houdini coordinate system and is converted to the TG2 coordinate system on import. See the '''Coordinate spaces''' section above for more information about that.
		+


	[[Terragen 2 Animation Module Reference\|Back to the Animation Module Reference]]		[[Terragen 2 Animation Module Reference\|Back to the Animation Module Reference]]

OBJ Reader - OBJ Options Tab

2012-05-16T06:30:05Z

← Older revision		Revision as of 06:30, 16 May 2012
(2 intermediate revisions by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_9_3_image_0.png\|~~465pxpx~~\|OBJ Reader - OBJ Options Tab]]	+	[[Image:drex_module_9_3_image_0.png\|center\|OBJ Reader - OBJ Options Tab]]

−	~~Back to~~: [[OBJ ~~Reader]]~~	+	'''Description:'''<br />
		+	This tab contains settings which are specific to loading OBJ files.

−	~~<!-- imported from file: module_9_3.html-->~~

−	[[~~Category~~: OBJ Reader\| ]]	+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Source in cm:''' If this is checked then TG2 interprets the measurement units in the OBJ file as being in centimetres. That's the theory, but there is currently a bug which means the units are interpreted as 10cm (decimetre) rather than 1cm. You may still need to scale the object using the [[OBJ_Reader\|Transform tab]] to make it the correct size.
		+	</li><li>
		+	'''Source Z up:''' Check this if you know the OBJ file uses Z up as opposed to Y up, which TG2 uses. This will cause the coordinates to be swapped when read from the file to match TG2's coordinate system. If the model seems to be laying over on its side when imported you probably need to check this setting.
		+	</li>
		+	</ul>
		+
		+
		+	Back to: [[OBJ Reader]]
		+
		+	[[Category: Object Nodes]]

OBJ Reader - Surface Shaders Tab

2012-05-16T06:19:54Z

← Older revision		Revision as of 06:19, 16 May 2012
Line 1:		Line 1:
−	[[Image:drex_module_9_2_image_0.png\|~~465pxpx~~\|OBJ Reader - Surface Shaders Tab]]	+	[[Image:drex_module_9_2_image_0.png\|center\|OBJ Reader - Surface Shaders Tab]]
		+
		+	'''Description:'''<br />
		+	This tab lets you assign a surface shader to texture the object. If there was a .mtl file associated with the OBJ file a [[Parts shader ]] with its associated nodes will be created and assigned to the '''Surface shader''' input.
		+
		+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Surface shader:''' You can use this to assign a surface shader to the object.
		+	</li>
		+	</ul>
		+

	Back to: [[OBJ Reader]]		Back to: [[OBJ Reader]]

−	~~<!-- imported from file: module_9_2.html-->~~

	[[Category: OBJ Reader\| ]]		[[Category: OBJ Reader\| ]]

OBJ Reader - Angular Position Tab

2012-05-16T06:12:55Z

← Older revision		Revision as of 06:12, 16 May 2012
Line 1:		Line 1:
−	[[Image:drex_module_9_1_image_0.png\|~~465pxpx~~\|OBJ Reader - Angular Position Tab]]	+	[[Image:drex_module_9_1_image_0.png\|center\|OBJ Reader - Angular Position Tab]]

−	~~Back to~~: [[~~OBJ Reader~~]]	+	'''Description:'''<br />
		+	This tab has settings which use angles and distance to set the position of the object relative to the scene origin. These settings are an alternative to using the '''Translate''' setting in the Transform tab. The diagram below shows how all the parameters relate to each other and the origin.<br />
		+	<br />
		+	[[image:angular_position.gif\|center]]

−	<~~!-- imported from file~~: ~~module_9_1~~.~~html-~~->	+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Heading:''' This angle sets the rotation of the object around the scene origin, in the XY plane, increasing as you turn clockwise.
		+	</li><li>
		+	'''Elevation:''' This angle sets the vertical part of the position. You could think of it as the angle above or below the horizon. 90 is straight up, -90 is straight down.
		+	</li><li>
		+	'''Distance:''' This sets the distance from the origin, in metres.
		+	</li>
		+	</ul>
		+
		+
		+	Back to: [[OBJ Reader]]

	[[Category: OBJ Reader\| ]]		[[Category: OBJ Reader\| ]]

OBJ Reader

2012-05-16T06:11:06Z

← Older revision		Revision as of 06:11, 16 May 2012
Line 1:		Line 1:
−	[[Image:drex_module_9_image_0.png\|~~485pxpx~~\|OBJ Reader]]	+	[[Image:drex_module_9_image_0.png\|center\|OBJ Reader]]
		+
		+	'''Node Description and Purpose:'''<br />
		+	The OBJ Reader node loads models from a Wavefront .OBJ file. The OBJ Reader can also load .mtl files specified by the OBJ containing texturing information. When you create an OBJ Reader it opens a file dialog allowing you to choose the file to load.
		+
		+
		+	'''Node Type:''' Object<br />
		+
		+
		+	'''Settings:'''<br />
		+
		+	<ul>
		+	<li>
		+	'''Population mode:''' This popup has two options:
		+	<ul>
		+	<li>
		+	<u>Individual Object:</u> This is the default for objects created individually, not part of a population. If you choose this option for objects that are part of a population the population instances will still render but the object itself will also show up at its original position.
		+	</li><li>
		+	<u>Member of a Population:</u> This is the default for objects created as part of creating a population. It means the objects only render as part of a population. If you choose this option for an individual object it won't render.
		+	</li>
		+	</ul>
		+	If you create an object as part of a population and then decide to use it on its own you may need to change the popup to <u>Individual Object</u> to get it to render.
		+	</li><li>
		+	'''Preview mode:''' This popup lets you choose how the object should be displayed in the 3D Preview. This popup sets the most detailed mode that the object can be displayed in. The Object Display Mode button in the 3D Preview controls the mode for the preview as a whole. For example if you set the '''Preview mode''' of the object to Wireframe but the 3D Preview object display mode is set to '''Show as bounding boxes''' then the object will only be drawn as a bounding box.
		+	</li><li>
		+	'''Visible to camera:''' If this is checked the object is visible to cameras such as the render camera. In other words it will show up in renders. If this is unchecked the object won't show up in renders. However if, for example, the '''Cast shadows''' checkbox is checked then the shadows cast by the object will still be visible.
		+	</li><li>
		+	'''Visible to other rays:''' When this is checked the object is visible to various rays which are traced during rendering, such as reflection, transparency and GI rays. As an example, if this was unchecked the object would not show up in reflections.
		+	</li><li>
		+	'''Cast shadows:''' This should be checked if you want the object to cast shadows.
		+	</li><li>
		+	'''Double-sided surface:''' If this is checked object surfaces are double sided. A single sided surface is only visible from the "front", which is the direction the surface normal is pointing. If you look at it from the other direction the surface isn't visible. Double sided surfaces are visible from all directions.
		+	</li><li>
		+	'''Use smooth normals:''' If this is checked the object normals are interpolated to make the surface appear smooth. If it's unchecked the surface will look faceted.
		+	</li><li>
		+	'''Flip normals:''' Check this to flip or reverse the object normals. You might want to use this on an imported object if it has gaps or strange dark patches when rendered.
		+	</li><li>
		+	'''Filename:''' This parameter shows the path to the file used by the OBJ Reader. You can use the file button at right to load a different file but this isn't recommended as the materials for the new file won't be loaded.
		+	</li>
		+	</ul>
		+
		+
		+	<u>Transform tab</u><br />
		+
		+	<ul>
		+	<li>
		+	'''Translate:''' This sets the position of the object.
		+	</li><li>
		+	'''Rotate:''' This rotates the object about its origin. The order of the values is heading, pitch then bank.
		+	</li><li>
		+	'''Scale:''' You can use this parameter to scale the object in the X, Y and Z directions.
		+	</li><li>
		+	'''Import chan file:''' Clicking this button allows you to import a .chan file for animating the object position and rotation.
		+	</li>
		+	</ul>
		+

	==Additional tabs for OBJ Reader==		==Additional tabs for OBJ Reader==
Line 9:		Line 64:
	* [[OBJ Reader - OBJ Options Tab]]		* [[OBJ Reader - OBJ Options Tab]]

−	~~<!-- imported from file: module_9.html-->~~

	[[Category: Object Nodes]]		[[Category: Object Nodes]]

Terragen 2 Animation Module Reference

2012-05-16T03:15:06Z

← Older revision		Revision as of 03:15, 16 May 2012
Line 16:		Line 16:

	[[Importing Animation Data from .chan/.mov Files]]<br />		[[Importing Animation Data from .chan/.mov Files]]<br />
−	This describes how TG2 ~~handles importing~~ animation data from .chan and .mov files.	+	This describes how TG2 can import animation data from .chan and .mov files.

Importing Animation Data from .chan/.mov Files

2012-05-16T03:06:40Z

Created page with "Terragen 2 can import motion and camera data from .chan and .mov files. .chan files can be exported from Houdini and Nuke and Maya can export .mov files. There are also often plu..."

New page

Terragen 2 can import motion and camera data from .chan and .mov files. .chan files can be exported from Houdini and Nuke and Maya can export .mov files. There are also often plugins or scripts available for other applications which can export .chan files. "chan" will be used to refer to both .chan and .mov files in the rest of this document.

chan files are are a simple text format. Essentially they consist of multiple numeric values per line, with each value separated by a space. How the values are interpreted on import depends a bit on how the file is imported. chan files are easy to generate if you want to create animation data from a script or spreadsheet or similar. Please note that the data is expected to be in the Houdini coordinate system and is converted to the TG2 coordinate system on import. See below for more information about that.

===Importing from animation buttons===

Before discussing chan files it's worth mentioning importing animation data from files using parameter animation buttons. Animation buttons have an '''Import animation file...''' item in their menu. This can be used to import animation data from simple text files similar to chan files but an important point is that the values read from the file should be in TG2 coordinate space and not Houdini coordinate space as for chan files.

The file format is similar though. From 2 to 4 values are read from each line of the file, depending on the parameter type. The first value should be the frame number. The values should be separated by spaces.

===Importing chan files===

There are several ways to import data from chan files.

Object nodes 
Some object nodes have an '''Import chan file''' button. For example the TGO Reader node has an '''Import chan file''' button on its Transform tab. This button loads a chan file and uses the file data to animate the '''Translate''' and '''Rotate''' parameters. The first value read from each line is the frame number. The next 3 values used to set '''Translate''' and the next 3 are used to set '''Rotate'''. There must be 7 values per line.

Camera nodes 
[[Camera]] nodes have the most configurable chan import options. The [[Camera_-_Import_Tab|Import tab]] allows you to import chan files and you can choose to import position and rotation data as well as camera view data.

The camera node has some rules about how it interprets chan files:

If the file has a .chan extension then
<ul>
<li>
the file should have 7, 8 or 10 values per line.
</li><li>
if the file has 7 values per line it is assumed to be a chan file without a frame number. In this case the number of the line in the file is used as the frame number. The first 6 values are position and rotation data. The 7th value is vertical field-of-view.
</li><li>
if the file has 8 values per line the first value is a frame number. The next 6 values are position and rotation data. The 8th value is vertical field-of-view.
</li><li>
if the file has 10 values per line the first value is a frame number. The next 6 values are position and rotation data. Value 8 is focal length, value 9 is aspect ratio and value 10 is horizontal aperture.
</li>
</ul>

If the file has a .mov extension then
<ul>
<li>
the file should have 6 or 7 values per line.
</li><li>
the number of the line in the file is used as the frame number.
</li><li>
the first 6 values are position and rotation data. If there are 7 values the 7th is vertical field-of-view.
</li>
</ul>

The Camera node has several options for importing camera view data. They effect how the view data is interpreted:

<ul>
<li>
'''Import vertical FOV:''' If this is checked the 7th or 8th value in each line, depending on the the file format, is read as the vertical field-of-view.
</li><li>
'''Import focal length:''' If this is checked the file must have 10 values per line. Value 8 is read as focal length, value 9 as aspect ratio and value 10 as horizontal aperture.
</li><li>
'''Import focal length to FOV:''' If this is checked the values are read as per '''Import focal length''' but the field-of-view parameters are also animated.
</li><li>
'''Do not import FOV:''' Field-of-view data isn't read from the file.
</li>
</ul>

For more information about importing chan files using the Camera node please read the [[Camera_-_Import_Tab|Import tab documentation]].

===Coordinate spaces===

In the case of motion data imported from object '''Import chan file''' buttons and the Camera chan import it's assumed the data is in Houdini coordinate space. It gets converted to TG2 coordinate space on import. Here's how the Houdini coordinate space compares to TG2:

* X (same as TG2) 
* Y (up, same as TG2) 
* Z (out of screen, negative/opposite to TG2) 
* Rotate X (pitch upwards, same as TG2) 
* Rotate Y (anti-clockwise* heading, negative/opposite to TG2) 
* Rotate Z (bank left, negative/opposite to TG2) 

* Heading is anti-clockwise when viewed as a heading on a map, but it's actually clockwise when viewed along the the positive Y axis.

[[Terragen 2 Animation Module Reference|Back to the Animation Module Reference]]

Terragen 2 Animation Module Reference

2012-05-16T02:50:31Z

← Older revision		Revision as of 02:50, 16 May 2012
(One intermediate revision by one user not shown)
Line 14:		Line 14:
	[[Main Window Timeline]]<br />		[[Main Window Timeline]]<br />
	Describes the timeline at the bottom of the main application window.		Describes the timeline at the bottom of the main application window.
		+
		+	[[Importing Animation Data from .chan/.mov Files]]<br />
		+	This describes how TG2 handles importing animation data from .chan and .mov files.

Grass Clump

2012-05-15T11:35:45Z

← Older revision		Revision as of 11:35, 15 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_192_image_0.png\|~~485pxpx~~\|Grass Clump]]	+	[[Image:drex_module_192_image_0.png\|center\|Grass Clump]]
		+
		+	'''Node Description and Purpose:'''<br />
		+	The Grass Clump object creates, as the name suggests, a clump of grass. The clump is round. The grass is made up of individual blades. The blades are denser toward the center of the clump. It's a simple but effective object. It might not stand up to close scrutiny but it's good for near middle to far distances.
		+
		+	Although a surface shader is created for the clump when the node is created the surface just has a grey default colour. You will need to change it to an appropriate colour.
		+
		+
		+	'''Node Type:''' Object<br />
		+
		+
		+	'''Settings:'''<br />
		+
		+	<ul>
		+	<li>
		+	'''Population mode:''' TBC
		+	</li><li>
		+	'''Preview mode:''' This popup lets you choose how the object should be displayed in the 3D Preview. This popup sets the most detailed mode that the object can be displayed in. The Object Display Mode button in the 3D Preview controls the mode for the preview as a whole. For example if you set the '''Preview mode''' of the object to Wireframe but the 3D Preview object display mode is set to '''Show as bounding boxes''' then the object will only be drawn as a bounding box.
		+	</li><li>
		+	'''Visible to camera:''' If this is checked the grass clump is visible to cameras such as the render camera. In other words it will show up in renders. If this is unchecked the grass clump won't show up in renders. However if, for example, the '''Cast shadows''' checkbox is checked then the shadows cast by the grass clump will still be visible.
		+	</li><li>
		+	'''Visible to other rays:''' When this is checked the grass clump is visible to various rays which are traced during rendering, such as reflection, transparency and GI rays. As an example, if this was unchecked the grass clump would not show up in reflections.
		+	</li><li>
		+	'''Cast shadows:''' This should be checked if you want the grass clump to cast shadows.
		+	</li><li>
		+	'''Double-sided surface:''' If this is checked object surfaces are double sided. A single sided surface is only visible from the "front", which is the direction the surface normal is pointing. If you look at it from the other direction the surface isn't visible. Double sided surfaces are visible from all directions.
		+	</li><li>
		+	'''Use smooth normals:''' If this is checked the object normals are interpolated to make the surface appear smooth. If it's unchecked the surface will look faceted.
		+	</li><li>
		+	'''Flip normals:''' Check this to flip or reverse the object normals.
		+	</li><li>
		+	'''Number of blades:''' This sets the number of grass blades in the clump.
		+	</li><li>
		+	'''Clump diameter:''' Use this to set the diameter of the clump.
		+	</li><li>
		+	'''Blade length:''' This sets the maximum length, or height, of the grass blades. The blades are given random lengths up to this value.
		+	</li>
		+	</ul>
		+
		+
		+	<u>Transform tab</u><br />
		+
		+	<ul>
		+	<li>
		+	'''Translate:''' This sets the position of the object.
		+	</li><li>
		+	'''Rotate:''' This rotates the object about its origin. The order of the values is heading, pitch then bank.
		+	</li><li>
		+	'''Scale:''' You can use this parameter to scale the object in the X, Y and Z directions.
		+	</li><li>
		+	'''Import chan file:''' Clicking this button allows you to import a .chan file for animating the object position and rotation.
		+	</li>
		+	</ul>

	==Additional tabs for Grass Clump==		==Additional tabs for Grass Clump==
Line 7:		Line 59:
	* [[Grass Clump - Surface Shaders Tab]]		* [[Grass Clump - Surface Shaders Tab]]

−	~~<!-- imported from file: module_192.html-->~~

	[[Category: Object Nodes]]		[[Category: Object Nodes]]

Terragen 2 Animation Module Reference

2012-05-15T10:37:33Z

← Older revision		Revision as of 10:37, 15 May 2012
Line 4:		Line 4:

	'''Important Note'''<br />		'''Important Note'''<br />
−	With the introduction of the Animation Module we needed to make changes to the way animation data is saved in project and clip files. This change happened in TG2 v2.4.20.0. Animation data in projects and clips saved from this version or newer cannot be loaded into older versions, but projects and clips from older versions can still be loaded into new versions. ~~Animaton~~ data in the old format is stripped out of files when they're saved with this version.	+	With the introduction of the Animation Module we needed to make changes to the way animation data is saved in project and clip files. This change happened in TG2 v2.4.20.0. Animation data in projects and clips saved from this version or newer cannot be loaded into older versions, but projects and clips from older versions can still be loaded into new versions. Animation data in the old format is stripped out of files when they're saved with this version.

	[[Animation Overview]]<br />		[[Animation Overview]]<br />

Rock - Angular Position Tab

2012-05-15T10:06:55Z

← Older revision		Revision as of 10:06, 15 May 2012
Line 1:		Line 1:
−	[[Image:drex_module_195_1_image_0.png\|~~465pxpx~~\|Rock - Angular Position Tab]]	+	[[Image:drex_module_195_1_image_0.png\|center\|Rock - Angular Position Tab]]
		+
		+	'''Description:'''<br />
		+	This tab has settings which use angles and distance to set the position of the rock relative to the scene origin. These settings are an alternative to using the '''Translate''' setting in the Transform tab. The diagram below shows how all the parameters relate to each other and the origin.<br />
		+	<br />
		+	[[image:angular_position.gif\|center]]
		+
		+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Heading:''' This angle sets the rotation of the object around the scene origin, in the XY plane, increasing as you turn clockwise.
		+	</li><li>
		+	'''Elevation:''' This angle sets the vertical part of the position. You could think of it as the angle above or below the horizon. 90 is straight up, -90 is straight down.
		+	</li><li>
		+	'''Distance:''' This sets the distance from the origin, in metres.
		+	</li>
		+	</ul>
		+

	Back to: [[Rock]]		Back to: [[Rock]]

−	~~<!-- imported from file: module_195_1.html-->~~

−	[[Category: ~~Rock\|~~ ]]	+	[[Category: Object Nodes ]]

Sphere - Angular Position Tab

2012-05-15T10:04:44Z

← Older revision		Revision as of 10:04, 15 May 2012
Line 2:		Line 2:

	'''Description:'''<br />		'''Description:'''<br />
−	This tab has settings which use angles and distance to set the position of the sphere relative to the scene origin. The diagram below shows how all the parameters relate to each other and the origin.<br />	+	This tab has settings which use angles and distance to set the position of the sphere relative to the scene origin. These settings are an alternative to using the '''Translate''' setting in the Transform tab. The diagram below shows how all the parameters relate to each other and the origin.<br />
	<br />		<br />
	[[image:angular_position.gif\|center]]		[[image:angular_position.gif\|center]]

Grass Clump - Angular Position Tab

2012-05-15T10:03:58Z

← Older revision		Revision as of 10:03, 15 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_192_1_image_0.png\|~~465pxpx~~\|Grass Clump - Angular Position Tab]]	+	[[Image:drex_module_192_1_image_0.png\|center\|Grass Clump - Angular Position Tab]]
		+
		+	'''Description:'''<br />
		+	This tab has settings which use angles and distance to set the position of the grass clump relative to the scene origin. These settings are an alternative to using the '''Translate''' setting in the Transform tab. The diagram below shows how all the parameters relate to each other and the origin.<br />
		+	<br />
		+	[[image:angular_position.gif\|center]]
		+
		+	'''Settings:'''<br />
		+	<ul>
		+	<li>
		+	'''Heading:''' This angle sets the rotation of the object around the scene origin, in the XY plane, increasing as you turn clockwise.
		+	</li><li>
		+	'''Elevation:''' This angle sets the vertical part of the position. You could think of it as the angle above or below the horizon. 90 is straight up, -90 is straight down.
		+	</li><li>
		+	'''Distance:''' This sets the distance from the origin, in metres.
		+	</li>
		+	</ul>
		+

	Back to: [[Grass Clump]]		Back to: [[Grass Clump]]

−	~~<!-- imported from file: module_192_1.html-->~~

−	[[Category: ~~Grass Clump\|~~ ]]	+	[[Category: Object Nodes ]]

Sphere - Angular Position Tab

2012-05-15T09:59:20Z

← Older revision		Revision as of 09:59, 15 May 2012
(3 intermediate revisions by one user not shown)
Line 1:		Line 1:
−	[[Image:drex_module_12_1_image_0.png\|~~465pxpx~~\|Sphere - Angular Position Tab]]	+	[[Image:drex_module_12_1_image_0.png\|center\|Sphere - Angular Position Tab]]

	'''Description:'''<br />		'''Description:'''<br />
−	~~The Angular Position~~ tab ~~contains~~ settings ~~relating~~ to the ~~angular~~ position of the sphere.	+	This tab has settings which use angles and distance to set the position of the sphere relative to the scene origin. The diagram below shows how all the parameters relate to each other and the origin.<br />
		+	<br />
		+	[[image:angular_position.gif\|center]]

−		+	'''Settings:'''<br />
−	'''Settings:'''	+
	<ul>		<ul>
	<li>		<li>
−	'''Heading:''' ~~TBC~~	+	'''Heading:''' This angle sets the rotation of the object around the scene origin, in the XY plane, increasing as you turn clockwise.
	</li><li>		</li><li>
−	'''Elevation:''' ~~TBC~~	+	'''Elevation:''' This angle sets the vertical part of the position. You could think of it as the angle above or below the horizon. 90 is straight up, -90 is straight down.
	</li><li>		</li><li>
−	'''Distance:''' ~~TBC~~	+	'''Distance:''' This sets the distance from the origin, in metres.
	</li>		</li>
	</ul>		</ul>
−

	Back to: [[Sphere]]		Back to: [[Sphere]]

−	~~<!-- imported from file: module_12_1.html-->~~

−	[[Category: ~~Sphere\|~~ ]]	+	[[Category: Object Nodes ]]

File:Angular position.gif

2012-05-15T09:55:21Z

uploaded "[[File:Angular position.gif]]" A diagram showing how angular position parameters are related.

Glossary

2012-05-15T05:27:01Z

← Older revision		Revision as of 05:27, 15 May 2012
(One intermediate revision by one user not shown)
Line 1:		Line 1:
		+	[[image:work_in_progress.jpg\|center]]
		+
		+	===B===
		+	;bucket
		+	:When TG2 renders it divides the image up into buckets or tiles. Each bucket is rendered separately, allowing multiple buckets to be rendered at once. It also allows memory to be used more efficiently.
		+
		+	===D===
		+	;DEM
		+	:DEM stands for Digital Elevation Model. A DEM is similar to a heightfield. DEMs are normally generated from measurements of a planet's surface.
		+
	===H===		===H===
	;heightfield		;heightfield

Main Page

2012-05-15T04:40:30Z

← Older revision		Revision as of 04:40, 15 May 2012
Line 31:		Line 31:
	[[Terragen 2 Node Reference]]<br />		[[Terragen 2 Node Reference]]<br />
	Describes all the TG2 nodes.		Describes all the TG2 nodes.
		+
		+	[[Glossary]]<br />
		+	The Glossary explains terms relevant to TG2.

	[[Terragen 2 Input Settings Reference\|Input Settings Reference]]<br />		[[Terragen 2 Input Settings Reference\|Input Settings Reference]]<br />

Glossary

2012-05-15T04:37:57Z

← Older revision		Revision as of 04:37, 15 May 2012
(One intermediate revision by one user not shown)
Line 7:		Line 7:
	;luminance		;luminance
	:TG2 converts RGB colours to greyscale by taking the luminance of the colour. This is essentially the brightness of the colour.		:TG2 converts RGB colours to greyscale by taking the luminance of the colour. This is essentially the brightness of the colour.
		+
		+	===P===
		+	;parameter
		+	:A parameter is an individual setting in a node parameter view which controls some aspect of the node.

	===R===		===R===
	;raster image		;raster image
	:In computer graphics, a raster image, or bitmap, is a dot matrix data structure representing a generally rectangular grid of pixels, or points of color, viewable via a monitor, paper, or other display medium.		:In computer graphics, a raster image, or bitmap, is a dot matrix data structure representing a generally rectangular grid of pixels, or points of color, viewable via a monitor, paper, or other display medium.
		+
		+	===S===
		+	;scalar
		+	:A scalar is a single number. 1, 200.45, -45, -0.2 are all examples of scalar values.
		+
		+	===V===
		+	;vector
		+	:A vector is a set of three scalars, normally representing X, Y and Z coordinates. It also commonly represents rotation, where the values are pitch, heading and bank.

Plane

2012-05-15T04:25:52Z

← Older revision		Revision as of 04:25, 15 May 2012
(One intermediate revision by one user not shown)
Line 9:		Line 9:
	The plane has quite a detailed preview. To help you size and orient the plane the A edge is drawn in orange and the B edge is drawn in magenta. The other two edges are drawn as dashed lines. The plane also has a full bounding box. If you can see the edges of the plane in the preview but not the plane itself then that means you are looking at the plane from "behind".		The plane has quite a detailed preview. To help you size and orient the plane the A edge is drawn in orange and the B edge is drawn in magenta. The other two edges are drawn as dashed lines. The plane also has a full bounding box. If you can see the edges of the plane in the preview but not the plane itself then that means you are looking at the plane from "behind".

−	[[image:~~plane_orientation~~.jpg\|center]]	+	[[image:plane_back_front.jpg\|center]]
−	<center><font size="-1">Left: Plane from "front". Right: Looking from "behind", plane isn't visible, though shadow still is.</font></center><br />	+	<center><font size="-1">Left: Plane from "front". Right: Looking from "behind", plane isn't visible, though shadow still is.</font></center><br />

	The plane is not the easiest object to position. The orientation of the plane is controlled by setting the direction of two of its edges, using the '''Edge vector a''' and '''Edge vector b''' parameters. Essentially you set the way the plane faces by pointing those two edges in appropriate directions.		The plane is not the easiest object to position. The orientation of the plane is controlled by setting the direction of two of its edges, using the '''Edge vector a''' and '''Edge vector b''' parameters. Essentially you set the way the plane faces by pointing those two edges in appropriate directions.