Merging routes with locked layers will cause an immediate CTD.
I was able to repro this one, the hard way, a couple times. This doesn't matter if this is the main route or the merge candidate.
If there are separate layers, they can be combined and moved in the merge-route interface as if there's nothing wrong, but as soon as the merging process takes place it's an instant CTD.
After running a test merge between two test-routes showed everything worked fine, I then checked the differences. Outside of the size, which really wasn't a lot, the main difference was the layers being locked. After unlocking those layers, everything worked fine.
Going forward. the route-merging process should be to check layers and unlock them. In reality, there should be a warning box on the merge-route interface with the interface locked to not allow the merging to take place unless the layers on the route(s) have been unlocked first.
I was able to repro this one, the hard way, a couple times. This doesn't matter if this is the main route or the merge candidate.
If there are separate layers, they can be combined and moved in the merge-route interface as if there's nothing wrong, but as soon as the merging process takes place it's an instant CTD.
After running a test merge between two test-routes showed everything worked fine, I then checked the differences. Outside of the size, which really wasn't a lot, the main difference was the layers being locked. After unlocking those layers, everything worked fine.
Going forward. the route-merging process should be to check layers and unlock them. In reality, there should be a warning box on the merge-route interface with the interface locked to not allow the merging to take place unless the layers on the route(s) have been unlocked first.