HowTo/Bogey/mesh - Revision history

Glt0145 at 00:51, 9 February 2022

2022-02-09T00:51:07Z

← Older revision		Revision as of 00:51, 9 February 2022
Line 36:		Line 36:

	===mesh subdirectories===		===mesh subdirectories===
	Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "meshes/a_mesh.trainzmesh"		Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes\a_mesh.im" or "meshes\a_mesh.trainzmesh"

Glt0145 at 00:40, 7 February 2022

2022-02-07T00:40:11Z

← Older revision		Revision as of 00:40, 7 February 2022
Line 36:		Line 36:

	===mesh subdirectories===		===mesh subdirectories===
	Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "meshes/a_mesh.~~tranzmesh~~"		Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "meshes/a_mesh.trainzmesh"

Glt0145 at 00:38, 7 February 2022

2022-02-07T00:38:57Z

← Older revision		Revision as of 00:38, 7 February 2022
Line 35:		Line 35:


	~~[edit]~~mesh subdirectories		===mesh subdirectories===
	Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "meshes/a_mesh.tranzmesh"		Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "meshes/a_mesh.tranzmesh"

Glt0145 at 00:38, 7 February 2022

2022-02-07T00:38:24Z

← Older revision		Revision as of 00:38, 7 February 2022
Line 36:		Line 36:

	[edit]mesh subdirectories		[edit]mesh subdirectories
	Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "~~night~~/a_mesh.tranzmesh"		Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "meshes/a_mesh.tranzmesh"

Glt0145 at 00:37, 7 February 2022

2022-02-07T00:37:49Z

← Older revision		Revision as of 00:37, 7 February 2022
Line 19:		Line 19:

	In the case of the shadow mesh it will be the name of the shadow mesh.		In the case of the shadow mesh it will be the name of the shadow mesh.

			This is a compulsory tag.

			Data type is string so it needs to be surrounded by "".

			This the name of the mesh that is being used within the asset. There maybe more than one mesh.

			Trainz uses and can understand two mesh extensions either ".im" or ".trainzmesh". The second one is the current file extension to the mesh. It is created by trainz when an asset is imported into trainz.

			If you have the ".lm" extension on the mesh name this point to a text file (LOD file). The mesh tag could also refer to the mesh itself i.e.. industry.im. If this were the case the asset would not have LOD mesh reduction.

			So an ".im" or ".trainzmesh" extension is referencing the asset mesh directly where as the "".lm" extension refers to a LOD text file with the mesh information contained within that text file.

			The ".lm" extension is mostly not used anymore and the LOD detains are contained within the main config file.


			[edit]mesh subdirectories
			Originally Trainz liked mesh that were not the main mesh to be in sub-directories. In recent editions and with the latest OS's all the mesh are now in one directory. This not a requirement and sub-directories can still be used, but the reference to the mesh must have the full location including the sub directory. Example maybe that the meshes are in a sub-directory call "meshes". So the reference to the mesh would be entered as "meshes/a_mesh.im" or "night/a_mesh.tranzmesh"

Glt0145 at 00:34, 7 February 2022

2022-02-07T00:34:36Z

← Older revision		Revision as of 00:34, 7 February 2022
Line 7:		Line 7:
	Data type is string so it needs to be surrounded by "".		Data type is string so it needs to be surrounded by "".

	This the name of the mesh that is being used within the asset. There maybe more than one mesh.		This the name of the mesh that is being used within the asset. There maybe more than one mesh.

			Trainz uses and can understand two mesh extensions either ".im" or ".trainzmesh". The second one is the current file extension to the mesh. It is created by trainz when an asset is imported into trainz. If a mesh is contained within a sub-directory of the directory containing the config file. Example the sub directory is "meshes" so the text would read "meshes\mesh.im"

	Trainz uses and can understand two mesh extensions either ".im" or ".trainzmesh". The second one is the current file extension to the mesh. It is created by trainz when an asset is imported into trainz.

	If you have the ".lm" extension on the mesh name this point to a text file (LOD file). The mesh tag could also refer to the mesh itself i.e.. industry.im. If this were the case the asset would not have LOD mesh reduction.		If you have the ".lm" extension on the mesh name this point to a text file (LOD file). The mesh tag could also refer to the mesh itself i.e.. industry.im. If this were the case the asset would not have LOD mesh reduction.
Line 16:		Line 17:

	The ".lm" extension is mostly not used anymore and the LOD detains are contained within the main config file.		The ".lm" extension is mostly not used anymore and the LOD detains are contained within the main config file.

			In the case of the shadow mesh it will be the name of the shadow mesh.

Glt0145: Created page with " == mesh == '''This is a compulsory tag.''' Data type is string so it needs to be surrounded by "". This the name of the mesh that is being used within the asset. There ma..."

2022-02-07T00:20:44Z

Created page with " == mesh == '''This is a compulsory tag.''' Data type is string so it needs to be surrounded by "". This the name of the mesh that is being used within the asset. There ma..."

New page

== mesh ==

'''This is a compulsory tag.'''

Data type is string so it needs to be surrounded by "".

This the name of the mesh that is being used within the asset. There maybe more than one mesh.

Trainz uses and can understand two mesh extensions either ".im" or ".trainzmesh". The second one is the current file extension to the mesh. It is created by trainz when an asset is imported into trainz.

If you have the ".lm" extension on the mesh name this point to a text file (LOD file). The mesh tag could also refer to the mesh itself i.e.. industry.im. If this were the case the asset would not have LOD mesh reduction.

So an ".im" or ".trainzmesh" extension is referencing the asset mesh directly where as the "".lm" extension refers to a LOD text file with the mesh information contained within that text file.

The ".lm" extension is mostly not used anymore and the LOD detains are contained within the main config file.