Does the merge route always have the same origin?

realm

New member
I am currently creating a fairly large layout. In order to make this easier, it is actually a multiple of smaller layouts that I merge in as I go. The problem I am having, however, is that when I add any of the smaller layouts into the larger one, the smaller one always show up at the same spot, which means I need to move it to where it belongs. I do know how to do that, however, it's becoming more and more tedious to do that, as the destination point is further and further away from where it shows up.

Does anyone know if there's any way to change where it shows up?

thanks!

realm
 
I am currently creating a fairly large layout. In order to make this easier, it is actually a multiple of smaller layouts that I merge in as I go. The problem I am having, however, is that when I add any of the smaller layouts into the larger one, the smaller one always show up at the same spot, which means I need to move it to where it belongs. I do know how to do that, however, it's becoming more and more tedious to do that, as the destination point is further and further away from where it shows up.

Does anyone know if there's any way to change where it shows up?

thanks!

realm

This has always been the case. I tried changing the world origin on the layout to be imported, hoping that the layout would line up to the new place, and save the scroll around the map thing, but that didn't work.

I don't know if this can be changed.

John
 
I don't think it's the World Origin. I would rather guess it's the internal baseboard coordinate system. The first baseboard in a route is always indexed (0,0).
 
I noticed the same thing when I first started creating and merging routes. Now, if I want to create route B to merge with route A, I first start with route A, add one baseboard where I want route B to merge with route A. After that I rename it to what I want route B to be called and then delete all of the baseboards from route A. If you do it this way, then route B will show up and merge in the right place. This process can get very tedious on a large route, but it's the only way that I've been able to figure out to do it.
Mike
 
I don't think it's the World Origin. I would rather guess it's the internal baseboard coordinate system. The first baseboard in a route is always indexed (0,0).

It would make sense, as this was the first baseboard created for that route. I had an idea tho.. instead of merging route B into route A, I should do it the other way around and see what happens... B is evidently much smaller than A, so I should have less clicking to do to get it in the right spot :)

realm
 
I noticed the same thing when I first started creating and merging routes. Now, if I want to create route B to merge with route A, I first start with route A, add one baseboard where I want route B to merge with route A. After that I rename it to what I want route B to be called and then delete all of the baseboards from route A. If you do it this way, then route B will show up and merge in the right place. This process can get very tedious on a large route, but it's the only way that I've been able to figure out to do it.

Mike, I think I sorta understand what you're saying. The layouts I'm adding are typically 5-10 boards big, maybe as large as 20 at times. The one I'm merging to has well over 300 boards by now.

That's ok tho, I think I'm pretty much done merging. I got all the tracks fixed (TransDEM did an awesome job at laying tracks down BTW, I just had to do some minor adjustments here and there). I'm now working on all the creeks and rivers, then I'll start getting into the fun stuff :)
 
Back
Top