Old Content coming back to life!

[Train-doc]

Well like many of you I have upgraded to 2010 and found a lot of my content not functional. Well with the help of some wonderful tools and a lot of patience. I have many classic locomotives and cars back from the deadline and rolling on the mainline.Since the files and meshes are not my property to share I can't exchange them with you but I can share my solutions with those in need. So if we maybe between myself and others and possibly the creators of these classics we can get them off the deadline.

Some examples that were problem children are
1.Gary Hoorn's PRR K4 5038 & tender ( now operational)
2. Magicland's PRR passenger cars (now operational)

the solutions are just patience and share the knowledge not the files .
Some files have spelling problems like minisize instead or minsize
or tags in the wrong place.

 

[johnwhelan]

Perhaps you could share your expertise here:

https://www.auran.com/planetauran/com_dls_cleanup.php

Cheerio John

 

[RRSignal]

The DLS Cleanup is being done in waves and, so far, no locos have been done. It's been mostly scenery, bogeys and a few interiors, so I suspect we'll start seeing the locos soon.

 

[wolfsong]

are most of the fixes text changes?

Hi,
I was wondering if most of the "fixes" are text changes. If so, with the use of a tools like SED and AWK, one can set up a way to save the differences/changes to the files and then leave them where everyone can pick them up and apply them without having to learn how to make each individual change manually. This has been done in the UNIX community for years but the tools are available under CYGWIN for free and they run on Windows platforms. I am sure there are a number of members who know all about using them. Just curious,
=gerry=

 

[johnwhelan]

Hi,
I was wondering if most of the "fixes" are text changes. If so, with the use of a tools like SED and AWK, one can set up a way to save the differences/changes to the files and then leave them where everyone can pick them up and apply them without having to learn how to make each individual change manually. This has been done in the UNIX community for years but the tools are available under CYGWIN for free and they run on Windows platforms. I am sure there are a number of members who know all about using them. Just curious,
=gerry=

The short answer is most need both the errors fixing and an update to the config files to include a mesh-table so not quite a straight edit.

http://forums.auran.com/trainz/showthread.php?t=68738

Cheerio John

 

[wolfsong]

What is the process at a high level?

Are the errors in text format in most cases along with the config file changes being in a text file or is there actual mesh editing with special tools? If just text in both cases without the use of mesh editing tools (or other binary massagers) then if diff files of the changes are created on the text files and setup for applying with SED (Streaming EDitor) then those can be passed around and applied by a batch/bash script which would come with it and save everyone from having to learn and edit the formatted text files on their own. That is what I was getting at but then you are probably going to tell me that most of the fixes require massaging binary files. Which way is it?

 

[RRSignal]

I already tried the automated approach long before the DLS Cleanup. Gone are the assets with merely a name tag missing a value - I think I've encountered 2 out of 1,600 assets I've repaired. By comparison, close to half the assets I repaired prior to the DLS cleanup (about 1,200) had that specific error. Which means, I suspect, that Auran did some in-house cleanup. Either, that or they are ignoring those for the time being.

Most of the errors are typos or tags TS2010 cannot parse properly, such as descriptions that got ganked up along the way so that now CMP thinks they're invalid tags, or tags with the value together.

I suppose the insertion of a thumbnail or changing of the trainz-build is something sed could readily handle, but it's so fast and easy to process a config file - not to mention CCP and AssetX (I think) partially automate this process anyway. I never really bothered to even explore the issue.

A large percentage are texture-related - usually, a misnamed or missing texture file. A very distant third are mesh errors.