Trial & Error With My Assets

[Railroader1970]

As some of you have figured out, some of my assets have some issues, such as older Kuids with a Trainz Build of less than 3.5 such as 2.9 or even 2.1. I am figuring this out as I go and am attempting to rectify these issues with the current assets I am working by doing thorough scans by checking each Kuid number to see if I need to install updates.

Apologies for any inconveniences. I hope to have this situation fully resolved with the recent assets I am working on. Like I said, this is all a trial and error matter and I don't like issues with assets anymore than the next guy. For myself, it's a learning curve and I'm working on it.

Peace and cheers.

- Railroader1970 (RR70).

 

[oknotsen]

For your information, these are 20 assets that have your userID and are flagged as faulty:
<KUID:826627:100596> Autorack TTGX - OGHS Orange 2014 to 2021
<KUID:826627:101587> ARC Autoflood Coal Hopper DES 1
<KUID:826627:101621> OGHS GP38-2 Blood Orange 2021 B With Logo
<KUID:826627:101637> OGHS GP38-2 Blood Orange 2021 A With Logo
<KUID:826627:101822> ARC Autoflood Coal Hopper DES 2
<KUID:826627:101824> Autorack TTGX - OGH Orange H Logo 2021 Onward
<KUID:826627:101833> OGH Woodchip Open Hopper
<KUID:826627:101843> OGHS Gondola ACF 50 Ton With ARN 1 DES
<KUID:826627:101846> OGHS Gondola ACF 50 Ton With ARN 2 DES
<KUID:826627:101847> OGH Gondola ACF 50 Ton With ARN 1 DES
<KUID:826627:101850> OGH Gondola ACF 50 Ton With ARN 2 DES
<KUID:826627:101856> OGHS SD70M-2 2022 Orange/Black Ph 2 H Logo
<KUID:826627:101858> Interior for SD70ACe OGH/S Locomotive 3
<KUID:826627:101866> ARC Autoflood Coal Hopper DES 3
<KUID:826627:101871> Hopper Cyl OGH Black 2021 H Logo DES
<KUID:826627:101874> OGH SD70M-2 2022 Orange/Black B Ph 2 H Logo
<KUID:826627:101875> OGH SD70M-2 2022 Orange/Black C-X Ph 2 H Logo
<KUID:826627:101877> Interior for SD70ACe OGH/S Locomotive 4
<KUID:826627:101880> Interior for SD70ACe OGH/S Locomotive 5
<KUID:826627:102329> Barber S-2-b Trucks Black TB 3.5 DES

If you are going to fix them, be sure to upload them with the same KUID (so effectively KUID2:826627:xxxxxx:2) as that will automatically flag them as an update of the previous asset.

 

[Railroader1970]

For your information, these are 20 assets that have your userID and are flagged as faulty:
<KUID:826627:100596> Autorack TTGX - OGHS Orange 2014 to 2021
<KUID:826627:101587> ARC Autoflood Coal Hopper DES 1
<KUID:826627:101621> OGHS GP38-2 Blood Orange 2021 B With Logo
<KUID:826627:101637> OGHS GP38-2 Blood Orange 2021 A With Logo
<KUID:826627:101822> ARC Autoflood Coal Hopper DES 2
<KUID:826627:101824> Autorack TTGX - OGH Orange H Logo 2021 Onward
<KUID:826627:101833> OGH Woodchip Open Hopper
<KUID:826627:101843> OGHS Gondola ACF 50 Ton With ARN 1 DES
<KUID:826627:101846> OGHS Gondola ACF 50 Ton With ARN 2 DES
<KUID:826627:101847> OGH Gondola ACF 50 Ton With ARN 1 DES
<KUID:826627:101850> OGH Gondola ACF 50 Ton With ARN 2 DES
<KUID:826627:101856> OGHS SD70M-2 2022 Orange/Black Ph 2 H Logo
<KUID:826627:101858> Interior for SD70ACe OGH/S Locomotive 3
<KUID:826627:101866> ARC Autoflood Coal Hopper DES 3
<KUID:826627:101871> Hopper Cyl OGH Black 2021 H Logo DES
<KUID:826627:101874> OGH SD70M-2 2022 Orange/Black B Ph 2 H Logo
<KUID:826627:101875> OGH SD70M-2 2022 Orange/Black C-X Ph 2 H Logo
<KUID:826627:101877> Interior for SD70ACe OGH/S Locomotive 4
<KUID:826627:101880> Interior for SD70ACe OGH/S Locomotive 5
<KUID:826627:102329> Barber S-2-b Trucks Black TB 3.5 DES

If you are going to fix them, be sure to upload them with the same KUID (so effectively KUID2:826627:xxxxxx:2) as that will automatically flag them as an update of the previous asset.

Holy COW... So this means that I have to go into the Config File of these assets and check the Kuids inside of those assets to see if they need updates, correct? So once I do this, I just upload them again and that's all? Or how do I ass the "Kuid2" portion. I saw some Kuids with the 2 behind that word.

Thanks for bringing this to my attention!

- RR70

 

[martinvk]

Or how do I ass the "Kuid2" portion. I saw some Kuids with the 2 behind that wor

That's a do-it-yourself feature.
When you're in the config making changes, you change the kuid:nnnn:nnnn to kuid2:nnnn:nnnn:2 That way it's the same item just a newer version. The previous version will automatically be obsoleted.

 

[Railroader1970]

That's a do-it-yourself feature.
When you're in the config making changes, you change the kuid:nnnn:nnnn to kuid2:nnnn:nnnn:2 That way it's the same item just a newer version. The previous version will automatically be obsoleted.

So just to be clear and since I can do this myself, I do the following:

(1) Go to the Config File,
(2) Go down to the Kuid number of the asset,
(3) Change the Kuid number from Kuid:****:****: to Kuid2****:****:2. So put a 2 right after "Kuid" and another 2 at the end behind the last ),
(4) Click "Save",
(5) Commit the Asset.

Then we're good to go?

Correct?

 

[martinvk]

Yes, the two can then live side by side with older one flagged as obsolete. And that's all there is to it.
And the next time you make an improvement, the last number gets incremented, so 2 becomes 3 and then the next time 3 becomes 4, etc.

 

[Railroader1970]

Yes, the two can then live side by side with older one flagged as obsolete. And that's all there is to it.
And the next time you make an improvement, the last number gets incremented, so 2 becomes 3 and then the next time 3 becomes 4, etc.

So to use this example for conformation based on your current response:

Original Kuid#:

<KUID:747511:100130>

Change to New Kuid#:

<KUID2:747511:100130:2>

Yes?

Additional question: I saw some Kuid numbers that had a 2 right behind "Kuid" (like you demonstrated in your example) but a 1 for a final number behind the last ) instead of 2. What's that all about?

I know to some these questions will come across as ridiculous, but I would rather ask what some would call ridiculous question than to say nothing and make a ridiculous mistake.

- RR70

 

[Frank_Dean]

When I update an old object I do it in the following way:
1-I create a container folder for the new updates.
2-Inside that folder I put the folders of the old objects, with the old kuids.
3-Once those old objects have been updated, meshes changed, textures changed or labels changed in the config.tex then the last thing I do is change the kuid number.
example:
Old Kuid number: Kuid:xxxxx:xxxxx
First update: Kuid2:xxxxx:xxxxx:1
Second update: Kuid2:xxxxx:xxxxx:2
Third update: Kuid2:xxxxx:xxxxx:3
etc, etc.....

 

[Railroader1970]

When I update an old object I do it in the following way:
1-I create a container folder for the new updates.
2-Inside that folder I put the folders of the old objects, with the old kuids.
3-Once those old objects have been updated, meshes changed, textures changed or labels changed in the config.tex then the last thing I do is change the kuid number.
example:
Old Kuid number: Kuid:xxxxx:xxxxx
First update: Kuid2:xxxxx:xxxxx:1
Second update: Kuid2:xxxxx:xxxxx:2
Third update: Kuid2:xxxxx:xxxxx:3
etc, etc.....

Ah, ok. You said (in example 3) "meshes changed". I didn't know about that one. What do I do there and where can I learn about Trainz meshes? Are there detailed articles here on the forum I can study and ask questions on?

 

[martinvk]

some would call ridiculous question

There are no ridiculous questions, just ridiculous answers

 

[martinvk]

Ah, ok. You said (in example 3) "meshes changed". I didn't know about that one. What do I do there and where can I learn about Trainz meshes? Are there detailed articles here on the forum I can study and ask questions on?

Apart from minor changes in the config file, this is where it gets interesting. The mesh is created in a 3D modeling app and after some transformations is what you see as the object in Trainz. Every blade of grass, tree, building and all of the rolling stock started life this way. How to do it? That is a whole other question that takes a lot of study and learning. Best advice, start small. Make a simple box before trying to build your favourite locomotive.
There are many apps that can do this. The current favorite among creators is Blender. Old timers like me started with something call GMax and still use it for simple objects.Both are free but Blender is more modern and has way more support. Search for Blender tutorials here and on Youtube, there are plenty.

 

[Railroader1970]

Apart from minor changes in the config file, this is where it gets interesting. The mesh is created in a 3D modeling app and after some transformations is what you see as the object in Trainz. Every blade of grass, tree, building and all of the rolling stock started life this way. How to do it? That is a whole other question that takes a lot of study and learning. Best advice, start small. Make a simple box before trying to build your favourite locomotive.
There are many apps that can do this. The current favorite among creators is Blender. Old timers like me started with something call GMax and still use it for simple objects.Both are free but Blender is more modern and has way more support. Search for Blender tutorials here and on Youtube, there are plenty.

Copy that. Thanks for responding to my queries. I will look into these matters. If you have any extra advice or additional statements you wish to provide on this thread, go ahead.

Sincerely,

RR70

 

[martinvk]

Additional question: I saw some Kuid numbers that had a 2 right behind "Kuid" (like you demonstrated in your example) but a 1 for a final number behind the last ) instead of 2. What's that all about?

The 1 is a bit redundant since the original kuid is considered 1 even though it doesn't show it. The updated kuid, the second version is 2, the third update is 3 etc.

 

[johnwhelan]

So just to be clear and since I can do this myself, I do the following:

(1) Go to the Config File,
(2) Go down to the Kuid number of the asset,
(3) Change the Kuid number from Kuid:****:****: to Kuid2****:****:2. So put a 2 right after "Kuid" and another 2 at the end behind the last ),
(4) Click "Save",
(5) Commit the Asset.

Then we're good to go?

Correct?

The easy way in content manager is to just create new version from the content menu.

John

 

[Railroader1970]

The 1 is a bit redundant since the original kuid is considered 1 even though it doesn't show it. The updated kuid, the second version is 2, the third update is 3 etc.

Ah, ok. Got it. Thanks!

 

[Frank_Dean]

I stand by what I said in my post:
Original Kuid or the first one: kuid:XXXX:XXXX
First update: kuid2:XXXX:XXXX:1
Second update: kuid2:XXXX:XXXX:2
Third update: kuid2:XXXX:XXXX:3
etc,etc………
Copied from Trainz wiki:

KUID Version Number
<KUID2:171456:38001:1>
The third number, 1 in the example above, is the KUID Version Number.
Should this asset require revisions after release to the Download Station, the KUID Version Number for each subsequent revision may be updated as follows:
First revision <KUID2:xxx:yyyyy:1>
Second revision <KUID2:xxx:yyyyy:2>
Third revision <KUID2:xxx:yyyyy:3> Etc.
The maximum version number is 127. If the maximum version number should be reached, a new Content ID must be allocated for the asset, and the previous one needs to be added to the obsolete-table.
To make a new version asset, right click on the asset in Content Manager and select "Create New Version". The asset will be duplicated and the KUID Version Number will be updated in the new copy.

https://online.ts2009.com/mediaWiki/index.php/KUID

 

[Dinorius_Redundicus]

Frank Dean is correct, martinvk and oknotsen are unfortunately (and surprisingly) wrong on this.

The original kuid has the format <kuid:xxxxx:yyyyyy>
The first update should then be <kuid2:xxxxx:yyyyy:1>
The second update is <kuid2:xxxxx:yyyyy:2>
etc.

If you go straight to <kuid2:xxxxx:yyyyy:2> as the first update, CM will always list <kuid2:xxxxx:yyyyy:1> as “unknown”. In fact any gaps in the version number sequence will be listed as “unknown” which causes all sorts of needless confusion. So make sure the version numbers (the end section in the kuid2 format) form a continuous sequence, 1, 2, 3…

 

[Railroader1970]

Frank Dean is correct, martinvk and oknotsen are unfortunately and surprisingly wrong on this.

The original kuid has the format <kuid:xxxxx:yyyyyy>
The first update should then be <kuid2:xxxxx:yyyyy:1>
The second update is <kuid2:xxxxx:yyyyy:2>
etc.

If you go straight to <kuid2:xxxxx:yyyyy:2> as the first update, CM will always list <kuid2:xxxxx:yyyyy:1> as “unknown”. In fact any gaps in the version number sequence will be listed as “unknown” which causes all sorts of needless confusion. So make sure the version numbers (the end section in the kuid2 format) form a continuous sequence, 1, 2, 3…

WOW. That was a close call. Good thing I didn't do any Kuid updates yet. Ironically, however, other users I recently spoke to who downloaded the aforementioned assets that were listed by Oknotsen as faulty, NONE of them showed up on any of their systems as faulty. So I'm not sure what's going on here. But I will check all of the interior Kuid numbers in those assets to see if any of those need to be updated. I will accept responsibility for not thoroughly checking some of the inside Kuid numbers. Like I said, I'm learning as I go through trial and error.

 

[Dinorius_Redundicus]

WOW. That was a close call. Good thing I didn't do any Kuid updates yet.

That's why I got up extra early that morning and typed a reply.

I tried to obtain all of your assets listed in Oknotsen's post to see if they were faulty in TANE. I could only find these 2 on the DLS;

<KUID:826627:101621> OGHS GP38-2 Blood Orange 2021 B With Logo
<KUID:826627:101637> OGHS GP38-2 Blood Orange 2021 A With Logo

Both are faulty due to a missing asset (one of those dreaded "unknowns"); <kuid2:569535:100237:1> by mutanay77. This is the sort of chaos that comes from things not being on the DLS.

 

[Railroader1970]

That's why I got up extra early that morning and typed a reply.

I tried to obtain all of your assets listed in Oknotsen's post to see if they were faulty or not in TANE. I could only find these 2 on the DLS;

<KUID:826627:101621> OGHS GP38-2 Blood Orange 2021 B With Logo
<KUID:826627:101637> OGHS GP38-2 Blood Orange 2021 A With Logo

Both are faulty due to a missing asset (one of those dreaded "unknowns"); <kuid2:569535:100237:1> by mutanay77. This is the sort of chaos that comes from things not being on the DLS.

Really? Whoa.. I'll look up that Kuid # and see what I can do. Or I can replace the loco interior (since it's one that I reskinned in exchange for a standard issue interior). This means that the locomotives will only be viewable from the outside looking in while the inside looking out will have to be an interior someone clones and reskins themselves with the Loco Art of the asset the interior is a part of.

I will look into this situation asap and see if I can rectify the problem. I'm guessing that the missing asset you mentioned has to be part of the loco interior then because the other GP38-2 assets I reskinned with standard issue interiors uploaded fine to the DLS (except the two listed here on the thread).

Thanks a bunch for your checks on those faulty assets! And feel free to PM me if you have any other issues with my past assets and future ones too.

- Tom (RR70)