Red signal, OR states no signal in path.

[Claude350]

You're welcome. I'm gonna try the signal reset controls. I'm having issues with the Shuswap Sub when using Open Rails. The signals are not clearing as they should. At times I have to stop at an absolute signal to get it to change to clear. I also encounter permissive signals that are showing restricting and there is no opposing traffic.

[prr4ever]

red signals

I sometimes get the same permissive showing restrictive with no opposing traffic. But, I figure that is the real world for you, could be a train on the block ahead of you (even though in the sim you know there is not). That would be in the days of no radios and dispatch by telegraph!

[Claude350]

I sometimes get the same permissive showing restrictive with no opposing traffic. But, I figure that is the real world for you, could be a train on the block ahead of you (even though in the sim you know there is not). That would be in the days of no radios and dispatch by telegraph!

Yep. It makes me wonder if the signal logic from MSTS is clashing with the signal logic from Open Rails.

[Claude350]

Claude you sure had me fooled, I thought you were posting about the Reset commands when you used the phrase "control tab".
(that it was a web typo not including the + sign)

Yes that was a typo on my part.

[tanglingwolf]

May I add to this? Upon starting an explore session and being stuck in auto mode, I am faced with a yellow followed by a red. I cannot clear/reset the aspects because there is "no signal" in my path, the dispatcher says no, and passing the yellow triggers the e-stop. Oh, and this only happens heading in one direction.

[Vince]

So first, why do I get a message no signal in path, then get an emergency release when I pass that signal that is not there but really is there? Why can I not pump the brakes back up and release them?

You have I believe encountered a 'Phantom Signal.This is a signal that exists in the Track Database (TDB) but not in the world and Track Item Table (TIT).
The signal will be invisible in the world but will be seen in the F4 Track Monitor.
This 'phantom' can be eliminated but it's a tedious process:
Basically to find the signal in the database you need to generate a small test activity running past that signal. Before saving the test activity, in the AE if you select that signal to mark it 'FAILED' it will add a failed signal entry to the activity (act) file. (down towards the end of the file). This adds a FailedSignal line to the last lines in the activity file ( test.act ), the small activity you just generated.

From the information in this line which will have the UId and the signal ID in it, you can manually remove the signal information from the database files (one way) or the signal information block can be added to the world and tit files. THEN, the signal shape can be selected in the Route Editor and deleted.
This last is the method I used on the PRR East to eliminate the three phantom signals at NB main 1 mile north Perryville , Trenton (SB main at station) and the last near the West Baltimore on the #2 track when running left side running south.
Pretty much a pain-in-the-butt to do but it does work.
regards.

[prr4ever]

hantom signal

You have I believe encountered a 'Phantom Signal.This is a signal that exists in the Track Database (TDB) but not in the world and Track Item Table (TIT).
The signal will be invisible in the world but will be seen in the F4 Track Monitor.
This 'phantom' can be eliminated but it's a tedious process:
Basically to find the signal in the database you need to generate a small a activity running past that signal. In the AE if you select that signal to mark it 'FAILED'.
This adds a FailedSignal line to the last lines in the small activity you generated. From the information in this line which will have the UId and the signal ID in it you can manually remove the signal information from the database files (one way) or the signal information block can be added to the world and tit files. THEN, the signal shape can be selected in the Route Editor and deleted.
This last is the method I used on the PRR East to eliminate the three phantom signals at NB main 1 mile north Perryville , Trenton (SB main at station) and the last near the West Baltimore on the #2 track when running left side running south.
Pretty much a pain-in-the-butt to do but it does work.
regards.

Thanks Vince,
Since it does not effect ops at all I will simply leave it alone. I can get past any signals in manual mode anyway, as long as no opposing traffic is present. Interesting explaination though..

[prr4ever]

Phantom signal

I should add here, after going back and reading my original post again, that a good part of the original problem was my not yet fully understanding OR. Since then by using OR a lot more I am currently running fine. What I believe was happening when I originally posted this was I was "forgetting" to hit SHIFT+TAB to clear a signal behind me. I was quite probably simply hitting TAB in manual mode which clears signals forward only.
Thanks for all the replies when, quite probably, the problem was only betweeen the ears.

Dave

[Vince]

Hi Dave,
It's helpful to print out all the OR keyboard commands, highlighting the one you use the most.
regards,

[prr4ever]

No signal in path

Hi Vince,
Did that after I got more comfortable with OR and I have found several oppurtunities to add to it along with some highlighted notes of my own. Kind of a check list or reminder. Like they say "a work in progress" and a great one at that!

[woodfyr]

I have had most of same problems mentioned in this thread. Not being one to jump into the forum with questions, I tend to attempt to solve issues through the trial and error method. Then I discovered the Dispatcher Window in OR. What a tool ! It helps to have a dual monitor setup. Playing in what I call "Dispatcher Mode" allows you to see what is going on with both player and A1 trains. And now with train control (ALT F9) the ability to manipulate actions and or events within an activity becomes available.






)

[OTTODAD]

I have had most of same problems mentioned in this thread. Not being one to jump into the forum with questions, I tend to attempt to solve issues through the trial and error method. Then I discovered the Dispatcher Window in OR. What a tool ! It helps to have a dual monitor setup. Playing in what I call "Dispatcher Mode" allows you to see what is going on with both player and A1 trains. And now with train control (ALT F9) the ability to manipulate actions and or events within an activity becomes available.

Yes, it is a great improvement over MSTSBin, but has one downside, video recording software like Bandicam can not see its window, it overlaying the main window or running on a second monitor, I have not tried jet, having a 24" Dell and a 22" Iiyama monitor using a GTX 560 Ti which does support it.