Frank_Dean
Well-known member
Discrepancies with the build of a wagon, train or other object with its dependencies.
This is a problem that although it is not very usual, is somewhat annoying for those nostalgic who do not use the latest version of Trainz available, and has an easy solution by not using or deleting the items that we downloaded with errors or unknown dependencies.
I am very clear that Trainz is a business that feeds its owners and employees with new sales and that in theory we should only use the latest version.
Currently in N3V is sold: TANE, 2019 and 2022 and in STEAM the same and also 2012, so if old versions of Trainz are sold, why not respect the builds in which the assets were built?
I am referring to the fact that if you upload or update a content with a build X, its dependencies to work have to be the same build x or lower, never higher.
The problem I am going to describe does not exist if you only use Trainz 2022, it is only if you use 2019,TANE or 2012.
There are more similar cases, but I will give only two examples of two authors who this year have uploaded their creations to the DLS. I have no desire to criticize the authors, but only to inform those who are interested. These authors have tested their wagons in 2022, with a lower Build, and as they work, they do not realize that if someone downloads and installs them in older versions they will not work, even though they have downloaded with a correct build for their version.
Example first, freight cars, with a Build 4.6 or 2019:
<kuid2:60238:39652:1> ATSF 40 foot Boxcar
<kuid2:60238:39674:1> Canadian Nationa 40 foot Boxcar
<kuid2:60238:39673:1> Chesapeake & Ohio 40 foot Boxcar
<kuid2:60238:39653:1> Conrail 40 foot Boxcar
<kuid2:60238:39671:1> Milwaukeec Road 40 foot Boxcar
<kuid2:60238:39651:1> Northern Pacific 40 foot Boxcar
<kuid2:60238:39672:1> Southern Pacific 40 foot Boxcar
<kuid2:60238:39654:1> Penn Central 40 foot Boxcar
They don't work in Trainz 2019, because they need the dependency:
<kuid2:523:19723699:1> Fruit and Vegetables Build 4.6, which is not in the DLS but is an internal dependency of Trainz 2022 and is not in 2019.
Second example, freight cars, with a Build 3.5 or Trainz 2012.
<kuid2:60238:39652:1> ATSF 40 foot Boxcar
<kuid2:60238:39674:1> Canadian Nationa 40 foot Boxcar
<kuid2:60238:39673:1> Chesapeake & Ohio 40 foot Boxcar
<kuid2:60238:39653:1> Conrail 40 foot Boxcar
<kuid2:60238:39671:1> Milwaukeec Road 40 foot Boxcar
<kuid2:60238:39651:1> Northern Pacific 40 foot Boxcar
<kuid2:60238:39672:1> Southern Pacific 40 foot Boxcar
<kuid2:60238:39654:1> Penn Central 40 foot Boxcar
They do not work in Trainz 2019, TANE or 2012 because they need the dependencies:
<kuid2:523:19723699:1> Fruit and Vegetables Build 4.6
<kuid2:523:19723702:2> Hardware Build 4.6
which is not in the DLS but are internal Trainz 2022 dependencies.
All the previous wagons can be used in 2019 if we look for those two dependencies in 2022 and install them in 2019, I have tested it and it is possible, both in TANE and in 2012 they do not work.
I apologize to the two authors mentioned if you feel offended or annoyed, I only intend to inform those who are interested, that the Build for which they were created has not been respected.
The solution is easy and quick, just use the wagons in 2022, as they work perfectly.
I apologize if any important meaning has been lost in the translation.
This is a problem that although it is not very usual, is somewhat annoying for those nostalgic who do not use the latest version of Trainz available, and has an easy solution by not using or deleting the items that we downloaded with errors or unknown dependencies.
I am very clear that Trainz is a business that feeds its owners and employees with new sales and that in theory we should only use the latest version.
Currently in N3V is sold: TANE, 2019 and 2022 and in STEAM the same and also 2012, so if old versions of Trainz are sold, why not respect the builds in which the assets were built?
I am referring to the fact that if you upload or update a content with a build X, its dependencies to work have to be the same build x or lower, never higher.
The problem I am going to describe does not exist if you only use Trainz 2022, it is only if you use 2019,TANE or 2012.
There are more similar cases, but I will give only two examples of two authors who this year have uploaded their creations to the DLS. I have no desire to criticize the authors, but only to inform those who are interested. These authors have tested their wagons in 2022, with a lower Build, and as they work, they do not realize that if someone downloads and installs them in older versions they will not work, even though they have downloaded with a correct build for their version.
Example first, freight cars, with a Build 4.6 or 2019:
<kuid2:60238:39652:1> ATSF 40 foot Boxcar
<kuid2:60238:39674:1> Canadian Nationa 40 foot Boxcar
<kuid2:60238:39673:1> Chesapeake & Ohio 40 foot Boxcar
<kuid2:60238:39653:1> Conrail 40 foot Boxcar
<kuid2:60238:39671:1> Milwaukeec Road 40 foot Boxcar
<kuid2:60238:39651:1> Northern Pacific 40 foot Boxcar
<kuid2:60238:39672:1> Southern Pacific 40 foot Boxcar
<kuid2:60238:39654:1> Penn Central 40 foot Boxcar
They don't work in Trainz 2019, because they need the dependency:
<kuid2:523:19723699:1> Fruit and Vegetables Build 4.6, which is not in the DLS but is an internal dependency of Trainz 2022 and is not in 2019.
Second example, freight cars, with a Build 3.5 or Trainz 2012.
<kuid2:60238:39652:1> ATSF 40 foot Boxcar
<kuid2:60238:39674:1> Canadian Nationa 40 foot Boxcar
<kuid2:60238:39673:1> Chesapeake & Ohio 40 foot Boxcar
<kuid2:60238:39653:1> Conrail 40 foot Boxcar
<kuid2:60238:39671:1> Milwaukeec Road 40 foot Boxcar
<kuid2:60238:39651:1> Northern Pacific 40 foot Boxcar
<kuid2:60238:39672:1> Southern Pacific 40 foot Boxcar
<kuid2:60238:39654:1> Penn Central 40 foot Boxcar
They do not work in Trainz 2019, TANE or 2012 because they need the dependencies:
<kuid2:523:19723699:1> Fruit and Vegetables Build 4.6
<kuid2:523:19723702:2> Hardware Build 4.6
which is not in the DLS but are internal Trainz 2022 dependencies.
All the previous wagons can be used in 2019 if we look for those two dependencies in 2022 and install them in 2019, I have tested it and it is possible, both in TANE and in 2012 they do not work.
I apologize to the two authors mentioned if you feel offended or annoyed, I only intend to inform those who are interested, that the Build for which they were created has not been respected.
The solution is easy and quick, just use the wagons in 2022, as they work perfectly.
I apologize if any important meaning has been lost in the translation.