Asset "Avalable Soon" since last November 2022

[davesnow]

What's the deal with this?

 

[pware]

I don't know where that display is from or which version of Trainz it is referring to but my current Content Manager shows <kuid:101046:108166> as an <unknown asset>

 

[Forester1]

I am seeing "Image Not Found" from PostImage, Dave. But no sign of the KUID above anywhere.

 

[davesnow]

I am seeing "Image Not Found" from PostImage, Dave. But no sign of the KUID above anywhere.

Yes, apparently N3V removed the image. The Kuid has been waiting approval since November of last year.

 

[pware]

Yes, apparently N3V removed the image. The Kuid has been waiting approval since November of last year.

That replacement image came from your image hosting service, postimage.org which I also use. So N3V would not have removed it. The original image was not found (usually meaning: it was deleted) on the postimage.org server.

Have you tried resubmitting the asset or submitting it as an update to the original?

 

[davesnow]

Have you tried resubmitting the asset or submitting it as an update to the original?

Yes, I have tried resubmitting and I get a reply saying that asset is either already on the DLS or waiting approval. So, I guess it's still waiting approval!

 

[ZecMurphy]

Hi Davesnow
It appears that the asset was uploaded with an old (lower than 3.5) build number, which has caused it to be placed in the Content Repair Group's queue to update to build 3.5. Assets with a build below 3.5 are no longer accepted for new uploads, and as such will result in them being placed into the CRG's queue.

However, if you create a new revision/update to this asset with a 3.5 or higher build number, then you should be able to upload this and it will obsolete the current version that isn't fully available.
Regards

 

[dundun92]

I had this issue with my grain hoppers, because the script library (wagon x), was build 2.9. After re-uploading it at 5.0, everything worked fine.

 

[davesnow]

Hi Davesnow
It appears that the asset was uploaded with an old (lower than 3.5) build number, which has caused it to be placed in the Content Repair Group's queue to update to build 3.5. Assets with a build below 3.5 are no longer accepted for new uploads, and as such will result in them being placed into the CRG's queue.

However, if you create a new revision/update to this asset with a 3.5 or higher build number, then you should be able to upload this and it will obsolete the current version that isn't fully available.
Regards

Thanks Zec, I'll go that route.