Diverging signals work differently on added track and tiles

[Literalman]

I extended the Blue Comet Lines by adding a lot of new world tiles with track, roads, and scenery but no interactives and no dynamic track, built as a separate route but then with the world and tiles copied into the original route. I went through the new areas and clicked on each track and road piece, and the vectors then showed up. I added speed limits, car spawners, crossing gates, platforms, and sidings. I visited all the new areas using Explore Route, noting and fixing problems. Finally I added signals and started creating activities, and when I started testing the first activities, I found that diverging signals would display red, and I could pass them by using the tab key and then I would have a 15 mph speed limit until the next clear signal. The one-head signals seem to be working OK. The same problem occurs in Open Rails, and Route Riter revealed no problems.

I went through the new parts of the route and made sure all diverging signals were properly linked, but the problem persists. The extension was created using the same signals, scripts, and configurations (mostly by Hank S.) from the original route. The route folder contains the script and configuration files dated 2011.

In the original parts of the route (from 2012), the diverging signals seem to be working correctly. I even tried adding a few new ones, and they worked correctly too.

I tried deleting a diverging signal in a new part of the route, clicking on the switch and on the track section where the signal was, then placing the signal again, but the same problem exists. (I back up my work daily, so if that had caused a catastrophe I could have gone back to the previous day's version.)

It appears that something in all the added tiles is causing the diverging signals to behave differently than in the original parts of the route. If so, what could it be?

Thanks for any help you can give.

[Vince]

A couple of thoughts:
Did setting the signal links go okay?
Distance from red tripper to switch red pole should be >1m.

[Literalman]

Yes, and I went through the new areas making sure that under "properties" all the diverging signals had the message saying that the signal head links were set up properly. And they direct the train to the proper path, but with red instead of green.

I was careful to make sure that the red pyramids weren't too close to the red poles, but it's possible that I missed one or more. I will check again. It seems that something in the new tiles is making the scripts behave differently or is interpreting the scripts differently.

Thanks, Vince. If I figure it out, I will post an answer for the benefit of others. In 21 years of route building, including one extension using the same methods, I've never seen this, but the possibilities for computer problems are endless!

[Vince]

Steve,
One other thing I forgot to mention.
TSRE has an error checker and repair routine accessed on the Tools menu.

A line needs to be added to the TSRE Settings.txt file as follows: loadAllWFiles = true
Place a '#' in front of the added line to shut it off when not needed like this: #loadAllWFiles = true

I didn't use the auto repair function as I decided that was too easy (to screw up) and opted to jump to each location called out in the error report and fix them manually.
vin

[Literalman]

It was a user problem. I'm ready for the glue factory! "Signal Head 1 Main Route" and "Signal Head 2 Diverging" were grayed out, so I thought I had to choose one of the other options: "Head 1 Fixed Red" and "Head 2 Fixed Red." I did and got—guess what? fixed red. All I had to click was "Link Heads." Nothing to see here. Move along. ;-)