Database Rebuild Problem

[trainguy77]

Looking for some wisdom and help. When running a database rebuild, it stalls at:
"Moving asaide unsaved asset edits: kuid 647439 101814 Layout 3 v76"
Then runs into a loop with:
"TrainzLockNativeFileSystem>resumable lock timeout:" and does not complete.

I can't find that kuid on my layout, or when I search the internet.

I'm running Trainz+22 on a Mac Studio M2, with plenty of storage space.

Any help here?
Thanks.

 

[CaseyBerg]

Dont’t have a solution, but I see by an earlier post you had this problem back in February and were going to open a ticket. No solution given to you ticket?

 

[JCitron]

The UID 647439 is your UID.

This must've been a route you are or were working on.

It appears the route data is corrupted and is preventing the DBR from working properly.


Open your user-data folder - the build folder associated with this version of TRS22. If you are not sure which one it is, click on Trainz settings on the Launcher and then the Install tab to view the name.

Using the Finder, open the folder and search for that kuid in that folder. There are multiple sub-folders and this search can take a while. Once found, copy the folder elsewhere and delete this one.

Run the DBR again to clean up the mess.

Hopefully this works. I've run into this before and this solved the problem for me.

 

[skittlekicks]

When this has happened to me, it was due to the route crashing and trying to rebuild immediately after.

The fix was to revert the route and then rerun the DB rebuild and then run the pre build command. This corrected stalls, the error message and unlocked the route.

This is why no matter how many minutes or hours I play, I always run the DB rebuild and pre build command before I ever close the launcher. This has kept Trainz 22 PE (Steam) stabile and working with little incident.

After logging more than 2300 hours in 9 months (yeah the journey was too addictive to quit), this technique has not failed me.

 

[trainguy77]

Thanks to both of you. I will try these. But first I need to restore a file. I inadvertently deleted a file that my session was dependent on - a parent kuid file. So the session wont load at all. But I had made a backup copy of the required file but not sure which folder to place it in to get the session to load.

 

[nabilk11]

go over to trash and that file may be there if you can find it

 

[JCitron]

Thanks to both of you. I will try these. But first I need to restore a file. I inadvertently deleted a file that my session was dependent on - a parent kuid file. So the session wont load at all. But I had made a backup copy of the required file but not sure which folder to place it in to get the session to load.

There are also Trainz backups. These are in your data-folder located under a Backups folder and are arranged by date. You can have up to 7-days of backups, not necessarily consecutive. Upon the 7th backup day, the oldest backup-day is removed.

If you modify, update, or delete any asset, Trainz will automatically create a backup of the asset. This is our content safety net and hopefully this will help you get your route back.

If you deleted your route within this backup window, open Finder and check the date you deleted your route, or maybe a day before if you were editing on those days.

Ignore any additional folders within the date-folders because the data is unusable for us.

Look for your route-name plus the kuid, or only the kuid.tzarc. In most cases, the route-backup will be the largest of the files in the folder.

Here's an example from one of my backups.

kuid 124863 101180.tzarc

Sometimes, there's a sequence number appended to the file.

kuid 124863 101180.tzarc_1209183964

These are subsequent backups since the first one occurred on that day.

How to restore your backup:

Copy the .tzarc file into the editing folder located in your User-data folder.

On the Launcher, click on Developer and then Rebuild database. This will restore your route.

If you choose one of the files with the kuid.tzarc_some-number, rename the file to remove the _some-number first.

 

[trainguy77]

Thanks JCitron, I am always grateful for your insights and responses. Thank you for your time. I was able to retrieve my layout. Unfortunately I cannot go back far enough with restoring backups to get a clean version. I have used your info to explore very usefully and have been able to clean some things up. Still have the issue - and it appears iterative. I have the main session file labelled 'Layout 3v76 - 0412 - 16:05, 12/4/24 - 00:00' <kuid:647439:101842>. I list faulty dependencies and I get a route file labelled 'Layout 3 v76 Default' kuid 647439:101814. When I list faulty dependencies on that, it shows the first file. But when I click on the route file I get the following:
Error: WorldList::ValidateBackingStoreFiles>missing file:mapfile_-1_0.obs, and
Error: VE180: Integrity check failure on mapfile_index.obs. One or more route/session tiles may be missing.
I cannot get info on what may be missing. I'm running out of ideas. I'm thinking I'm screwed!

 

[JCitron]

Thanks JCitron, I am always grateful for your insights and responses. Thank you for your time. I was able to retrieve my layout. Unfortunately I cannot go back far enough with restoring backups to get a clean version. I have used your info to explore very usefully and have been able to clean some things up. Still have the issue - and it appears iterative. I have the main session file labelled 'Layout 3v76 - 0412 - 16:05, 12/4/24 - 00:00' <kuid:647439:101842>. I list faulty dependencies and I get a route file labelled 'Layout 3 v76 Default' kuid 647439:101814. When I list faulty dependencies on that, it shows the first file. But when I click on the route file I get the following:
Error: WorldList::ValidateBackingStoreFiles>missing file:mapfile_-1_0.obs, and
Error: VE180: Integrity check failure on mapfile_index.obs. One or more route/session tiles may be missing.
I cannot get info on what may be missing. I'm running out of ideas. I'm thinking I'm screwed!

The .obs file missing is the hint. When TRS22 creates a route, it'll subdivide the route into small chunks labeled mapfile_-x_x.obs files. If any of these files are missing, the route is junk.

This is a relatively new system developed in the last TANE service pack to improve performance. In the olden days, Trainz versions would load a complete route into memory causing truly awful performance as the route grew in size. A single plain baseboard was fine but as routes got larger, and content got more complex while the route became more packed with objects, this caused a slideshow for many people.

Dividing the route up into sections allows TRS19 and TRS22 to handle large routes with lots of content fairly well compared to the older versions. There's still stutters and chunky performance in very packed baseboards with lots of old and poorly created content, but overall, the performance is quite good.

Anyway, I'm not sure what you can do with this going forward. Unless you have separate backup, meaning exported your route and session to a .cdp file, you are pretty much SOL unless you can find an older back up within your Trainz's own backup system. It's sad news to bear, but the data is trashed as far as I can tell.

I'm glad I can help you, well not completely in this case. As a retired network administrator and senior level tech, I spent my years on the front lines troubleshooting not only hardware but also software and providing support to a countless number of users. With lots of time on my hands now, I provide support to the community here since I am unable to create content and I am grateful for those that do, and donate my time through support. I don't know everything, even though it may appear that way, and I'm still learning something new every day.

 

[stagecoach]

Check in your backup folder and open the last backed-up copy of the route. Copy the missing file from the route folder and paste it into the working CM routes folder.

 

[trainguy77]

The .obs file missing is the hint. When TRS22 creates a route, it'll subdivide the route into small chunks labeled mapfile_-x_x.obs files. If any of these files are missing, the route is junk.

This is a relatively new system developed in the last TANE service pack to improve performance. In the olden days, Trainz versions would load a complete route into memory causing truly awful performance as the route grew in size. A single plain baseboard was fine but as routes got larger, and content got more complex while the route became more packed with objects, this caused a slideshow for many people.

Dividing the route up into sections allows TRS19 and TRS22 to handle large routes with lots of content fairly well compared to the older versions. There's still stutters and chunky performance in very packed baseboards with lots of old and poorly created content, but overall, the performance is quite good.

Anyway, I'm not sure what you can do with this going forward. Unless you have separate backup, meaning exported your route and session to a .cdp file, you are pretty much SOL unless you can find an older back up within your Trainz's own backup system. It's sad news to bear, but the data is trashed as far as I can tell.

I'm glad I can help you, well not completely in this case. As a retired network administrator and senior level tech, I spent my years on the front lines troubleshooting not only hardware but also software and providing support to a countless number of users. With lots of time on my hands now, I provide support to the community here since I am unable to create content and I am grateful for those that do, and donate my time through support. I don't know everything, even though it may appear that way, and I'm still learning something new every day.

Many thanks for this. All is not lost as a large part of the layout works fine. Some routes dont work though. Following your comment, I think the error may be a couple of track sections - the trains just stop there for no reason. I'm trying to replace the track in those section but no luck so far. So I've learned my lesson - backup, backup, backup - as I dont have backups far enough back to recover. Meanwhile, on to my next layout, and more learning.