HowTo/Bridge/mesh-table/mesh
(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 may...") |
|||
| (One intermediate revision by one user not shown) | |||
| Line 20: | Line 20: | ||
=== mesh subdirectories === | === mesh subdirectories === | ||
| − | Originally Trainz liked | + | Originally Trainz liked meshes 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" |
Latest revision as of 10:51, 9 February 2022
[edit] 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 meshes 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"
