Authors - Notice of Intent on Project TARM

[gisa]

Ian, I just had to say that I think you are doing a great thing for the community. I just got 2010 last night and I'm surprised to see some of the rolling stock that came with it has script errors. @@

There is some content that is outdated for sure, but I think there is a lot of content that is still great that I'd love to import and fix.

I'm not sure if I can do much to assist you (as I will have a very busy schedule coming this summer) but if you need someone to proof read or need a sounding board, let me know and I'll do what I can to help. The community has given so much to us (and to me) so I'd like to be able to help out if I can.

:wave:

Gisa ^^

 

[WindWalkr]

Ok, fair enough. Here is an example.....

The addition of your content file sharp_curves1.cdp has failed due to the following reasons:

<kuid2:87907:23135:1> : The tag 'name' in container 'scenery' is empty.

This seems legitimate - either the tag should not be there (in which case a default value is used) or the tag should have a properly formed value. There's no "good" case that I can think of where a name tag should be present but empty.

And we can't have this why ? Basically, what I read out of this is that we will continue to be frustrated because our versions show no errors and yours does.

You can, and by now, probably do.

We update the validation code from time to time. The code running on the DLS may at any given point be newer or older than the code available to users, depending on which was most recently released. We don't deliberately withhold fixes from users, but at the same time we don't generally release something publicly without a substantial amount of external testing. This introduces a delay between when we fix an issue, and when you have the fix.

chris

 

[EdrickV]

Judging from the build numbers he mentioned, Meridious would appear to be running TS2009 which explains why the DLS validation system was complaining about something that his Content Manager didn't. The DLS is using TS2010 standards. (That same tag without a value situation would show up as an error in TS2010's Content Manager.)http://forums.auran.com/trainz/member.php?u=57907

 

[meridious]

You are correct in that I'm using 09.

The "name" tag wasn't put there by myself. Most of the configs for my content were generated by Content Foundry from 04. This is just one reason why almost 375 pieces of my content show warnings. The goal posts keep moving from one version to the next.. I never had this issue until 09 came along. No, it isn't an error but it does show a warning which to quite a few people is just as bad.

I'm really not trying to place blame on anyone. I'm just expressing my frustrations.

 

[American_Connections]

If it ain't broke, don't fix it!

J...appear to be TS2009 which explains why the DLS validation system was complaining about something that his Content Manager didn't. The DLS is using TS2010 standards. (That same tag without a value situation would show up as an error in TS2010's Content Manager.)

Your tellin us that even 2009 standards are not good anymore for 2010! There is something very wrong here!

 

[Barry]

No comment

 

[EdrickV]

Your tellin us that even 2009 standards are not good anymore for 2010! There is something very wrong here!

Content Manager actually applies somewhat different standards to an item depending on it's build version, however it seems the error checking was tightened for all versions. 2.9 and higher however have tighter error checking standards then earlier content. For example there are at least a couple tags that, if missing a value, will not cause a warning in an older asset but will if the asset's build version is bumped up to 2.9. I've noticed that when using CCP to fix items. Two I can think of are contact-website and organization. I think those tags are ignored because they have no actual function in game. The name tag I assume actually was used for something. (Or at least was intended to be used for something.)

As for why the name tag got added in the first place, the creators of the program probably assumed that the user would go through and add the values to the tags but didn't think to have the program check for tags like that being left empty. (A tag with no value at best serves no purpose and at worst might result in Trainz crashing.)