Merging Layouts
- Thread starter johnno8H
- Start date
Simplest way is to decide which route you want to merge (usually the smaller one) and which you want to merge into. Big sticking point is the route layer names, most are simply named "route-layer" and it won't let you merge if they have the same name. So open the smaller route for edit, select the layers tab;
Click where it says route-layer and change it to something else. Save as, something like "merger", then exit and open the other route.
Main Menu, Merge Route, brings up a list of routes, select the new one you just cloned.
That brings up a map overlay, the orange is overlap. The arrows in the main window (red) scroll the current map around, the smaller arrows at the bottom (yellow) move the map being merged. Move it to the desired location with the bottom arrows, then check there's no overlap.
After that it's best to open the layers tab again, and merge the new route layer into the original so you don't get confused between layers.
Click where it says route-layer and change it to something else. Save as, something like "merger", then exit and open the other route.
Main Menu, Merge Route, brings up a list of routes, select the new one you just cloned.
That brings up a map overlay, the orange is overlap. The arrows in the main window (red) scroll the current map around, the smaller arrows at the bottom (yellow) move the map being merged. Move it to the desired location with the bottom arrows, then check there's no overlap.
After that it's best to open the layers tab again, and merge the new route layer into the original so you don't get confused between layers.
This seems to have been a problem with TS12 since it was first released. N3V have not yet fixed it. There are lots of posts on the forum complaining about this problem.
I have the opinion that it may be caused by the computer running out of available memory when trying to merge. I have found a workaround but there is a lot of work involved to prepare the layout you want to merge into the main map.
I have found that the amount of detail (ie number of assets) on the baseboards directly affects this. I have been able to merge a map with 60 baseboards with low detail yet at other times I could only merge about 15 boards when there has been a lot of assets on them.
Open the larger map in surveyor and merge the smaller layout into it. If this crashes, split the smaller layout into separate smaller maps and merge each piece, save, close and re-open the new larger layout. Keep going like this, merging each piece and saving etc. If at any stage it crashes again, split the piece you were trying to merge into smaller pieces.
By following this process I was able to merge two layouts each having a few hundred baseboards. It is an absolute pain in the butt and takes a lot of time to split the map you are going to merge into the main layout into smaller chunks.
The process used to be trouble free in 2009 and 2010 and I do not know why it has not been fixed yet in TS12.
Scottish
netting2010
New member
I have found that merging in TS12 can be difficult. Height is one issue and also north south aspect of the layouts to be merged is another as I understand you cannot rotate the maps. In the end I had to add some extra boards and then build a connection as required. If there is a height issue there are two options that I am aware of. 1. Accept the height variation and tailor the connection to suit or, 2, increase / decrease the height of one of the merged areas manually and then adjust the spline heights to match. There may be other ways that I am not aware of.
Please note I am new to this so I am happy to be corrected!!!
Please note I am new to this so I am happy to be corrected!!!
Hate to break it to you, but if you created a 3500 tile route you may already be mad!
Hmmm, just now tried it twice - two routes with 5x4 tiles each, total of 20 baseboard squares each, crashed 49922 every time I tried it. Works in 2010.
I tried a similar exercise after upgrading my system RAM to 24GB. The issue is still there. This must be a memory heap problem - pointers and such that the program references during the merging. I did successfully merge a route in but that was after removing all of the objects.
John
Hello,
Just for info.
Every time when I try to merge large routes ( big size ( created with Transdem ) - more than 500Mb ) or import content ( more than 500 Mb ) I get a Taddeamon error and Trainz is no further useable. By using task manager I am able to close Trainz and restart it again. I have this issue in Trainz2010 and 12 ( haven't tried it yet in 2009 ). Merging routes - for instance, a combination of large routes - 300Mb + 250Mb = same result, which is Taddaemon error.
So I started a ticket on May 18th 2012 ( Taddaemon error importing content larger than 500Mb into trainz ) . It seems to be a hard cookie to swallow :hehe:.
Best regards
Kurt :wave:
Just for info.
Every time when I try to merge large routes ( big size ( created with Transdem ) - more than 500Mb ) or import content ( more than 500 Mb ) I get a Taddeamon error and Trainz is no further useable. By using task manager I am able to close Trainz and restart it again. I have this issue in Trainz2010 and 12 ( haven't tried it yet in 2009 ). Merging routes - for instance, a combination of large routes - 300Mb + 250Mb = same result, which is Taddaemon error.
So I started a ticket on May 18th 2012 ( Taddaemon error importing content larger than 500Mb into trainz ) . It seems to be a hard cookie to swallow :hehe:.
Best regards
Kurt :wave:
Last edited:
Auran is aware of this issue and have stated that a fix is on the way in the next Service Pack. Don't hold your breath though , it has been several months that the issue has been known to them.
http://forums.auran.com/trainz/showthread.php?87778-Won-t-merge-Why-not&highlight=bolivar
http://forums.auran.com/trainz/showthread.php?87778-Won-t-merge-Why-not&highlight=bolivar
Last edited: