Problem with faulty asset <kuid:1942:28178> in TRS2006

[shaneturner12]

The asset in question is Station_Through_8T by tafweb. <kuid:1942:28178>

The errors reported in CMP for this asset are:

Error: Attachment point '55' in 'attachment-points' must be found in mesh '...'.
Error: Attachment point '55' in 'attachment-points' must be found in mesh '...'.
Error: Attachment point '57' in 'attachment-points' must be found in mesh '...'.

Unfortunately, as I do not have the original source files or knowledge of how to use PEV's AttachmentMaker, I'm a bit stuck. It seems to be causing all sorts of strange results in Trainz.

Anyone got any ideas on how to rectify this? (It has been downloaded from the DLS, and no changes have been made to it)

Shane

 

[itareus]

You could try deleting the (relevant) attachment point references from the config.txt file and see if the asset works OK....

 

[shaneturner12]

I will have a look, but after having a look in the config file, it seems very complex and has a lot of attachment points.

Shane

 

[itareus]

Shane,

tried this on mine and it's now error free in CM3.

Just look for attachment points:

a.sit60
a.passoff168
a.passoff224

and delete them.

 

[shaneturner12]

Strangely enough, I found what the problem was - a extra space between the attachment name and the " on the 3 lines you mentioned in your last post. Deleting the extra space seems to have cured the problem.

Thank you itareus, without the references in your last post, I wouldn't have found the problem.

Shane

EDIT: I am not being rude - I am actually very grateful for the info.

 

[itareus]

That "extra space" is interesting Shane - had a problem once (I think it was with TS2009 to TS2010) where many assets showed an error due to what appeared to be a "spacing" problem in the config - easy to sort but a PIA to do for 200 plus assets from various creators!!

I think it was due to the use of the "Tab" character when creating the config .txt file rather than the use of "Space" (or vice versa) causing a problem with Aurans conversion routine. Never did confirm this though.

Anyway, glad the problem is solved and thanks for the feedback.

Cheers

Chris

 

[shaneturner12]

I'm glad as well - I begin to wonder how many other people have had the same problem.

Don't worry, I always accept help when given it, and will always give help where my knowledge is aware of a fix/workaround or possibilities.

It still amazes me how a tab or space character can cause so many problems.

Thankyou again for the help though.

Shane

 

[rweber95]

"It still amazes me how a tab or space character can cause so many problems."
FYI from an old time assembly language programmer:
The space character is used by Trainz to parse the tags in Config.txt. This means that the parser reads the first string of characters in the config.txt file until it encounters a space and assumes this is a tag, then reads the next string of characters until it encounters an end of line indication and assumes those characters to be the data. If there is an extra space character any where in the line the parser pukes and gives an error indication.

Bob