Tex Coords From XYZ - Revision history

Redmaw: Updated overview and replaced example images.

2021-06-29T23:41:10Z

Updated overview and replaced example images.

← Older revision		Revision as of 23:41, 29 June 2021
Line 5:		Line 5:
	The Tex Coords from XYZ node generates world space texture coordinates for the shader or function nodes assigned its Main Input.		The Tex Coords from XYZ node generates world space texture coordinates for the shader or function nodes assigned its Main Input.

	~~That is~~, ~~it returns the current altitude of a given sample point which more than likely has been modified by displacements~~, ~~such~~ as ~~a Power fractal shader~~, from ~~its original position on~~ the ~~planet’s smooth surface~~.		Historically, this node was first written to compute texture coordinates, and later as the need for surface normals became apparent the Compute Normal node was written. Finally, the Compute Terrain node combines the functionality of the Tex Coords from XYZ node and the Compute Normal node into one node.

	~~Without this information, certain shaders within Terragen such as the Surface Layer shader~~, ~~might not have~~ the ~~correct altitude values at render time~~. ~~Click [[Render_State\|here~~]] ~~for more information about an item’s render state.~~		[[File:TexCoordXYZ_02_Nodes.png\|800px\|The Tex Coords from XYZ node returns world texture space coordinates. The Compute Normal returns surface normals, and the Compute Terrain node does both.]]

	~~Taking~~ the default Terragen project ~~for example~~, if ~~displacements occur after~~ the Compute ~~terrain~~ node in the Terrain ~~group then it’s possible that~~ a ~~Surface Layer shader providing colour information~~ for the ~~terrain might~~ not ~~have~~ the ~~correct altitudes~~ to ~~apply colour or constraints~~.
			It’s important to understand that in order for displacements and textures to be in sync and aligned, there should only exist one calculated solution within a given branch of the node network. This is why the Terrain Group ends with a Compute Terrain node in the default Terragen project before moving onto the Shaders Group. This workflow ensures that every shader will have consistent knowledge of the texture coordinates to work with. However, if your workflow doesn’t require normals to be known, such as using Redirect shaders and Vector displacement, then the Texture Coords from XYZ may be a faster solution than the Compute Terrain node because it only calculates texture coordinates.

			{\|
			\|-
			\| [[File:TexCoordXYZ_03_Comparision_Altitude.jpg\|800px\|When the Tex Coord from XYZ node or the Compute Terrain node is enabled, surface shaders have access to the displacement altitudes.]]
			\|-
			\|[[File:TexCoordXYZ_06_Comparision_Slope.jpg\|800px\|When the Tex Coord from XYZ node is enabled (and there is no Compute Terrain node), surface shaders do not have have access to the displacement altitudes because the surface normals have not been calculated.]]
			\|-
			\| [[File:TexCoordXYZ_10_ComputeTerrainOn.jpg\|800px\|Some shaders, such as the Surface Layer, have Slope Key and Altitude Key settings which allow you to access the Final position of the surface and not just the last Compute Terrain or Tex Coords from XYZ nodes within the node network branch.]]
			\|}


			Therefore, having a Tex Coords from XYZ and a Compute Terrain node in the same branch of a pipeline is not recommended. Multiple Tex Coordinates from XYZ and/or Compute Terrain nodes can exist in a project provided they’re not being used by the same node network branch. For example, a Compute terrain node with a Patch Size of 200 could exist and be used for populations only, while another Compute terrain node with a Patch Size of 20 is connected from the Terrain group (displacements) to the Shader group (texturing).

			[[File:TexCoordXYZ_08_ComputeTerrainOn.jpg\|800px\|In this example, the forest population uses the Compute Terrain node with a Patch Size of 200 and not the Tex Coords from XYZ in order to access the terrain’s slope information.]]


			Certain workflows may also benefit by having the major surface displacement nodes positioned prior to the Compute Terrain node, and having the smaller, secondary displacements, such as a Strata and Outcrop shader occur after the Compute Terrain node.


Line 18:		Line 36:

	*'''Enable: '''When checked, the node is active and the current world space texture coordinates will be calculated for the shader or function nodes assigned to the Main input. This includes all nodes upstream from the assigned shader node.		*'''Enable: '''When checked, the node is active and the current world space texture coordinates will be calculated for the shader or function nodes assigned to the Main input. This includes all nodes upstream from the assigned shader node.
	~~</ul>~~


	~~[[File:TexCoordXYZ_01_Example.jpg\|none\|800px\|Workflow showing a displaced terrain with and without using a Tex Coord From XYZ node.]]~~

	</br>		</br>

Redmaw: Added link to Render State wiki page

2021-06-15T12:02:27Z

Added link to Render State wiki page

← Older revision		Revision as of 12:02, 15 June 2021
Line 7:		Line 7:
	That is, it returns the current altitude of a given sample point which more than likely has been modified by displacements, such as a Power fractal shader, from its original position on the planet’s smooth surface.		That is, it returns the current altitude of a given sample point which more than likely has been modified by displacements, such as a Power fractal shader, from its original position on the planet’s smooth surface.

	Without this information, certain shaders within Terragen such as the Surface Layer shader, might not have the correct altitude values at render time. Click here for more information about an item’s render state.		Without this information, certain shaders within Terragen such as the Surface Layer shader, might not have the correct altitude values at render time. Click [[Render_State\|here]] for more information about an item’s render state.

	Taking the default Terragen project for example, if displacements occur after the Compute terrain node in the Terrain group then it’s possible that a Surface Layer shader providing colour information for the terrain might not have the correct altitudes to apply colour or constraints.		Taking the default Terragen project for example, if displacements occur after the Compute terrain node in the Terrain group then it’s possible that a Surface Layer shader providing colour information for the terrain might not have the correct altitudes to apply colour or constraints.

Redmaw: Enhanced description for node and added example image.

2021-06-15T01:27:41Z

Enhanced description for node and added example image.

@@ Line 1: / Line 1: @@
-[[Image:drex_module_174_image_0.png|center|Tex Coords From XYZ]]
+[[File:TexCoordXYZ_00_GUI.png|none|470px|Tex Coords From XYZ]]
-'''Node Type:''' Other Shader<br />
+That is, it returns the current altitude of a given sample point which more than likely has been modified by displacements, such as a Power fractal shader, from its original position on the planet’s smooth surface.
 [[Category:Other Shader]]

Jo at 09:36, 16 May 2012

2012-05-16T09:36:56Z

← Older revision		Revision as of 09:36, 16 May 2012
Line 3:		Line 3:
	'''Node Description and Purpose:'''<br />		'''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.		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 />


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

Jo at 09:36, 16 May 2012

2012-05-16T09:36:14Z

← Older revision		Revision as of 09:36, 16 May 2012
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.

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

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

JavaJones at 19:53, 1 June 2011

2011-06-01T19:53:16Z

← Older revision		Revision as of 19:53, 1 June 2011
Line 1:		Line 1:
	~~[[Category:IMPORT]]~~
	~~='''Tex Coords From XYZ'''=~~

	[[Image:drex_module_174_image_0.png\|485pxpx\|Tex Coords From XYZ]]		[[Image:drex_module_174_image_0.png\|485pxpx\|Tex Coords From XYZ]]

	Generates world space texture coordinates from the input functions. Does not compute normals.		Generates world space texture coordinates from the input functions. Does not compute normals.

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

			[[Category:Other Shader]]

JavaJones at 19:43, 28 April 2011

2011-04-28T19:43:14Z

← Older revision		Revision as of 19:43, 28 April 2011
Line 3:		Line 3:

	[[Image:drex_module_174_image_0.png\|485pxpx\|Tex Coords From XYZ]]		[[Image:drex_module_174_image_0.png\|485pxpx\|Tex Coords From XYZ]]

			Generates world space texture coordinates from the input functions. Does not compute normals.

	__NOTOC__		__NOTOC__
	<!-- imported from file: module_174.html-->		<!-- imported from file: module_174.html-->

127.0.0.1: jrfconvert import

2010-07-11T02:55:05Z

jrfconvert import

New page

[[Category:IMPORT]]
='''Tex Coords From XYZ'''=

[[Image:drex_module_174_image_0.png|485pxpx|Tex Coords From XYZ]]
__NOTOC__