Constant dependency KUID reference path issues

BraselC5048

Active member
I've got an annoying problem where whenever an asset config references another asset as a dependency, it only reads the specific Kuid version specificed (such as 12345:8>), and ignores any newer, updated Kuid versions also installed (such as 12345:10>), then becomes faulty since it needs a mesh/etc. that's only in the newer version. Or it doesn't reference an asset version (12355>), and can't find what it's looking for since it's only in the newer one (12345:2>), and as a result is faulty. I'm pretty sure that's not supposed to be how it works - do I have something in the settings wrong, or is it a deeper problem? (using SP5)

Thanks.
 
While I can't speak with any level of certainty or authority on the matter, I believe that this is a longstanding issue with the software and/or the database used to store Trainz assets. That said, hopefully someone with more knowledge on the matter can chip in with a proper explanation of this phenomenon.
 
So, what happens if the author has removed a mesh from the library and you have another asset that is depending on the older version? That's a rhetorical question since I already know its a problem.

It also bugs me that you have to open a mesh library for edit to find out what it contains. I think there should be a compulsory description file that is validated against the contents.
 
Back
Top