Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
TUME-Street-101 is NOT on the Content Manager.
It doesn't appear either in T:ANE.
It has to tied to the :2 version. If you updated the asset pushed to the DLS, it does not show. Reverting back to :1, it shows.
Thanks for finding this. I'll make the change as well.
The problem is related to a bug I reported previously to N3V QA Team regarding this very issue. If a route has a certain KUID installed, something at version :1, for example, and the asset is updated to a :2, the route will show no missing dependencies locally.
However... If the route is exported and installed in another Trainz install, even if the :2 asset is installed, the route will still look for the :1 version.
This issue affects other assets that have dependencies and N3V is looking into the matter.
Perhaps if people seeing this problem for themselves would submit more Helpdesk tickets, N3V would put more resources into fixing it. Breakdown of the obsoleting system is a pretty serious issue I would have thought.
I'm still a bit confused by what's reported to be going on here. In this case, jbaxter 1964 is saying the problem is fixed by somehow getting version :1 and deleting version :2.
In the case of assets that call on mesh libraries, it's the opposite solution. The problem is fixed by deleting version :1 (of the mesh library) thereby forcing the dependent assets to use version :2. It should be looking for and using whatever is the latest version of the library even if older versions are still also present.
Either way, there is something very wrong with the way Trainz is handling the obsoleting system.
Yes there's a bug with the obsoleting system as you can see.
The problem is the route still has the version :1 in its object file list, and under normal circumstances, how things used to work, installing a version :2 would automatically obsolete the version :1 on the route and things would work. Everything is fine as long as things remain local. However... That's not the case here and things go a bit awry now if the route is exported and imported into another Trainz version. In this case the route is still referring to version :1 and is ignoring the fact that the version :2 may already be installed. Since this is a simple asset, changing the build number to version :1 gets around the unknown asset.
I agree this can get messy with mesh-table assets because things will get out of sync with the versioning.
Yeah, I didn't try updating the route config to point to :2. Probably would have worked, but I am not messing with it now. lol