Bukkit

What steps will reproduce the problem?
On my server places have a destination sign and trains are supposed to find there way like that, with only switchers in between.
1.Use elevator sign on unconnected pieces of track.(What else is the point)
                         elevator------------END (destination)
                          BLOCKS
                          BLOCKS
START------+-------elevator
                |
                |
             REST OF TRACK
2. Having a destination set on lower level (or visa versa)
3. Having the destination at lower level (or visa versa

What is the expected output? What do you see instead?

You would expect the train to find it's destination. It just keeps driving around on the lower/upper levels, unless ofc it has no other option or running ahead makes it hit the elevator by chance after which it does function normally if it's on a track directly connected to the destination.

What version of the product are you using?

Most recent build. (problem was present in stable 1.6.4 builds also, didn't use the plugin before that.)

Do you have an error log of what happened?

No

Please provide any additional information below.

Same thing: START-+--ELEVATOR ELEVATOR-+-END
                             |                                        |
                            Alternative track 4 times as long but fully connected
Train will take the long way around...

From what I understand, the routing system follows continuous tracks, ignoring signs such as elevator. I wouldn't say this is a defect, it could be awkward to implement.

You could place a destination sign before your elevator which sets a new destination to reach after the elevator.

[+train]
destination
beforeElev
afterElev

@andrewvpo: Go Correct answer indeed. I can 'maybe' implement it, but the problem is, then I have to pretend that the elevator is always activated (it needs redstone to do anything at all) AND then I need to add some sort of 'onDestinationProcess' in all sign systems as it should be something not that much hardcoded into it. The blocker signs were already pushing it, I'm afraid implementing teleportation signs with this is going to cause some headaches in the long run...

But I'll leave it open for the time being.