Stuck at load when merging modules of 1 MB or larger file size

Yes, definitely increase your RAM. Why only 1 TB drives? 2 TB are inexpensive now. Put your Trainz data on a 2 TB drive and be done with it. You can probably do some drive clean up and optimization too. The Trainz drive can lose the contents of backup folder periodically along with clearing the cache/internet folder. I've seen Trainz backups eat up to 50 GB of space or more if I do a lot of route building, downloads, and repairs.
In my defense, when I first built this PC, I didn't know Trainz would take up as much space as it does. So I thought a 1 TB drive would be all I would need. It also probably doesn't help that I've also got a few Steam games installed on my D drive as well.

Hindsight really is 20/20. ^^;
 
Right, system restart completed, DBR run and route reverted.

I'm going to try this one more time. I'll update and let y'all know if it worked or not.

P.S. What is the optimum time for a nine-board, 1.6 MB module to merge with a 6.1 MB route
I'm not sure if this was mentioned or not, but there should be no Consists on either of the Routes, except invisible ones used for Crossing Control.

Always use Find Command, Tools Menu, and look for Consists on each Route.

Prior to deleting them off my Routes, I make sure to save the ones I want in Trains Tab "add Consist" Button.

Also, if you want to see what Consists are installed Globally in your Trainz, Open CM and use Consist Category to display all the Consists you've made, bought with Routes, Payware etc. You might be surprised how many you have collected over time from yours, DLC and Payware purchases!

As a Bonus, if you do a Consists search on DLS, it will blow one's mind how many have been maid by Members. And you might see something you like too.

I think this one thing some folks are not aware of when they Merge Routes, I should also say, I have merged many Routes that had a few consists on one or both, but the Rub is, where is the cutoff point, that caused the Merge not to work?

So the cleaner the Route, less is more is a bonus when playing the merge Game.

Hope this is of some help.
 
Updating from the related thread to this one.

Turns out that it was the turntables that were causing the issues.

From the Route emerging issues thread:
----------------------------------------------
The track replacement went off without a hitch, and the module merges just fine now! However, I've also found another issue that was playing into my merging problems. It turns out that, for some reason, my game/PC refuses to merge any route that has a turntable onto an existing route! And just to be sure that it was the turntable that was causing the hangs, I created a new route with just a turntable sitting in the middle, then I tried to merge it with one of my other projects, and right on queue, it hung like a condemned outlaw.

You can get around this by using the offending route as the base route and merging everything else onto it, or just remove the turntable from the offending route, merge it, and then re-add the turntable.
------------------------------------------------

Merry Christmas y'all!
 
John, I'm trying a merge between two large routes now and it's hanging. I wonder if it's an issue with 19? Does 22 not have this problem? If so, I might move the two routes over to 22 and copy all the dependencies over then merge. I can't go backwards and move them into TANE. I hate when Trainz does a DBR after hanging because it takes so long. I just leave it run and do something else until it finishes.
 
John, I'm trying a merge between two large routes now and it's hanging. I wonder if it's an issue with 19? Does 22 not have this problem? If so, I might move the two routes over to 22 and copy all the dependencies over then merge. I can't go backwards and move them into TANE. I hate when Trainz does a DBR after hanging because it takes so long. I just leave it run and do something else until it finishes.
Merging isn't a problem in TRS22 or Plus. Large routes can take a long time and more RAM and disk space helps a lot. If you are using a regular disk, when was the last time you defragged the disk if this is a regular hard drive? That really helps too.

If Trainz crashes, a DBR will run. This is the way the program cleans up afterwards. I recommend defragging after a DBR
 
The only solution was to import the routes into 22 and merge, but I can't go back to 19 with the merged route so I'll have to use it in 22. I have a faulty tree, <kuid2:523:1113:1>Tree SugarMaple 02 but there is a working tree with the same name but different kuid. How can I obsolete the faulty tree with the good one? If I edit the config when it's open for edit and save, a wrong kuid error pops up and it won't commit. I have to revert. Somehow I managed to obsolete the bad tree in 19 but I forget how I did it. I want to do the same thing in 22. Maybe if I edit the config and save it outside the folder then paste it back in.
 
The only solution was to import the routes into 22 and merge, but I can't go back to 19 with the merged route so I'll have to use it in 22. I have a faulty tree, <kuid2:523:1113:1>Tree SugarMaple 02 but there is a working tree with the same name but different kuid. How can I obsolete the faulty tree with the good one? If I edit the config when it's open for edit and save, a wrong kuid error pops up and it won't commit. I have to revert. Somehow I managed to obsolete the bad tree in 19 but I forget how I did it. I want to do the same thing in 22. Maybe if I edit the config and save it outside the folder then paste it back in.
This is a built-in asset. Have you tried Reverting to original?
 
It had some errors I didn't know how to fix in 22 so I cloned the good tree and deleted the bad tree and pasted the kuid of the good tree in the cloned one. Now everything's ok.
 
It had some errors I didn't know how to fix in 22 so I cloned the good tree and deleted the bad tree and pasted the kuid of the good tree in the cloned one. Now everything's ok.
Speed Trees can't be repaired due to having code in them, besides built-in assets are encrypted and PEV's tools or any of our normal tools won't repair them.
 
There is a workaround for such faulty assets if you have a similar or identical asset with a different kuid. You clone the good asset, delete the bad asset and paste the kuid of the bad asset in your cloned one, replacing your kuid. Then the asset should show up in game so that you can replace it with something else with the bulk replace tool. Or you could leave it as is but then if you upload the route you should replace the cloned asset with one that is publicly available like the good asset that you cloned but the original one with the author's kuid. If the bad asset can never be fixed to work in a newer Trainz version then you might as well delete it.
 
Back
Top