Unchangeing Red signals

[125900]

Has anyone else had this problem? You come accross a red signal in a scenario that has no reason to be set at red. ie no train in the section ahead or junctions set incorrectly. This happens constantly on a scenario from Armstrong Powerhouse. AP7 1N09. A red light a few miles out of york and then again at Darlington. The only fix I know is to save the scenario then continue, which ruins the timings and any chance of completing the scenario properly. I also get this on a scenario going into Glasgow Central. If anyone knows a fix for this I'd be very greatful as it is getting really annoying now. I've tried reinstalling the pack like AP suggests and clearing the blueprints but nothing seems to work.
Stephen

[USRailFan]

This is sometimes a problem on Bath - Templecombe and Hedborough North as well, with the only solution being the same - save and then reload after completely quitting Railworks. Might possibly be a memory/resources issue? Try reporting it to RS.com anyway (haven't gotten around to doing so myself).

[stuart666]

If you havent already, try pressing tab (the equivilent of calling up the signalman and asking whats wrong), and if it says proceed as normal do so, and the next signal will probably be ok.

Ive found on my route that im building that if semaphore are too close together, and the consist behind your locomotive is too long to fit in the section, the signal in front of you will sometimes not clear before the rear of you train passes the previous semaphore. Ive a suspicion the same can sometimes apply to red signals as well.

Just treat it as a simulation of a failed signal. It happens in the real world too....

[LoneWolfDon]

Yes, sometimes it doesn't really make any sense why a signal may be red. I think some of the routes and scenario "pathing" is sometimes a bit buggy that could be causing such problems.
I've been making up a scenario-pack for RailWorks recently, and several times I've encountered this problem... nothing ahead blocking the Player's-train path, and all junctions appear to be set correctly.
Though usually pressing the Tab key when this happens will give approval to pass.

If not (in some cases pressing Tab key did noting), sometimes you have to look way ahead of the Player's-train path, as there could be some junction way up the line that's opposing the path causing the conflict.

[125900]

Found a kind of fix for the problem. Removing both of the AI trains which travel north ahead of the players train enables the signal to operate properly.

[smarty2]

Yes, this has been a bug since RS days! Perhaps this core update (whenever that comes?) will fix it?