half of UTM ok, other half broken in TANE

[Chris750]

As the subject states, some are ok and others show as broken and saying wrong build version. Using TANE 81190 and Win 8.1. All were uploaded at the same time to the route so I am confused. Using TRANSDEM 2.5.0.13 as I don't wish to spend more money for the same program that I have already purchased.

[geophil]

Are you using the legacy UTM tile exporter? In version 2.5, TransDEM may copy the wrong asset. Which files do you have in the folder of a faulty UTM tile?

[Chris750]

I take it this is what you want?

[geophil]

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.

[Chris750]

Hi; These are the files I have, I thought I had everything I needed, which file and where do I get what is missing?





And I installed the 2.5.1 tex update but my version still shows as 2.5.0.13

[geophil]

The TransDEM 2.5.1 patch can be downloaded from my website. However, your version 2.5.0.13 is an unofficial in-between patch. The official patch won't work with it. You would have to uninstall TransDEM first, reinstall 2.5.0 and then apply the 2.5.1 patch.

Looking at my source code repository, most of the 3D UTM tile creation tweaks were made in February 2014. 2.5.0.13 dates from April 2014, so those tweaks should already be present in 2.5.0.13.

The example folder you listed in post #3 looks formally complete and I suspect the problem isn't the tile finalization / process synchronization issue but insufficient terrain coverage, particularly if the CM fault message is reproducible. 2.5.1 would not help here.

[Chris750]

Ok, so I need to get rid of the 25013 world origin patch, correct?

[geophil]

Ok, so I need to get rid of the 25013 world origin patch, correct?

Yes, to update to 2.5.1, uninstall current TransDEM first, then reinstall 2.5.0 from the original package. Every modification/fix/enhancement present 2.5.0.13 will also be present in 2.5.1.

Nonetheless, it may not have any effect on the faulty tiles.