Route Editor Track Properties Spacebar Scroll

[xguerra]

This is a question you'd expect I would have asked a long time ago, but never had a need to look into this until now.

You know when you're in the route editor and you press spacebar to change the track to coloured pathways which represent different track properties, is there a list of what all the different colours represent?

You see I am trying to make some scenarios for my NLL route, yet I am having issues where the AI or the player train won't work between Stratford and North Woolwich. Yet, QuickDrive works absolutely fine.
I've gone over the track with the selector tool to see if it's a directionality issue but so far found no issues. All the track is bi-directional.

So I want to see if there's any other factor involved that's stopping them from working.

Thank you!

[malkymackay]

The three properties that are liable to stop services pathing in a normal scenario are Line Type, Directionality and Electrification. http://forums.uktrainsim.com/viewtopic. ... 6&t=105209 will at least give you some assistance with the colour coding of the Line Type, which is the first press of the space bar. If the track has all been laid as Bidirectional, then that's fine. The electrification type is on the 5th space bar press and IIRC, black with a crossed out white OHLE symbol is non-electric track and white with a black OHLE symbol is Overhead electrification. Can't remember what 3rd rail is off the top of my head.

[gptech]

white with a black OHLE symbol is Overhead electrification. Can't remember what 3rd rail is off the top of my head.

It's not really an OHLE symbol as such, rather a 'High Voltage' warning flash which simply denotes the track is electrically enabled--3rd rail track is yellow with the symbol and 4th rail is red.
Once track is thus enabled you should be able to route any electric train over it, regardless of whether the train is AC or DC---you can have hours of fun driving a class 87 on the Brighton mainline if you wish!!

[xguerra]

Thank you both for your help!!

Changing the consist type seems to have solved the issue. At least it means I don't have to patch the route again. Thank you!

[malkymackay]

If the issue has been solved by changing the consist type, then that would lead me to suspect you have a section of track that wouldn't allow the consist type you were trying to use originally. Using a track rule where the line type has to be set to passenger or freight to get the desired radius of curvature and then forgetting to go back and change it to mainline, for example, would be my guess on the issue. Done that a fair few times myself. The other one is setting the properties for a crossover and then not going back and changing the values for the mainlines...
At least you can change the properties in the scenario editor now, so you could use the originally planned consist type, if that is needed.

[xguerra]

If the issue has been solved by changing the consist type, then that would lead me to suspect you have a section of track that wouldn't allow the consist type you were trying to use originally. Using a track rule where the line type has to be set to passenger or freight to get the desired radius of curvature and then forgetting to go back and change it to mainline, for example, would be my guess on the issue. Done that a fair few times myself. The other one is setting the properties for a crossover and then not going back and changing the values for the mainlines...
At least you can change the properties in the scenario editor now, so you could use the originally planned consist type, if that is needed.

The fool-proof solution indeed would be to go over and change the line types but it would mean I'd have to patch the route again for users to play the scenarios.
And since QuickDrive worked anyway I'm not too bothered at this present time.

[malkymackay]

No real need to patch the route. The track properties can be changed in the scenario editor for the particular scenario you are authoring. They don't alter the core route files and won't affect any other scenarios. Very useful for adding in things like Temporary Speed Restrictions, without the need for them to be present in every single scenario on a route.