Kuid files ending with 127

[km1961]

How do i get rid of these files. When i am installing I get this error on content manager and cannot clear it. I cannot download any of the files ending 127 as they cannot be found. I have checked the config files and again no mention of the said files.

I cannot upload a screenshot as it will not let me but it shows as an unknown asset. I have loads of the files ending in 127 which stops me loading up any of the assets associated that have the 127 file in the list.

What can I do?

 

[OddRails]

Here is a tip written earlier on the forum. It may help.

https://forums.auran.com/threads/ot...run-a-multiplayer-session.181904/post-2061849

Seeing a value of 127 makes me think that somehow an 8-bit register in the cpu got maxed out. But I'm not certain what might be using an ancient 8-bit register. Modern cpu's probably use 32-bit and 64-bit registers.

 

[stagecoach]

127 was given this emergency number when a creator incorrectly numbered the asset. kuid:11111:12345:2 is wrong because the kuid2 is missing, or kuid2:11111:12345, where the version number was missed..
Open the asset and delete the 27, and then submit. The reason I say delete the 27 is that a newer version above 1 may be available.

 

[HPL]

In Trainz Plus SP6 HF1, there are: one ":127" as "Base"; another one as "Built-in" ; and 99 as "Packaged". Additionally, I also have 113 of them in various payware. None causes trouble.

 

[JCitron]

Th Kuid2: range is "1" to "126". When the content-creator put in no asset version, the numbers wrapped and the result became :127. This to me is a bug that was never fixed in the Kuid2: system. There should have been a trap set to catch any empty asset versions.

 

[HPL]

Both Wikis say (here and here) that normal range is 1 to 127.

 

[pware]

How do i get rid of these files. When i am installing I get this error on content manager and cannot clear it. I cannot download any of the files ending 127 as they cannot be found.

From your description the problem is not with the :127 version numbers, as that is a normal part of the <kuid2> numbering system. Without seeing what the exact Content Manager error label is, or an example asset with this "issue", it seems that those assets are simply missing from the DLS. This is not an uncommon problem often (but not always) the result of asset creators including the missing assets in the config.txt file as dependencies when they are not actually needed.

I have checked the config files and again no mention of the said files.

The "missing files" could be referenced indirectly by one of the dependencies of the asset. You would need to check all the sub-dependencies and sub-sub-dependencies, etc, which would be a somewhat futile exercise.

Could you supply the <kuid> of a sample asset that is reported as having a missing :127 asset?