Crash after merge possible cause

[stagecoach]

I recently had two working routes Module A and Module B. These where both set up with the session layer merged into the route layer. Both routes operated fine so I thought about putting them both together. I created a blank baseboard as a bridging section. I merged Module A and it was fine, I then merged Module B, all seemed fine again so saved and exited. Went back to the new merged route and started to look around, CRASH and exit game. I went back in and looked at the find object window and started to scroll down the list and found that many items had been doubled up because each route had the same name/number. I used a steam engine 1 in module A and also in Module B as they where different routes. In the merged route I have two steam engine 1's instead of steam engine 1 and steam engine 2, Likewise for ATLS, Signals etc. This must cause script errors which would lead to the crash. Any thoughts from those with knowledge of how trainz works.

 

[blueodessey]

Things to do before Merging a Route(S) Etc

Ok.....If Understood what you said correctly, you have duplication's on the Routes,,,,,

So first course of action:

Route Layer on one, other Route1 Layer named, there has to be Uniqueness across the board........It looks like that is Ok

Next before merging, make sure you have a copy and original.....

Use Copy to play and Merge, always maintain original, I can't stress this enough......




Next NO consists, of any type on either Route,,,,Never, Never.....I know it is a pain, but I have learned the hard way over years of anguish.....

Next check your Signals, Switches and Area Names, they need to have unique numbers or names....Just take the second Model, and put a 1in front of the names, that'll make it unique to other route.

Make sure you have no missing Assets on either Route, Pure no errors is key here.....

Now make sure, you are in Airplane Mode while you do your merge, I have Carbonite backup and Email, yada yada just like other folks....You want only trainz running, that means if possible, since your in Airplane mode, shut off Virus protection too, if possible, all this stuff going on, can corrupt a file operation, merge etc in Trainz....Been there, done that.....

Now merge your extra Tile,,,,,,,

Now here is what most people fail to due, they don't don't save a copy of this Merge, they continue on working with merged copy....And then save....

Don't do that, you merge, you save, exit Surveyor for a few seconds, then reopen the first merge file, look it over carefully see if anything is wrong????

Now you bring in Module B and merge, wash rinse and repeat the steps......

You should be OK now,

Re add your Rolling Stock etc, connect your Track.....I just throw in a quick Track between the new modules, to see how things run......Doesn't matter if it is hanging in the air etc, quick and dirty is the name of game when checking to see that your basic functions are working between the newly merged Routes.......

Also go into to your FIND OBJECT option, pan thru industries and Switches Signals etc, see how the names look, see if everything is there.......You rename stuff later, you just want to see if things are basically in order.....And believe me, using Find Object is one of the best friends you'll ever have trying to find things quickly, doing naming conventions and the like....

And of course your Content Manager......

I wish you good luck here and hope my notes will solve the issue at hand.........

Good Day Sir......

 

[Christopher824]

So I am with blueoddessey here 100%. After much experimentation, here is how I find a 100% success rate merging Routes.

No Consists, you can add them back to a Session after you merge the Routes

All Switches and Junction have unique names. To do this I have a spreadsheet and I give my Routes a 2 digit prefix. Then I go an renumber every switch and signal using the 2 digit prefix and a 4 digit sequential number, ie Junction 140001 Junction 140002 Junction 140003 - Signal 140001 Signal 140002 Signal 140003. My ATLS Crossings I go with Channel 1401 and then name everything with that number ie... ATLS Controller 1401, ATLS Signal 1401 N, Signal 1401 S. Same idea with the ASB Crossovers. (Channel numbers can be typed in manually, you don't need to press the plus button that many times)

My current method gives me 99 unique Routes that can be merged, if I ever go past that ill go to 100's for the prefix and 4 numbers index after that, that will give me 999 Routes, and could jump up one more number again and again.. Either way it keeps all these little critters inline when you try to drive the AI, and keeps the desktop crashes away when merging.

And then the final caveat. Save and exit completely after each Merge, don't do 2 at once, it may work sometimes, but for me rarely ever.

 

[blueodessey]

I breath Excel Spreadsheet

:wave: Hello Christopher824,

You know I grew up with Excel, and that is a terrific idea for renaming the asset names, granted it will take me a while, but when using Add-on's like ATLS and who knows what else is coming down the pike in later years, that makes logic, and perfect sense........

Thanks for the tip.......