From the files in this folder, you are using the standard UTM tile exporter, and you are creating 3D UTM tiles.
Possible issues I am aware of here with 2.5.*:
- Incomplete tiles, due to a strange lifecycle synchronization problem between the TransDEM parent and mesh generator child processes. That was addressed in TransDEM 2.5.1, a free update for all 2.5 users.
- Invalid mesh geometry for tiles close to the borders of the Trainz route. For 3D UTM tiles, the terrain source is the route itself, not the DEM loaded in TransDEM. These tiles should be avoided. (TransDEM 2.6 fills missing terrain with a substitute.)
- A few minor glitches that did not prevent CM import, most of them fixed in 2.5.1 as well, one or two in 2.6.
About the build number: As we all know, TransDEM 2.5 does not explicitly support T:ANE. But it is a long standing feature of Trainz Content Manager and Surveyor to accept assets built for an earlier version of Trainz. Content Manager may issue a warning for build numbers but should still process the object - unless there are more significant issues. (You cannot simply increase the build number because then more restrictive asset analysis kicks in, and for T:ANE CM, this means LOD for 3D UTM tiles. Solved in TransDEM 2.6.)
So I suggest to make sure you are running TransDEM 2.5.1. If 3D UTM tiles appear to be corrupt - rejected by CM - delete them and recreate them, few at a time. If the error persists for the very same locations, it may have to do with the route data source. Does the terrain for affected UTM tiles exist as a baseboard in the route? If not fully covered, then ignore those tiles.