KIND Mesh - Revision history

Pw3r: /* mesh-table-lod-transition-distances */

2018-07-04T03:18:50Z

mesh-table-lod-transition-distances

← Older revision		Revision as of 03:18, 4 July 2018
Line 39:		Line 39:

	==mesh-table-lod-transition-distances==		==mesh-table-lod-transition-distances==
	The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[mesh-table LOD]] level ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array, no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index, effectively giving some number of meaningful LOD variants and a final "null" LOD where no rendering occurs.		The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[mesh-table LOD]] level ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array (i.e. to tag value), no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index, effectively giving some number of meaningful LOD variants and a final "null" LOD where no rendering occurs.

	This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].		This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].

Windwalkr: /* mesh-table-lod-transition-distances */

2017-10-19T05:40:06Z

mesh-table-lod-transition-distances

← Older revision		Revision as of 05:40, 19 October 2017
Line 39:		Line 39:

	==mesh-table-lod-transition-distances==		==mesh-table-lod-transition-distances==
	The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[~~Level of Detail\|~~mesh-table LOD ~~level~~]] ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array, no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index, effectively giving some number of meaningful LOD variants and a final "null" LOD where no rendering occurs.		The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[mesh-table LOD]] level ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array, no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index, effectively giving some number of meaningful LOD variants and a final "null" LOD where no rendering occurs.

	This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].		This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].

Windwalkr at 05:14, 19 October 2017

2017-10-19T05:14:45Z

← Older revision		Revision as of 05:14, 19 October 2017
Line 23:		Line 23:
	{		{
	}		}
	mesh-table-lod-transition-distances		mesh-table-lod-transition-distances
	season-selector		season-selector
	{		{

Windwalkr at 03:10, 16 October 2017

2017-10-16T03:10:04Z

← Older revision		Revision as of 03:10, 16 October 2017
Line 39:		Line 39:

	==mesh-table-lod-transition-distances==		==mesh-table-lod-transition-distances==
	The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[Level of Detail\|mesh-table LOD level]] ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array, no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index.		The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[Level of Detail\|mesh-table LOD level]] ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array, no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index, effectively giving some number of meaningful LOD variants and a final "null" LOD where no rendering occurs.

	This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].		This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].

			This tag does not override user settings for draw distance and scenery detail. If a LOD transition takes place beyond the master draw distance for that object type, it will never be visible. Furthermore, at lower detail settings the LOD ranges may be adjusted to be more aggressive than specified by the content creator.

	==mesh-table==		==mesh-table==

Windwalkr at 01:43, 16 October 2017

2017-10-16T01:43:46Z

← Older revision		Revision as of 01:43, 16 October 2017
Line 2:		Line 2:
	[[KIND Mesh]] provides the basis for many mesh-based assets. It may be used to create attachments, and acts as the basis for various standalone mesh-based objects.		[[KIND Mesh]] provides the basis for many mesh-based assets. It may be used to create attachments, and acts as the basis for various standalone mesh-based objects.

	This page describes [[trainz-build]] 4.5.		This page describes [[trainz-build]] 4.6.

	=KIND Hierarchy=		=KIND Hierarchy=
Line 23:		Line 23:
	{		{
	}		}
	mesh-~~detail~~-~~level~~-~~count 1~~		mesh-table-lod-transition-distances
	season-selector		season-selector
	{		{
Line 38:		Line 38:
	A scaling factor used to influence the way that this mesh is represented for in-game 3D asset pickers. This can be useful if the default display scale results in the asset being zoomed too far in or out for practical viewing.		A scaling factor used to influence the way that this mesh is represented for in-game 3D asset pickers. This can be useful if the default display scale results in the asset being zoomed too far in or out for practical viewing.

	==mesh-~~detail~~-~~level~~-~~count~~==		==mesh-table-lod-transition-distances==
	The "mesh-~~detail~~-~~level~~-~~count~~" tag determines ~~how many~~ mesh-table ~~LODs~~ are ~~supported by this asset~~. This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]] ~~but~~ is ~~not related to the~~ [[LM.txt file]] format.		The "mesh-table-lod-transition-distances" tag (float array) determines the distances in meters at which each [[Level of Detail\|mesh-table LOD level]] ends. This means that there is effectively one more mesh-table LOD than entries in this array. With an empty array, no mesh-table LOD is used. With three values in the array, four mesh-table LOD indices are used (ie. 0, 1, 2, 3). For small objects, it may be appropriate to not provide any meshes for the final mesh-table LOD index.

			This is used in conjunction with the "lod-level" tag in the [["mesh-table" Container]]. Note that mesh-table LOD is an entirely separate concept from [[LM.txt file]] format LOD. You should not attempt to configure the LM.txt transition distances using this tag. It is, however, possible to [[Advanced LOD Techniques\|combine the effects]].

	==mesh-table==		==mesh-table==

Windwalkr at 01:40, 9 August 2017

2017-08-09T01:40:40Z

← Older revision		Revision as of 01:40, 9 August 2017
Line 2:		Line 2:
	[[KIND Mesh]] provides the basis for many mesh-based assets. It may be used to create attachments, and acts as the basis for various standalone mesh-based objects.		[[KIND Mesh]] provides the basis for many mesh-based assets. It may be used to create attachments, and acts as the basis for various standalone mesh-based objects.

	This page describes [[trainz-build]] 4.1.		This page describes [[trainz-build]] 4.5.

	=KIND Hierarchy=		=KIND Hierarchy=

Windwalkr at 01:40, 9 August 2017

2017-08-09T01:40:31Z

← Older revision		Revision as of 01:40, 9 August 2017
Line 10:		Line 10:
	* [[KIND Product]]		* [[KIND Product]]
	* [[KIND Scenery]]		* [[KIND Scenery]]
	* [[KIND ~~Track~~]]		* [[KIND Bogey]]
			* [[KIND Interior]]
	* ~~...~~		* [[KIND Pantograph]]


Line 28:		Line 28:
	}		}
	visibility-radius (varies)		visibility-radius (varies)
			maximum-lod-distance 0


Line 51:		Line 52:
	==enable-pfx-collisions==		==enable-pfx-collisions==
	Bool value, defaults to 1 and is not compulsory. Defines whether or not this mesh object should be used for collision detection against particles (e.g. smoke, steam). Disabling it for objects that are unlikely to interact with particles is a good idea.		Bool value, defaults to 1 and is not compulsory. Defines whether or not this mesh object should be used for collision detection against particles (e.g. smoke, steam). Disabling it for objects that are unlikely to interact with particles is a good idea.

			==maximum-lod-distance==
			If specified, controls the distance (meters) at which the maximum mesh-table LOD is reached. Only valid if a mesh-detail-level-count is specified. If configured greater than the user's current scenery draw distance setting, the draw distance acts as the maximum limit instead.

	=Downloads=		=Downloads=

Pw3r: Reverted edits by Pcas1986 (talk) to last revision by Gevrard

2015-11-06T02:49:56Z

Reverted edits by Pcas1986 (talk) to last revision by Gevrard

← Older revision		Revision as of 02:49, 6 November 2015
Line 18:		Line 18:
	The [[KIND Mesh]] [[config.txt file]] supports the following tags. Each tag is show here with its default value.		The [[KIND Mesh]] [[config.txt file]] supports the following tags. Each tag is show here with its default value.

	~~{\| border=0 cellspacing=15px width=30%~~		preview-mesh-kuid <NULL>
	\|-		preview-scale 1.0
	~~\| enable~~-~~pfx~~-~~collisions \|\| 1~~		mesh-table
	\|-		{
	~~\| mesh-detail-level-count \|\|~~ 1		}
	\|-		mesh-detail-level-count 1
	\| mesh-table \|\| {		season-selector
	\|-		{
	\| }		}
	\|-		visibility-radius (varies)
	~~\| preview-~~mesh-~~kuid \|\| <NULL>~~
	\|-
	~~\| preview~~-~~scale \|\|~~ 1.0
	\|-
	\| season-selector \|\| {
	\|-
	\| }
	\|-
	\| visibility-radius \|\|(varies)
	\|}

	==preview-mesh-kuid==		==preview-mesh-kuid==

Pcas1986: Reformatted and updated supported tags table.

2015-06-03T14:16:50Z

Reformatted and updated supported tags table.

← Older revision		Revision as of 14:16, 3 June 2015
Line 18:		Line 18:
	The [[KIND Mesh]] [[config.txt file]] supports the following tags. Each tag is show here with its default value.		The [[KIND Mesh]] [[config.txt file]] supports the following tags. Each tag is show here with its default value.

	~~preview~~-mesh-~~kuid <NULL>~~		{\| border=0 cellspacing=15px width=30%
	~~preview~~-~~scale 1.0~~		\|-
	mesh-table		\| enable-pfx-collisions \|\| 1
	{		\|-
	}		\| mesh-detail-level-count \|\| 1
	mesh-~~detail~~-~~level~~-~~count~~ 1		\|-
	season-selector		\| mesh-table \|\| {
	{		\|-
	}		\| }
	visibility-radius (varies)		\|-
			\| preview-mesh-kuid \|\| <NULL>
			\|-
			\| preview-scale \|\| 1.0
			\|-
			\| season-selector \|\| {
			\|-
			\| }
			\|-
			\| visibility-radius \|\|(varies)
			\|}

	==preview-mesh-kuid==		==preview-mesh-kuid==

Gevrard at 06:28, 27 March 2015

2015-03-27T06:28:32Z

← Older revision		Revision as of 06:28, 27 March 2015
Line 1:		Line 1:
	{{ORP-top}}		{{ORP-top}}
	[[KIND Mesh]] provides the basis for many mesh-based assets. It may be used to create attachments, and acts as the basis for various standalone mesh-based objects.		[[KIND Mesh]] provides the basis for many mesh-based assets. It may be used to create attachments, and acts as the basis for various standalone mesh-based objects.

			This page describes [[trainz-build]] 4.1.

	=KIND Hierarchy=		=KIND Hierarchy=