T:ANE Built-in's faulty in TRS2019

davesnow

Crabby Old Geezer
It would seem like good sense that anything built-in in T:ANE would import problem-free into TRS2019. That is not the case however. Whenever I try to transfer an "unknown asset" created by Auran from T:ANE to TRS2019 it invariably shows up as faulty.

I imagine a lot of map creators who used T:ANE built-in stuff are, or will become, frustrated when they try to transfer a route from T:ANE to TRS2019 and discover a multitude of assets show up as faulty.

Yeah yeah, I know I could probably go in and fix them, but I don't have the time or inclination. I'll go find some other game to play.
 
Revert won’t solve the problem.
A bunch of built-in TANE assets are faulty. They just don’t show faulty in TANE as the game prevents that from happening for built-in assets. When you export them and use them in a new version, that prevention is not there so the faulties show.
 
Last edited:
Revert won’t solve the problem.
A bunch of built-in TANE assets are faulty. They just don’t show faulty in TANE as the game prevents that from happening for built-in assets. When you export them and use them in a new version, that prevention is not there so the faulties show.

Typical case of "if they can't see the problem, there is no problem."
 
I had the same problem with built-in payware assets missing dependents and when checked there weren't any. I did an extended database repair which fixed all of faulty and missing dependencies issues.

John
 
I had the same problem with built-in payware assets missing dependents and when checked there weren't any. I did an extended database repair which fixed all of faulty and missing dependencies issues.

John

tried that and it did not help
I
 
My understanding is that N3V will be providing all the TANE built-in assets for TRS 2019. The remaining ones are to appear I think in the first non-beta version of TRS2019. which is to be released later this year.
 
My understanding is that N3V will be providing all the TANE built-in assets for TRS 2019. The remaining ones are to appear I think in the first non-beta version of TRS2019. which is to be released later this year.
They said the same about all the TS12 built-in content. I send in and bumped my tickets about missing TS12 content last month (and just checked they are still not there).
So...
I would not believe to much of that.
 
It would seem like good sense that anything built-in in T:ANE would import problem-free into TRS2019. That is not the case however. Whenever I try to transfer an "unknown asset" created by Auran from T:ANE to TRS2019 it invariably shows up as faulty.

You can't import built-in stuff. This has been the case for at least the last two versions. What was built-in will be either built-in for the new version or will be downloadable from the DLS. There are some exceptions, such as where the obsoleting has been done incorrectly and the new version isn't recognised as an update, some built-ins that were overlooked and aren't yet on the DLS, and some that never will be because they are incompatible with the new version. Of course, TRS2019 is still in beta, so it would be unreasonable to expect that all built-ins are included yet. Most everything that can be brought from TS12 should be available now, but there might be some missing T:aNE built-ins. If you find examples that you believe should be transferred you can submit the list as a bug report, as I presume that someone is keeping a list of old built-ins to be included.
 
Some of the built-ins can be made to work using PM2IM. This fixes the texture issues, but not script problems or incorrectly referenced aliased meshes, which require updating the mesh-table in the source asset.

I was able to import all the built-ins I used in to my test data using the method I noted. I don't recommend doing this for your final data because the PM2IM process actually degrades the images a small amount that is a bit noticeable on some assets, but for testing purposes it's fine.

As said "some of the built-ins" can be made to work. There are others such as those that are part of the DLC that won't work at all due to being encrypted as well as base assets. The assets can be opened, but cannot be saved again, and the textures will not unpack from the .texture files.
 
TANE content will be available to download as "free DLC" for TANE owners. We're not far away from making everything available.

You cannot import built-in assets from TANE, or indeed it will be faulty.
 
TANE content will be available to download as "free DLC" for TANE owners. We're not far away from making everything available.

You cannot import built-in assets from TANE, or indeed it will be faulty.




So what you're saying is, the routes we all created in T:ANE (or TS12 or whatever), any built-in content will not be available for TRS2019, so all those assets we used to create the route are gone forever. Or are you saying that eventually, those assets WILL work in TRS2019?
 
Once we release the TANE content for you to download, all your routes made in TANE will be fine.

I've just checked your MyTrainz account, and for some reason, you did not have 3 of the TANE builtin routes allocated. These have been added to your account.
Click File > Download purchased items, and download the routes that appear (they will have names like "sc237" etc.

Then can you please provide a list of your "unknown assets" to confirm if there are any still missing.

 
Then can you please provide a list of your "unknown assets" to confirm if there are any still missing.


<kuid2:9:35004:1>
<kuid2:68236:23100:2>
<kuid:146087:27900>
<kuid:370528:1276>
<kuid2:60238:38172:1>
<kuid2:146523:880:1>
<kuid:60850:27120>
<kuid:68787:100354>
<kuid2:303612:41:1>
<kuid2:64038:39081:2>
<kuid2:69038:27113:3>
<kuid2:60238:27113:1>
<kuid:75805:60009>
<kuid2:151900:500225:2>
<kuid2:64038:28115:1>
<kuid2:103475:37005:2>
<kuid:370528:1165>
<kuid2:148778:22014:2>
<kuid:127320:919998>
<kuid:506034:1150>
<kuid:370528:1172>
<kuid2:60238:56:1>
<kuid2:60238:38171:1>
<kuid2:60238:58:2>
<kuid2:148778:22010:3>
<kuid2:60238:26042:1>
<kuid2:124017:20117:3>
<kuid2:148893:21013:2>
<kuid2:151900:500117:2>
<kuid2:9000:27404:1>
<kuid:146087:60227>
<kuid2:38408:10051:1>
<kuid2:50305:27500:1>
<kuid2:68236:23074:1>
<kuid2:60238:32:1>
<kuid2:148893:21014:2>
<kuid2:124017:20118:3>
<kuid2:60238:38173:1>
<kuid2:60238:26141:1>
<kuid2:60238:29:3>
<kuid2:9000:27306:1>
<kuid2:146523:9000:1>
<kuid2:68236:23208:2>
<kuid:11:611>
<kuid2:68236:23075:1>
<kuid2:60238:38174:1>
<kuid2:60238:26142:1>
<kuid2:64038:27783:1>
<kuid2:9000:27501:1>
<kuid:146087:260845>
<kuid2:1942:25015:1>
<kuid:370528:1280>
<kuid2:60238:38212:1>
<kuid2:64038:32004:2>
<kuid2:124017:26043:3>
<kuid2:84609:28411:2>
<kuid:146087:60101>
<kuid2:148778:22013:3>
<kuid:370528:1163>
<kuid2:60238:27115:1>
<kuid:370528:1169>
<kuid2:50722:21008:1>
<kuid:378673:100056>
<kuid2:68236:23076:1>
<kuid2:60238:57:2>
<kuid2:9000:27101:1>
<kuid2:59545:100243:1>
<kuid2:59545:100254:1>
<kuid2:60238:24:1>
<kuid:1987:12>
 
They are all listed as built in for TRS2019 build 96000 except
<kuid2:84609:28411:2> Austin Mini Blue
<kuid:11:611> a-grass stripes
<kuid:1987:12> A12
<kuid2:303612:41:1> Bjorn
<kuid:75805:60009> A25 Forklift Truck
<kuid:370528:1280> Cow1
which are listed as Installed, Payware.
 
It looks to me like you haven't got ECML installed.

Check in CM for <kuid2:154322:101483:19> ECML Kings Cross - Edinburgh

Some of the assets are not part of the "builtin" content set, but instead are part of certain DLC items. Installing ECML should fix half of the problems. (Click File > Download purchased items, and download the routes that appear).

It is also possible that you've only partially installed some of the DLC/builtin routes.
Check the number of parts installed in your packages folder against this list:
http://online.ts2009.com/mediaWiki/...loading#Trainz_A_New_Era_.28Std_.2B_Deluxe.29
 
Last edited:
Back
Top