Path looks right, but keeps showing error

[RonKStevens]

I am developing a scenario for the NEC. Having a problem I'm not sure how to correct.

I am bringing the player-driver engine out of Race Street yard, to a scenario marker reverse point, and then backing up to Philadelphia 30th Street LL track to hook up to cars.
The reverse marker is showing DIRECTLY in the path of the engine, and is not on a switch. When I add the stop point, I get the (!!!) error saying it can not route a path to the reverse point.
I never did a scenario before that had shunting in before, so I'm not sure what I may be doing wrong.
Thanks for your help

[OldProf]

I am developing a scenario for the NEC. Having a problem I'm not sure how to correct.

I am bringing the player-driver engine out of Race Street yard, to a scenario marker reverse point, and then backing up to Philadelphia 30th Street LL track to hook up to cars.
The reverse marker is showing DIRECTLY in the path of the engine, and is not on a switch. When I add the stop point, I get the (!!!) error saying it can not route a path to the reverse point.
I never did a scenario before that had shunting in before, so I'm not sure what I may be doing wrong.
Thanks for your help

Several questions come to mind:
1) Is the "scenario marker reverse point" a marker you have added or one included in the route and what kind of marker is it (siding, destination, etc.)?
2) The "!!!" error usually comes with a white X in a red circle. Clicking that circle reveals an error message. Have you looked at that message? What does it say?

And a couple of suggestions:
1) Quite often, path errors like the one you describe prove to be bogus when the scenario runs. If you haven't done so already, try running the scenario despite the error and see whether it works.
2) I've also resolved similar situations by letting the "dispatcher" find a path. In other words, take out the Drive To instruction, leaving only the Add to Front or Back instruction and see whether a path appears for it. Often, the path chosen by the "dispatcher" will not match that planned by the scenario writer.

Let me know what happens? I'll try to remember to look for this thread.

[artimrj]

This started happening a few updates ago. You get a reverse error, bi directional passing error and something else. I figured out to save the scenario, close it and reopen it and it is usually good. If you come back in and it is still broke then you have somethng really wrong. The scenario writers at the NERW were having this problem and they started doing what I said and it works. But like I say, if it doesn't work you have another problem somewhere else on the path.