"mesh-table" container - Revision history

Pcas1986: /* collision-data-generation-mode */ Added link to HowTo/Configure a spline for collisions

2026-09-05T03:32:33Z

collision-data-generation-mode: Added link to HowTo/Configure a spline for collisions

← Older revision		Revision as of 03:32, 5 September 2026
Line 147:		Line 147:
	:* "separate-shape-triangle-mesh" - this sub-mesh will generate its own individual collision object, as a triangle mesh. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.		:* "separate-shape-triangle-mesh" - this sub-mesh will generate its own individual collision object, as a triangle mesh. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.

	If you get the error "Failed to generate collision data". This will be because one of your meshes must have collision in order for Trainz to generate the collision data from it. If your mesh isn't suitable for collision generation then look at using a collision mesh. See [[%22mesh-table%22_container#Mesh-Table_Example_.28with_collision.29\|Mesh-Table Example (with collision)]] at the bottom of this page on how to do this.		If you get the error "Failed to generate collision data". This will be because one of your meshes must have collision in order for Trainz to generate the collision data from it. If your mesh isn't suitable for collision generation then look at using a collision mesh. See [[%22mesh-table%22_container#Mesh-Table_Example_.28with_collision.29\|Mesh-Table Example (with collision)]] at the bottom of this page on how to do this. See also this article discussing splines and collision data. [[HowTo/Configure a spline for collisions]]

	===collision-mesh===		===collision-mesh===

N3vpolsen at 00:07, 20 November 2025

2025-11-20T00:07:32Z

← Older revision		Revision as of 00:07, 20 November 2025
Line 147:		Line 147:
	:* "separate-shape-triangle-mesh" - this sub-mesh will generate its own individual collision object, as a triangle mesh. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.		:* "separate-shape-triangle-mesh" - this sub-mesh will generate its own individual collision object, as a triangle mesh. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.

	If you get the error "Failed to generate collision data". This will be because one of your meshes must have collision in order for Trainz to generate the collision data from it. If your mesh isn't suitable for collision generation then look at using a collision mesh. See Mesh-Table Example (with collision) at the bottom of this page on how to do this.		If you get the error "Failed to generate collision data". This will be because one of your meshes must have collision in order for Trainz to generate the collision data from it. If your mesh isn't suitable for collision generation then look at using a collision mesh. See [[%22mesh-table%22_container#Mesh-Table_Example_.28with_collision.29\|Mesh-Table Example (with collision)]] at the bottom of this page on how to do this.

	===collision-mesh===		===collision-mesh===

N3vpolsen at 00:04, 20 November 2025

2025-11-20T00:04:16Z

← Older revision		Revision as of 00:04, 20 November 2025
Line 146:		Line 146:
	:* "separate-shape-convex-hull" - this sub-mesh will generate its own individual collision object, as a convex hull.		:* "separate-shape-convex-hull" - this sub-mesh will generate its own individual collision object, as a convex hull.
	:* "separate-shape-triangle-mesh" - this sub-mesh will generate its own individual collision object, as a triangle mesh. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.		:* "separate-shape-triangle-mesh" - this sub-mesh will generate its own individual collision object, as a triangle mesh. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.

			If you get the error "Failed to generate collision data". This will be because one of your meshes must have collision in order for Trainz to generate the collision data from it. If your mesh isn't suitable for collision generation then look at using a collision mesh. See Mesh-Table Example (with collision) at the bottom of this page on how to do this.

	===collision-mesh===		===collision-mesh===

Ek.skirl at 18:15, 8 January 2024

2024-01-08T18:15:30Z

← Older revision		Revision as of 18:15, 8 January 2024
Line 216:		Line 216:
	===mesh-scale===		===mesh-scale===
	:Type: Floatlist		:Type: Floatlist
	:Default: 0,0,0		:Default: 1.0,1.0
	:Compulsory: No		:Compulsory: No
	:Desc: This tag defines a minimum and maximum scaling value for the mesh, where 1.0 is the size as modelled. Each instance of the mesh that exists in the world will randomise within this range. Randomisation will not change between runs or between Trainz editions, but may change based on factors such as the position of the mesh in the world. This tag is currently only supported on SpeedTree assets; attempts to use this tag on other assets results in undefined behaviour.		:Desc: This tag defines a minimum and maximum scaling value for the mesh, where 1.0 is the size as modelled. Each instance of the mesh that exists in the world will randomise within this range. Randomisation will not change between runs or between Trainz editions, but may change based on factors such as the position of the mesh in the world. This tag is currently only supported on SpeedTree assets; attempts to use this tag on other assets results in undefined behaviour.

Ek.skirl: correct orientation value from 0.0.0 to 0,0,0

2023-08-01T15:43:56Z

correct orientation value from 0.0.0 to 0,0,0

← Older revision		Revision as of 15:43, 1 August 2023
Line 88:		Line 88:
	\|-		\|-
	\| orientation		\| orientation
	\| 0.0.0		\| 0,0,0
	\|-		\|-
	\| position		\| position

Builderbob: Clarify

2020-04-02T00:06:11Z

Clarify

← Older revision		Revision as of 00:06, 2 April 2020
Line 206:		Line 206:
	:Default: <NULLKUID>		:Default: <NULLKUID>
	:Compulsory: No		:Compulsory: No
	:Desc: Specifies a mesh asset ~~library~~ to be used in conjunction with the 'mesh' tag. The mesh name specified in the 'mesh' tag must be located in ~~this~~ asset as Content Manager not check for the existence of the mesh. If the mesh is not located in the root folder of the mesh asset then ~~include the path as part of~~ the mesh name in the 'mesh' tag.		:Desc: Specifies a mesh asset to be used in conjunction with the 'mesh' tag when the mesh is not contained within the current asset. The mesh name specified in the 'mesh' tag must be located in the mesh asset as Content Manager does not check for the existence of the mesh and will not report an error if it is missing. If the mesh is not located in the root folder of the mesh asset then the mesh name in the 'mesh' tag must include the path to the folder.

	<div style="background-color: #ddf5eb;border-style: dotted; width:800px; overflow:auto; ">		<div style="background-color: #ddf5eb;border-style: dotted; width:800px; overflow:auto; ">
	NOTE: The KUID number ~~specified~~ must be the version of the asset ~~that is required for~~ the mesh in the 'mesh' tag ~~to be present~~.		NOTE: There may be several different versions of the mesh asset installed, with different meshes. The mesh asset KUID number must be the version of the asset in which the mesh in the 'mesh' tag exists.

	Example: If the mesh in the 'mesh' tag was added in kuid2:12345:9876:12 then this is the kuid number you must specify in the mesh-asset tag; specifying an older revision number (ie kuid:12345:9876 or kuid2:12345:9876:1) will result in errors.		Example: If the mesh in the 'mesh' tag was added in kuid2:12345:9876:2 and does not exist in earlier versions, then this is the kuid number you must specify in the mesh-asset tag; specifying an older revision number (ie kuid:12345:9876 or kuid2:12345:9876:1) will result in errors. This applies even if the only change between versions is that the mesh is in a different folder.
	</div>		</div>

S301: /* mesh-asset */

2020-01-22T01:43:00Z

mesh-asset

← Older revision		Revision as of 01:43, 22 January 2020
Line 206:		Line 206:
	:Default: <NULLKUID>		:Default: <NULLKUID>
	:Compulsory: No		:Compulsory: No
	:Desc: Specifies a mesh asset library to be used in conjunction with the 'mesh' tag. The mesh name specified in the 'mesh' tag must be located in this asset as Content Manager not check for the existence of the mesh. If the mesh is not located in the root folder of the mesh asset then include the path as part of the mesh name in the 'mesh' tag.		:Desc: Specifies a mesh asset library to be used in conjunction with the 'mesh' tag. The mesh name specified in the 'mesh' tag must be located in this asset as Content Manager not check for the existence of the mesh. If the mesh is not located in the root folder of the mesh asset then include the path as part of the mesh name in the 'mesh' tag.

			<div style="background-color: #ddf5eb;border-style: dotted; width:800px; overflow:auto; ">
			NOTE: The KUID number specified must be the version of the asset that is required for the mesh in the 'mesh' tag to be present.

			Example: If the mesh in the 'mesh' tag was added in kuid2:12345:9876:12 then this is the kuid number you must specify in the mesh-asset tag; specifying an older revision number (ie kuid:12345:9876 or kuid2:12345:9876:1) will result in errors.
			</div>

	===mesh-scale===		===mesh-scale===

Gdennish: Added mesh-table example with collision

2019-05-13T03:01:26Z

Added mesh-table example with collision

@@ Line 284: / Line 284: @@
       auto-create 1
       lod-level 1
+    }
+  }

Windwalkr at 05:39, 19 October 2017

2017-10-19T05:39:20Z

← Older revision		Revision as of 05:39, 19 October 2017
Line 26:		Line 26:
	==Level of Detail (LOD)==		==Level of Detail (LOD)==

	For discussions of LOD see [[~~Level_of_Detail~~]], [[~~LOD_Example~~]], [[mesh-table LOD]] and [[LM.~~txt_file~~]]		For discussions of LOD see [[Level of Detail]], [[LOD Example]], [[mesh-table LOD]] and [[LM.txt file]]

	==Mesh subcontainer==		==Mesh subcontainer==

Windwalkr at 05:38, 19 October 2017

2017-10-19T05:38:50Z

← Older revision		Revision as of 05:38, 19 October 2017
Line 26:		Line 26:
	==Level of Detail (LOD)==		==Level of Detail (LOD)==

	For discussions of LOD see [[Level_of_Detail]], [[LOD_Example]] and [[LM.txt_file]]		For discussions of LOD see [[Level_of_Detail]], [[LOD_Example]], [[mesh-table LOD]] and [[LM.txt_file]]

	==Mesh subcontainer==		==Mesh subcontainer==
Line 193:		Line 193:
	:Default: 255		:Default: 255
	:Compulsory: No		:Compulsory: No
	:Desc: The ~~object~~ LOD level at which this mesh is displayed. The default value (255) indicates that this mesh is visible at all detail levels. See also [[KIND Mesh]] for the 'mesh-detail-level' tag.		:Desc: The [[mesh-table LOD]] level at which this mesh is displayed. The default value (255) indicates that this mesh is visible at all detail levels. See also [[KIND Mesh]] for the 'mesh-detail-level' tag.

	===mesh===		===mesh===