I am sure this has been mentioned before but I cannot find it in a search.
When I run TO for 2004 I get several faults pop up where the kuid number ends in 127. It tells me I must change them manually but what to? Is it 1 or 2 or 7????
Puzzled...
Angela
Angela
As others have said, this happens when a creator uploads a kuid2:XXX:YYYY:0 which, despite Auran's statements to the contrary, is not treated (by Content Dispatcher or possibly the DLS software) as equivalent to kuid:XXX:YYYY . Instead, the version number 0 gets bumped up to the highest possible value in the kuid2 format, which is 127. Auran still haven't fixed that as far as I know, so you may still occasionally see new 127's on the DLS.
Trainzobjectz sees it as an error, but in syntax terms, it's not - someone just might one day make 128 versions of something! The only downside is that the creator cannot obsolete a 127 asset via the kuid2 system. They presumably would need to use a whole new number (in the YYYY bit) and obsolete the 127 using an obsolete-table entry in the config.
If you manually change a 127 to something else, and manually adjust any dependencies that refer to it, then I guess it should still work on your system....
....BUT if the original creator decides to obsolete their 127 using the same number you manually chose, then there is a chance your download system will not 'see' it because it thinks you already have it. I think that's a possibility unless someone can tell me otherwise. Also if you upload an asset that uses the 127 as a dependency but refers to it by your manually inserted kuid number, then it will cause a 'missing kuid' error for other people trying to use your asset.
I've chosen to archive any 127's just to avoid the TO 'error' message and any possible errors arising from using 'non-official' kuid numbers. It also means my downloader will pick up any official versions that obsolete the 127's (a case in point being the new version of the Slugsmasher log dump industry uploaded to correct a 127 error).
~ D