...odd export behaviour...

[Jerker]

G'day geophil,

I appreciate that the following may not be a TransDEM issue, Roland but I am unable to reach a conclusion for the issue I am facing. After exporting a completely 'new' route that is nothing more than a blank terrain created from a DEM without any Topographic data nor any Route Polyline and 120 x 150 baseboards large...



...with the shown settings, I encounter the standard Windows (XP) error message ..."...taddeamon.exe has encountered a problem and needs to close..."... (etcetera - you know the one, I'm sure), shortly after attempting to import the 'route' into Trainz. At this time, although Trainz (Content Manager Plus) appears to work properly, the import seemingly continues on in the background and I am sure that the whole she-bang is awry, as the only way to stop the 'import' is to close down the importing dialogue box with Task Manager and when I do that, Trainz shuts down, as well, completely. The export from TransDEM, albeit very SLOWLY created, seems to 'go' correctly and all of the appropriate files are created and as they should be (I can certainly read the two *.txt files). A standard 'route' created and exported over the same period went through to completion without incident or error of any kind. This one route is just causing this problem...

...if you can provide any 'light at the end of the tunnel', it would be greatly appreciated...

Jerker {:)}

[geophil]

According to your screenshot you export the entire DEM, no route filter or rectangular mask active, which makes 120 x 150 baseboards in this case, yielding 18000 baseboards in total. That's quite a number. What's the size of the .gnd file? It could be the cause of evil.

[Jerker]

G'day geophil,

Roland, all of your observations regarding the export are quite correct. As it turn out, the *.gnd file weighs in at some 858 MBytes, which I would venture to say is 'rather large' but I did something similar to this many years back (in the days of TRS 2004, with MicroDEM and HOG), which involved twice the area being exported here, that produced an 'end result', as expected...

Jerker {:)}

[geophil]

Content Manager and its dependencies seem to be able to digest .gnd files up to around 500 MB. There's probably not a static limit, so it's more a rule of thumb.

[Jerker]

G'day Roland,

Hmmm! ..."...about 500 MB..."... you say? That wouldn't be closer to 512 MB, somehow 'interlinked' with the limit of a *.cdp file as set by Auran, would it?...

...it seems that the only way I may do this, then, is to split the export into 2 or more parts and to merge them in Trainz when the whole lot is done...

...thanks, again, for your assistance, Roland...

Jerker {:)}