Jointed Rail GP38-2 and GP40-2 errors

[cweis127]

I've been fiddling with Jointed Rail's road switchers and they all display errors after installation. These are all original

Such errors with the GP38-2's include:

Error: The Tag 'bogey' is not permitted within a container of type 'traincar'.
Error: The Tag 'bogey-1-r' is not permitted within a container of type 'traincar'.
Error: Tag 'category-region-0' in the container 'traincar' is obsolete.
Error: Tag 'category-era-0' in the container 'traincar' is obsolete.
Error: Tag 'category-era-1' in the container 'traincar' is obsolete.
Error: Tag 'category-era-2' in the container 'traincar' is obsolete.
Error: Tag 'category-era-3' in the container 'traincar' is obsolete.
Error: Tag 'asset-filename' in the container 'traincar' is obsolete.

The warnings for the GP38-2's and the GP40-2's are the same:

Warning: Required container 'bogeys' is missing.
Warning: Required container 'thumbnails' is missing.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.


I would appreciate if anyone can help me with resolving these issues. All I want is error-free locomotives to run and it is quite a disappointment when it works out this way

 

[Kris94]

I've been fiddling with Jointed Rail's road switchers and they all display errors after installation. These are all original

Such errors with the GP38-2's include:

Error: The Tag 'bogey' is not permitted within a container of type 'traincar'.
Error: The Tag 'bogey-1-r' is not permitted within a container of type 'traincar'.
Error: Tag 'category-region-0' in the container 'traincar' is obsolete.
Error: Tag 'category-era-0' in the container 'traincar' is obsolete.
Error: Tag 'category-era-1' in the container 'traincar' is obsolete.
Error: Tag 'category-era-2' in the container 'traincar' is obsolete.
Error: Tag 'category-era-3' in the container 'traincar' is obsolete.
Error: Tag 'asset-filename' in the container 'traincar' is obsolete.

The warnings for the GP38-2's and the GP40-2's are the same:

Warning: Required container 'bogeys' is missing.
Warning: Required container 'thumbnails' is missing.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.


I would appreciate if anyone can help me with resolving these issues. All I want is error-free locomotives to run and it is quite a disappointment when it works out this way

Go into CCP and just click on the errors and delete the containers. That will get rid of the errors and warnings.

 

[pdkoester]

I've been fiddling with Jointed Rail's road switchers and they all display errors after installation. These are all original

Such errors with the GP38-2's include:

Error: The Tag 'bogey' is not permitted within a container of type 'traincar'.
Error: The Tag 'bogey-1-r' is not permitted within a container of type 'traincar'.
Error: Tag 'category-region-0' in the container 'traincar' is obsolete.
Error: Tag 'category-era-0' in the container 'traincar' is obsolete.
Error: Tag 'category-era-1' in the container 'traincar' is obsolete.
Error: Tag 'category-era-2' in the container 'traincar' is obsolete.
Error: Tag 'category-era-3' in the container 'traincar' is obsolete.
Error: Tag 'asset-filename' in the container 'traincar' is obsolete.

The warnings for the GP38-2's and the GP40-2's are the same:

Warning: Required container 'bogeys' is missing.
Warning: Required container 'thumbnails' is missing.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.
Warning: An asset must be specified for tag 'texture-kuid'.


I would appreciate if anyone can help me with resolving these issues. All I want is error-free locomotives to run and it is quite a disappointment when it works out this way

Were you editing these and saving to version above 2.0? That may be the reason the errors are showing. I'm trying to replicate it.

Paul

 

[cweis127]

Yes. The units are, by default, build "2" and I upgraded them to build "3.4" and those tag errors are appearing

 

[colin55]

Use AssetX to fix things

 

[pdkoester]

I find if I use CCP and edit them, the ARN stops working. So... leave 'em at 2.0 if you really want to use these. No other reason to change them, if they work in game. Warnings are yellow and just an alert, nothing to prevent them from working.


Paul

 

[xcrossi]

Use AssetX to fix things

Same here....

 

[22alpha]

Go into CCP and just click on the errors and delete the containers. That will get rid of the errors and warnings.

NEVER go into CCP to edit any JR products, it will break it for sure. What prevented these from working provided as is?

Mike

 

[Southern1581]

Not necessarily, any JR unit using the current JR script (I believe it's 1.28) generally won't break if you go in and swap some stuff around. Stuff will get broken if it's on one of the older scripts though. I believe all of the GP38-2's/GP40-2's run on an older script, so editing in CCP would explain a lot of this. But I fail to understand how the heck the bogey containers went missing...and a lot of the other errors/warnings...

 

[jointedrail]

The bottom line on the whole thing here is.....they worked just fine right out of the CDP right out of the box. No editing or anything should be needed to make any of these work.

As always if you feel you need to edit anything of ours, do it in the config files. Do not do it in CCP, this takes the asset to the latest build version your running. This basically will blow the compatibility we have had to maintain between TS2009 SP4 thru TS12....

 

[titaniclover]

Not to add to this thread but I seem to be having an issue as well with these same locomotives just released.
I just re installed TS2010, updated to SP3 (build# under my user name) and while the locomotives can be placed they have no textures. These are actually my first content adds to the clean game. See image below.



The only errors on any of the assets associated with the locomotives are from the following KUID's:

<kuid2:45324:85302:2>
<kuid2:45324:85306:2>
<kuid2:45324:85317:2>
<kuid2:45324:85317:1>
<kuid2:45324:85303:1>
<kuid2:45324:85303:2>
<kuid2:45324:85316:2>

All have a variation (or exact match) of the following error:

Warning: The file '\cplr.lm' is provided in LM format despite having no attachment points and no animation support. This may have a negative impact on performance.

Any ideas anyone?

 

[jointedrail]

Open the asset up for edit, go into File,Settings/ Miscellaneous tab i believe it is and select Enable texture compression or something to that effect then recommit. It's in the bottom left corner. I dont recall it exactly since im not at my Trainz machine at the moment. Then recommit the asset and this shouldnt be an issue. The warning you posted has no bearing on the cplr.lm that is noted.

That part is of no concern and will not affect anything as far as the locomotive is concerned.

if this doesnt fix it, delete and reinstall the CDP.

 

[norfolksouthern37]

Not necessarily, any JR unit using the current JR script (I believe it's 1.28) generally won't break if you go in and swap some stuff around. Stuff will get broken if it's on one of the older scripts though. I believe all of the GP38-2's/GP40-2's run on an older script, so editing in CCP would explain a lot of this. But I fail to understand how the heck the bogey containers went missing...and a lot of the other errors/warnings...

it has nothing to do with the script but the configs. these were made at a point when we still supported 04 and up versions of TRS. since we have dropped support for versions before TS09, this will no longer be an issue for items created under those config specifications.

 

[titaniclover]

Hello,

Thanks for the tips. I found that it was actually enabled at start and disabled it instead and the textures on the locomotives show up, but not on the bogies or couplers! This even occurs after deleting the files and all associated files with the item. Fascinating development...
I wonder if it has something to do with my nVidia video settings. I will tinker with them and see if anything improves.

 

[cweis127]

Mine was asking to specify textures for certain containers and the bogey, front and rear, were needing tagged. I, from experience, know that CCP screws up ARN with locomotives and freight cars

 

[JohnnyC1]

Mine was asking to specify textures for certain containers and the bogey, front and rear, were needing tagged. I, from experience, know that CCP screws up ARN with locomotives and freight cars

If you are going to modify (upgrade to a higher build number) learn how to use Asset-X., especially if you have T12 H4. Otherwise leave things alone, it ain't broke!

John

 

[ex-railwayman]

Yes. The units are, by default, build "2" and I upgraded them to build "3.4" and those tag errors are appearing

So, don't change the build number then, there's no reason to fiddle with this at all, EVERYTHING I've installed in my TRS2009 works, even though half the stuff is build 1.3 and 2.0, no reason to change anything and I certainly don't alter Payware assets, cannot understand why folks ''upgrade'' assets you're only creating problems with stuff.

Oh, and for those of you who have category era errors, just delete all the lines, you only need to have a 1 line entry in the config. which reads -

category-era "1960s;1970s;1980s;1990s;2000s"


Cheerz. ex-railwayman.

 

[slave-driver]

Yes. The units are, by default, build "2" and I upgraded them to build "3.4" and those tag errors are appearing

You opened a can full of worms by changing the build number from 2 to 3.4. If all you had was a warning about an out of date build number I wouldn't have messed with it if you don't have experience with making and modifying configs. From past experience with updating my own content and fixing others I've installed it can get fairly intensive trying to get rid of all the errors with some of the changes that have happened within the configs from 2.9 and later. I would recommend deleting and reinstalling the content in question and without changing anything with the files commit it. Then if the only warning you get is "out of date build" don't mess with it.

Bill