Alias Mesh not found in dependency fix?

[Little_Boy921]

Is that located at Trainzforge?

Yes it is! I actually got it from there

 

[N3VSupport]

this is true I forgot about this but some mesh libraries will not use the latest version available for libraries if the old and new are installed.

Just to confirm, Trainz will error check against all installed mesh-library library revisions starting from the revision specified in the mesh-asset tag.

So if the mesh-asset tag specifies <kuid:648132:100797>, but the mesh being specified is only present in <kuid2:648132:100797:1>, then it will show an error if <kuid:648132:100797> is also installed. As such if you are specifying a new mesh added in an update to the mesh-library, you should specify that revision of the mesh-library in the mesh-asset tag.

Regards

 

[rwk]

I'm having this problem with two PRR signal bridges by rrsignal in 22PE. They are faulty because they reference an obsolete mesh library saying the error VE33: Alias mesh 'prrbridge4-4-lod0.im' not found in dependency <kuid:481384:1000000>. I don't think the signal bridges are faulty in older Trainz versions. The library installed is <kuid2:481384:1000000:11> PRR Catenary Mesh Library. The library was upversioned at some point with an 11 added to the end of the kuid. The signal bridges are referring to an obsolete version of the library that doesn't seem to exist thus the error. How do I get the signal bridges to show up in Trainz 22?

 

[p-dehnert]

Delete (or disable) all obsolete versions of the PRR Catenary Mesh Library, and keep only the latest version (currently <kuid2:481384:1000000:11>).

Peter

 

[pcas1986]

I recall being told that to access a deleted library mesh you should quote the last library version that did include it. That may mean quoting different library versions for different meshes used in the same asset. That's why I'm reluctant to delete obsolesent libraries.

I'm also sure different versions of Trainz behave differently in this matter.

 

[rwk]

It was an old library that was apparently conflicting and I deleted it. No errors now.