Problems porting TANE to TRS22

trainlunitic

New member
Well. I finally switched to TRS22 after years of using TANE. I've been pretty successful in porting everything except my routes. In the warnings and errors section it states that:

This kuid '<kuid:844403:100003>' specified in 'map-kuid' is not of the correct type.

Any way to fix this? Or must I part ways with my route?
 
That would or should be in your session config.txt and associates your route with the session.

Make sure that that KUID belongs to the route and not something else. If it's incorrect, you can edit the session config.txt and change that KUID. You'll have to update that twice, so use a search and replace function to make that easier while editing the file in Notepad or some other text editor such as Notepad++.
 
That would or should be in your session config.txt and associates your route with the session.

Make sure that that KUID belongs to the route and not something else. If it's incorrect, you can edit the session config.txt and change that KUID. You'll have to update that twice, so use a search and replace function to make that easier while editing the file in Notepad or some other text editor such as Notepad++.
Okay, here's the config, I assume I have to change the map-kuid and #1 under the kuid table?



kuid <kuid:844403:100034>
kind "profile"
username "Eastern Sword Railroad"
trainz-build 4.5
map-kuid <kuid:844403:100003>
category-class "YP"
category-region "00"
category-era "2010s"
description

thumbnails
{
default
{
image "thumbnail.jpg"
width 240
height 180
}
}

string-table
{
}

rule-data
{
}

kuid-table
{
0 <kuid:-3:10083>
1 <kuid:844403:100003>
2 <kuid:-3:10057>
3 <kuid:-3:11209>
4 <kuid:-16:2025>
5 <kuid:-3:10058>
6 <kuid:-3:10186>
7 <kuid:-3:10077>
8 <kuid:-3:11149>
9 <kuid:401543:1180>
10 <kuid:-3:10076>
11 <kuid:-3:10081>
12 <kuid:-3:10082>
13 <kuid:-3:10090>
14 <kuid:-3:10206>
15 <kuid:-3:10078>
16 <kuid:401543:1090>
17 <kuid2:60850:89003:1>
18 <kuid:401543:1184>
19 <kuid:401543:3203>
}
 
Correct. These should point to the route your session is built for:
map-kuid <kuid:844403:100003>
1 <kuid:844403:100003>
 
<kuid:844403:100003> should read <kuid:844403:100034>
; <kuid:844403:100034> : Validating <kuid:844403:100034>
! <kuid:844403:100034> : VE179: The kuid '<kuid:844403:100034>' specified in 'map-kuid' is not of the correct type.
; <NULL> : Performing asset precache
; <kuid:844403:100034> : Loading asset <kuid:844403:100034>
- <kuid:844403:100034> : VE198: Session failed to load route asset: <kuid:844403:100034>
- <kuid:844403:100034> : VE199: Asset <kuid:844403:100034> failed to load. Unloading resources.
; <kuid:844403:100034> : TADGetSpecFromAsset> unlinked asset
 
NO, because <kuid:844403:100034> is the KUID of your session posted above. You can't refer to your session as a map within the very config.txt of the session.
kuid <kuid:844403:100034>
kind "profile" (kind "profile" is a session)
Inside the config, it is pointing to map-kuid <kuid:844403:100003> as the route the session goes to.

So, as Stagecoach asked above, What is the KUID of the route this session is for. Maybe tell us what route you are working with. According to your session file, the actual route map should be
map-kuid <kuid:844403:100003>
I do not have any assets by 844403, nor do there appear to be any on the DLS, so I cannot look up what this number is. <kuid:844403:100003> appears to be something other than a route, which is why it is throwing the error of "Invalid".

So we need to know two things to help you:

1. What is <kuid:844403:100003>?
2. What route is this session supposed to be for?
 
Hi, I figured it out. My sense of naming custom routes is non-existent, so when I first booted up TRS22 I created a new route and left it as "New Route". My old route from TANE was also named "New Route" so something must have happened where my TANE content somehow ended up in that first custom route I created in TRS22. I deleted it and re-installed the TANE route and it seems to have worked. Just some missing dependencies which I can fix easily. Sorry for any confusion I may have caused, and thank you for the help you provided.
 
Nice to know you figured it out. If there is one thing about Trainz, you will find there are lots of things to figure out! ;)
 
Having the same name is very confusing... Been there before with default sessions.

With two different Trainz versions, you do risk the chance of assets with the same kuid. Having the same name is confusing for us, but having the same kuid is bad for your data. A house can become a tree, or a route can go missing as you found out.
 
Back
Top