![mesh enabler not installing mesh enabler not installing](https://helpx.adobe.com/content/dam/help/en/flash-player/kb/enabling-flash-player-safari/_jcr_content/main-pars/procedure_1639289420/proc_par/step_1/step_par/image/flash-player-entry.jpg)
The following effect kinds are supported:ĭesc: The mesh-table LOD level at which this mesh is displayed. The effect subcontainers support the following generic tags.Įach effect subcontainer supports additional tags depending on the effect kind. Setting this tag to true (1) means the mesh will cast shadows.Įffects Type: Corona Effect | Name Effect | Attachment Effect | Animation Effect | Texture-Replacement Effect Default ĭesc: The effects container can contain a list of effect subcontainers. Setting this tag to false (0) means the mesh will not cast shadows.
![mesh enabler not installing mesh enabler not installing](https://ars.els-cdn.com/content/image/1-s2.0-S0886779821004235-ga1.jpg)
Leaving this flag set to true (1) is a significant performance penalty.Ĭustom-render-plugin Type: KUID Default: ""ĭesc: "does-cast-shadows" determines if this mesh will cast shadows when the user has shadows enabled in the settings. If your asset is not scripted, does not use scripted animation events, or only uses the events for display purposes and will not break if the occasional event is missed, this tag should be set to false (0). The method used to generate the collision data (through the " collision-data-generation-mode" tag) is the one specified on this entry, which is allowed to be different from that of the referenced mesh.ĭefault: 1 (TBD: surely this should be false (0))ĭesc: "critical-animation" indicates that this mesh's animation generates events which are critical to the script system's behavior. This is the most accurate option but also the most costly in terms of performance, only use when specifically needed.ĭesc: Specifies a mesh to use instead of this mesh to generate collision data - must be an entry of this mesh-table.
![mesh enabler not installing mesh enabler not installing](https://www.mdpi.com/ijerph/ijerph-15-02816/article_deploy/html/images/ijerph-15-02816-g001.png)
The insertion attachment point is located within the mesh ‘name’, as listed in the config.txt.ĭesc: The model is generated automatically when placed, or when you load a map which includes the model. 0.5, 2.0) may be used in the tag to play the animation at a different speed from that created in the 3D modelling tool.ĭesc: The mesh (and animation if present) is inserted at a mesh attachment point rather than the origin (without this line the mesh is placed relative to the origin of the parent model).ĭefault: Defaults to "default" which is the parent meshĭesc: The tag tells Trainz in which mesh the attachment point is located. If this tag is not present when placed the animation will not play by default, but may play if controlled by script. This may include a sub-path.ĭesc: This tag must be present if the asset is to animate when placed. The att-parent tag can include a path.Įach mesh subcontainer supports the following tags.ĭesc: The animation file (.kin) exported from the 3D modelling tool and/or TrainzMeshImporter. * The att-parent defaults to "default" which is the parent mesh. Each tag is shown here with its default value. The following config containers also reference back to their Asset's mesh-table container in some fashion:įor discussions of LOD see Level of Detail, LOD Example, mesh-table LOD and LM.txt file Mesh subcontainerĮach mesh subcontainer supports the following tags. The Content Types listed here use the mesh-table container as part of their definition. Known Dependent Parent Types Main article, see: KIND Mesh These names are used to refer to specific meshes from within the mesh-table and also from script. Each mesh derives its name from the subcontainer's tag name.
#Mesh enabler not installing full
Tags are parsed in a standardised format, but not all Content Types support the full range of tags listed below. Each mesh subcontainer uses the following format. The mesh-table is a list of mesh subcontainers with no standalone tags. The "mesh-table" container is a top-level config.txt file entry used by various Content Types.