NIMBY Rails Wiki - User contributions [en]

How to signal a junction

2024-10-29T21:31:58Z

Schatty: started writing the guide

This is a guide to safely signal junctions in the game.

== Simple Junctions ==
There are two very basic rules that you can follow, that will make signalling your junction very easy and protect these from train crashes:
# Place a path signal at the entrance of a junction, in front of the branch (exceptions will follow)
# Place a balise at the exit of a junction

The order is WP

===1. Branching line===
If you have a junction that looks the following: 
'''>>picture to be added<<''' 

You want to first place the path signals at the entrances of the junction: (place them a little bit in front of the branching point, as trains have an additional 30m hitbox in front of them) 
'''>>picture to be added<<''' 

Then you want to place the balises at the exits of the junction: (you can place the balise directly after the junction, but it would be better to place it at least one train length after the junction) 
'''>>picture to be added<<''' 
Special case: a single tracked branch line

=== 2. Scissors ? (unsure if It's own point)===

=== 3. Stations ===

=== 4. Diamond Crossing ===

Track

2024-09-30T17:02:09Z

Schatty: /* Branch track */

{{Concepts sidebar}}
Track objects (also called track segments) model the railways over which trains can move. The consist of a single control point, and are always linked to one or two other tracks (the previous and next sibling). Tracks can also be attached to tracks in two other ways: as a [[branch]] or as a [[parallel]] track. Tracks can contain [[signal]]s.

=== Normal track ===
A normal track, with default settings, has the following properties you can edit:
* Promote track into platform
* Node mode: [[Point mode]] and [[Tangent mode]]
* Tangent track shape
* Custom max speed
* Reset boundary to middle point
* Lock to control point: Pick parent

=== Parallel/parented track ===
A track that is parented to another track. You can still edit almost every function of the track
There are two parenting modes, lock control point: 

'''to a control point:''' 
The track is parented to the other control point and an offset from 0m - 1000m can be assigned. The track can also be flipped to the other side by either pressing the flip button or [F].

'''to a track point:''' 
The track is parented to a point on the track. The point can be defined by the segment t value (0 to 1). The displace value allows you to set an offset in the pendicular direction of the normal offset from -1000m to 1000m.

=== Branch track ===
A branch can be created by simply hovering over another track (it should snap to the track and a branch icon should appear) and building like a normal track.
It is not possible to create a branch on a platform segment and to make it an platform itself. The texture of the branch can be different that the one of the main track (can be defined by the creator of the tracks).

Distance category

2024-09-30T16:43:01Z

Schatty: feature got deleted

<big>'''Deleted feature'''</big>

''NIMBY Rails [[pax]] are allocated to three [[distance category|distance categories]] upon spawning: local, regional and long distance.
*Local: destination 0 to 15km from origin
*Regional: destination 15km to 100km from origin
*Long distance: destination more than 100km from origin
Distance categories are used for how pax pick their [[destination]].

Indirectly, distance categories can be a driver of advanced issues and problems in a network because of the hard cut-off distances.
For example, if your entire network is in a single metropolitan area (within a 100km radius) except for one station outside, all long distance pax will pick that one station as their destination.''

[[Category:Concepts]]

Track

2024-09-29T22:18:10Z

Schatty:

{{Concepts sidebar}}
Track objects (also called track segments) model the railways over which trains can move. The consist of a single control point, and are always linked to one or two other tracks (the previous and next sibling). Tracks can also be attached to tracks in two other ways: as a [[branch]] or as a [[parallel]] track. Tracks can contain [[signal]]s.

=== Normal track ===
A normal track, with default settings, has the following properties you can edit:
* Promote track into platform
* Node mode: [[Point mode]] and [[Tangent mode]]
* Tangent track shape
* Custom max speed
* Reset boundary to middle point
* Lock to control point: Pick parent

=== Parrallel/parented track ===
A track that is parented to another track. You can still edit almost every function of the track
There are two parenting modes, lock control point: 

'''to a control point:''' 
The track is parented to the other control point and an offset from 0m -1000m can be assigned. The track can also be flipped to the other side by either pressing the flip button or [F].

'''to a track point:''' 
The track is parented to a point on the track. The point can be defined by the segment t value (0 to 1). The displace value allows you to set an offset in the pendicular direction of the normal offset from -1000m to 1000m.

=== Branch track ===

Point mode

2024-09-29T22:14:56Z

Schatty:

An additional track mode that changes how the tracks are drawn. Only accessible trough the track editing menu.

[[Category:Concepts]]

Tangent mode

2024-09-29T22:14:51Z

Schatty:

The default track mode.

[[Category:Concepts]]

Point mode

2024-09-29T22:14:28Z

Schatty: Point mode

An additional track mode that changes how the tracks are drawn. Only accessible trough the track editing menu.

Tangent mode

2024-09-29T22:13:39Z

Schatty: Tangent mode

The default track mode.

Point of Interest

2024-09-29T21:48:50Z

Schatty:

Point of Interests (POI) are points on the map that have an population and a demand curve assigned, to simulate additional pax demand. Examples of POIs are Airports, Offices or recreational spaces.

[[Category:Concepts]]

Demand Curve

2024-09-29T21:48:32Z

Schatty:

The demand curve shows and lets you edit the demand of your population. There exists a default one (can be edited) that will be used for the population and the possibility for the player to create custom ones.
== Demand curve editor ==

[[Category:Concepts]]

NIMBY:Contents

2024-09-29T21:47:08Z

Schatty: /* Versions */

= Guides =
== Tutorials ==
All tutorial pages start with "How to" and contain a step by step guide to a simple game concept.
Following the tutorial pages should enable you to build and run a simple network.

*[[Quickstart guide]]
*[[How to build track]]
*[[How to build stations]]
*[[How to create a line]]
*[[How to schedule a train]]

== Advanced ==
Advanced guides enable players to use optional functionality such as signals and depots which can be ignored and replaced with defaults if needed.
*[[How to signal a junction]]
*[[How to use depots]]
*[[How to manual timetable]]
*[[How to use the in-game routeplanner]]
*[[How to have multiple trains share a platform]]

== Strategy ==
Strategy pages assume you know ''how'' something is done and consider ''why'' you might want to do it.
*[[Depot strategies]]
*[[Mapping resources]]
*[[Transfer hub strategy]]

= Concepts =

== [[Geographical layer]]s ==
''Geographical background objects provided by the game data which cannot be modified by the player''
*[[Population layer]]
*[[Admin layer]]

== Map concepts ==
''Objects created by the player on top of the geographical data''
*[[Blueprint]]
*[[Track]]
*[[Station]]
*[[Signal]]
*[[Layer]]s
*[[Building]]
*[[Point of Interest]]

== Simulation concepts ==
''Things that the game generates as it runs the simulation''
*[[Pax]]
*[[Dominating trip]]
*[[Path]]
*[[Accounting]]
*[[Satisfaction]]
*[[Demand Curve]]

== Line concepts ==
*[[Line]]
*[[Stop]]
*[[Timetable]]
*[[Duration]]
*[[Custom Duration]]

== Train concepts ==
*[[Train]]
*[[Run]]
*[[Order]]
*[[Timetable]]

= Versions =
*[[Demo 1.0]]
*[[Version 1.1]]
*[[Version 1.2]]
*[[Version 1.3]]
*[[Version 1.4]]
*[[Version 1.5]]
*[[Version 1.6]]
*[[Version 1.8]]
*[[Version 1.9]]
*[[Version 1.10]]
*[[Version 1.11]]
*[[Version 1.12]]
*[[Version 1.13]]
*[[Version 1.14]]

Demand Curve

2024-09-29T21:45:48Z

Schatty: /* Demand curve editor */

NIMBY:Contents

2024-09-29T21:37:56Z

Schatty: Added: POI and Demand Curve

Demand Curve

2024-09-29T21:35:51Z

Schatty:

Point if Interest

2024-09-29T21:32:00Z

Schatty: Schatty moved page Point if Interest to Point of Interest

#REDIRECT [[Point of Interest]]

Point of Interest

2024-09-29T21:32:00Z

Schatty: Schatty moved page Point if Interest to Point of Interest

Point of Interests (POI) are points on the map that have an population and a demand curve assigned, to simulate additional pax demand. Examples of POIs are Airports, Offices or recreational spaces.

Demand Curve

2024-09-29T21:30:40Z

Schatty: Created page with "The demand curve shows and lets you edit the demand of your population. There exists a default one (can be edited) that will be used for the population and the possibility for the player to create custom ones."

Point of Interest

2024-09-29T21:22:35Z

Schatty: Created page with "Point of Interests (POI) are points on the map that have an population and a demand curve assigned, to simulate additional pax demand. Examples of POIs are Airports, Offices or recreational spaces."

Point of Interests (POI) are points on the map that have an population and a demand curve assigned, to simulate additional pax demand. Examples of POIs are Airports, Offices or recreational spaces.

Station

2024-09-29T20:31:54Z

Schatty:

{{Concepts sidebar}}
A station is a set of one or more [[platform]]s whose footprints overlap on each other (in particular, a single platform is a valid station too). Stations are the main destination kind available for picking as a [[line]] [[stop]] (the other being [[waypoint]]s). [[Pax]] [[Spawn rate|spawn]] at stations, travelling from their [[Origin|origin station]] to a [[Destination|destination station]].

There are no limits on how many platforms can be combined into an station, including overlapping them at any [[layer]] or aligned in any orientation.

== Passengers ==

Passengers (called [[Pax]] ingame) have an origin station and a destination station, on their way between these two stations pax can transfer in stations, but also do Out-of-Station Interchanges (walking).

'''Out-of-Station Interchanges (OSI) '''
The max radius at which an OSI is possible is 2.3km. There are two ways to achieve such a link between two stations: Either by using the auto walk transfer range of the station or by using the create walk link function [not assigned] in the station building tool. The transfer between two stations via walking takes time, because the pax are walking at a speed of 1m/s. While the pax are walking they appear in the station hall of their destination (of the OSI) with a timer.

== Station properties ==
[[File:Station properties 1.14.png|thumb|Station properties]]
The station properties window is used in the [[Track|Tracks menu]] to edit the station's properties, including:
*The station name
*The station label display settings
*The station coverage area (affecting the reach of the station, and hence the [[spawn rate]] of passengers)
*The auto walk transfer range (this is the range in which the station will automatically create a walking link between stations)
*The platforms pax capacity (a slider for the capacity of the station from 50 pax to 100,000 pax)
*The checkbox to allow Transfer pax overflow into the Station Hall
The station properties window also has a locator button (next to the "Done" button) to jump to the location of the station.

=== Station names ===
There are two options for the station name:
*Automatic naming: Is enabled by default and has to be disabled manually. There is a button with which you can switch between multiple auto-generated names.
*Manual naming: Is activated by unchecking the box for automatic naming under the name. You can then enter your own name.

==== Using station names as tags ====
As of [[Version 1.5]], NIMBY rails does not support station tags. An advanced strategy is to use the station name as a kind of station tag system, which can help in understanding certain menus that do not support tagged listings, as well as the [[Accounting export]]. For example, starting the station name with the stations [https://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Units_for_Statistics|NUTS] regional code can make it easier to do regional aggregations on the accounting export.

== Station window ==
[[File:Station_window.png|400px|thumb|right|Station window]]
=== Passengers ===
Passengers can be show in
*Show all
*Show best current trip. This functions as an "in game routeplanner" for the current time.
*Show dominating trips. This functions as an "in game routeplanner" across time.
*Group by destination
*Group by origin
*Group by waited line stop
*Group by next stop

=== Platforms ===
A platform is a special piece of track which a train can use for loading/unloading passengers.

=== Accounting ===
Stations have their own [[Accounting]] window, showing the accounting events that occurred at this station.

== Stations as depots ==
[[Depot|Depots]] are technically just stations that are used for a particular purpose, storing trains for longer periods of time. Depots do not require any kind of special building to function.
*The station coverage area can be set to zero. This prevents pax from spawning or choosing the depot as a destination.
*The station label display settings can be made less prominent.

[[Category:Concepts]]

Stop

2024-09-29T20:18:13Z

Schatty: station assignement

{{Concepts sidebar}}
A [[line]] stop is a point in the map for [[train]]s to stop (or pass by) while running a line. Stops are always defined as two [[track]]s, be it a [[station]] [[platform]] or a [[waypoint]]. Stops have other associated data like leg duration or stop wait time.
== Stop assignment ==
There are two different modes to assign a stop to a line:
=== Basic mode ===
The default mode. You can only assign the end segments of the platform, the position of the train is automatically adjusted. If you press Alt, you can assign platforms that were not otherwise selectable without pressing it or you can select a platform again.
=== Advanced mode ===
Lets you assign any point on a track as a stop on a line, if it is on a station section it creates a stop and if it is on normal tracks it creates a waypoint. The nose of the train will stop at the assigned point, the length of the reference train of the line will be displayed with a thick stripe the length of the train.
== Stop settings ==

Line

2024-09-29T20:01:25Z

Schatty: /* Accounting */

{{Concepts sidebar}}
A line is a sequence of one or more [[stop]]s, and some associated data like fares and line [[duration]]. [[Train]]s can follow lines by setting them in auto mode or by creating [[order]]s.
= Line overview =
The Line overview is a list of all lines. The way the lines are sorted and displayed can be changed at the top. The map icon only shows all lines that are currently visible on the map.
The second button opens a menu with the following grouping options:
*Group by: All lines (shows all lines)
*Group by: Tags (shows all lines in the way your tags are build up and assigned)
*Group by: Untagged (shows all lines that have no tags)
There are also options to exclude lines from being displayed in the overview:
*Closed
*Technical
*Open
*With warnings
Additionally there is also a option to make the lines more compact. 

At the bottom are six buttons that are from left to right:
*Create a new line
*Create a new depot line (creates a new line, which is already set to technical maneuvers)
*Clone selected line
*Issue an intervention to all trains currently running the selected line
*Delete selected line
*Pan and zoom view when selecting a line or station

= Line Settings =
You can access the line settings by selecting a line. A window to the right of the line overview will appear.
== Stops ==
The stops tab gives you access to the basic line settings and have an overview of the stops assigned to the line and their settings.
=== Basics ===
* Name (the name of the name of the line)
* Code (the line code, which is displayed in several places instead of the line name, e.g. on the train icon, the platform overview, ...)
* Base ticket price (price that will be payed once by pax for boarding the train)
* Price per km (price that will be payed by pax for every driven km, will be added to the base ticket price)
* Color (color that will be used on the map and the line overview)
* Display on Map
* Service level
=== Tags ===
Expands a field where you can assign tags to the line, which will then be assigned to trains as they service the line.
=== Default timings ===
* Reference train
* Cruise speed (km/h) (By default set to 90% of the maximum speed of the reference train, can be changed to a manual cruise speed. Trains can run faster than the cruise speed to make up for delays.)
* Max. acceleration (m/s-2)
* Max. breaking (m/s-2)
* Default stop time (stop time that will be assigned if a stop is let on automatic timing)
* [[Duration|Line duration]] (appears if certain line duration options are selected)
* (Period)
* (Custom Period)
* (Custom)
* Extra stop time on (Padding time which will be added to reach the assigned line duration. Two different modes: Either evenly split on all stops or evenly split an manually marked stops)

=== Auto run line ===
* First train departure
* Timezone
* (Custom time zone)
* Launch trains
* Auto interval
* Manual interval
=== Stop overview ===

== Timetable ==
Shows you a timetable for one day with all the trains that have an assigned order on that line on the selected day.
By default, the timetable is set to the current day and time, but there are two arrows at the top right to switch between the different days of the week.
There are two buttons at the bottom right to zoom in and out.
== State ==

== Accounting ==
Shows you all the accounting data of your line.
The following data is collected and displayed: 

<big>'''(WIP)'''</big>

Line

2024-09-29T17:51:48Z

Schatty:

Line

2024-09-29T16:35:43Z

Schatty:

File:Line stops basics 1.14.png

2024-09-20T18:19:56Z

Schatty:

Line stop basics (1.14)

Signal

2024-09-20T18:01:26Z

Schatty: /* Signal menu */

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the [[How to build track|track editor]] [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when selected by pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, the signal will check the [[path]] of the train (visible in a map mode), and if this train intersects with another train's path, the train will be stopped and the signal will turn red. The signal will check again until it can give the train a green light. The path of the path signal that it checks, will end if it hits a balise or a one way signal, that looks against the direction of the path. 
The bound option: 
''Only for same direction:''This is the default option. The signal will let every path through that is against its own direction, but block every path that is in the same direction. 
''Always:''The signal will block every path form very signal, ignoring their direction. It can also be used by trains from both sides. 

As with the Balise, there is a cosmetic option to shift the signal to either side. 
There is also an option to set a time after which you will be alerted about a waiting train. The default option is the global setting, which you can change in the settings. You can also set a custom time between 1 minute and 24 hours.
 

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

Signal

2024-09-20T17:48:51Z

Schatty: /* Signal types */

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the [[How to build track|track editor]] [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, the signal will check the [[path]] of the train (visible in a map mode), and if this train intersects with another train's path, the train will be stopped and the signal will turn red. The signal will check again until it can give the train a green light. The path of the path signal that it checks, will end if it hits a balise or a one way signal, that looks against the direction of the path. 
The bound option: 
''Only for same direction:''This is the default option. The signal will let every path through that is against its own direction, but block every path that is in the same direction. 
''Always:''The signal will block every path form very signal, ignoring their direction. It can also be used by trains from both sides. 

As with the Balise, there is a cosmetic option to shift the signal to either side. 
There is also an option to set a time after which you will be alerted about a waiting train. The default option is the global setting, which you can change in the settings. You can also set a custom time between 1 minute and 24 hours.
 

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

Signal

2024-09-20T17:47:32Z

Schatty: /* Signal types */

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the [[How to build track|track editor]] [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, the signal will check the [[path]] of the train (visible in a map mode), and if this train intersects with another train's path, the train will be stopped and the signal will turn red. The signal will check again until it can give the train a green light. The path of the path signal that it checks, will end if it hits a balise or a one way signal, that looks against the direction of the path. 
The bound option: 
''Only for same direction:''This is the default option. The signal will let every path through that is against its own direction, but block every path that is in the same direction. 
''Always:''The signal will block every path form very signal, ignoring their direction. It can also be used by trains from both sides. 

As with the Balise, there is a cosmetic option to shift the signal to either side. 
There is also an option to set a time after which you will be alerted about a waiting train. The default option is the global setting, which you can change in the settings. You can also set a custom time between 1 minute and 24 hours.
 

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

Signal

2024-09-20T17:46:19Z

Schatty: /* Signal types */

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the [[How to build track|track editor]] [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|50px|thumb|One way signal
Platform train stop point 1.14.png|50px|thumb|Platform train stop point
Block balise 1.14.png|50px|thumb|Block balise
Path signal 1.14.png|50px|thumb|Path signal (unbound)
No way signal 1.14.png|50px|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, the signal will check the [[path]] of the train (visible in a map mode), and if this train intersects with another train's path, the train will be stopped and the signal will turn red. The signal will check again until it can give the train a green light. The path of the path signal that it checks, will end if it hits a balise or a one way signal, that looks against the direction of the path. 
The bound option: 
''Only for same direction:''This is the default option. The signal will let every path through that is against its own direction, but block every path that is in the same direction. 
''Always:''The signal will block every path form very signal, ignoring their direction. It can also be used by trains from both sides. 

As with the Balise, there is a cosmetic option to shift the signal to either side. 
There is also an option to set a time after which you will be alerted about a waiting train. The default option is the global setting, which you can change in the settings. You can also set a custom time between 1 minute and 24 hours.
 

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

Line

2024-09-20T17:39:38Z

Schatty:

Line

2024-09-20T16:08:14Z

Schatty:

Line

2024-09-20T16:08:02Z

Schatty:

Line

2024-09-20T16:07:34Z

Schatty:

Station

2024-09-18T19:02:32Z

Schatty:

{{Concepts sidebar}}
A station is a set of one or more [[platform]]s whose footprints overlap on each other (in particular, a single platform is a valid station too). Stations are the main destination kind available for picking as a [[line]] [[stop]] (the other being [[waypoint]]s). [[Pax]] [[Spawn rate|spawn]] at stations, travelling from their [[Origin|origin station]] to a [[Destination|destination station]].

There are no limits on how many platforms can be combined into an station, including overlapping them at any [[layer]] or aligned in any orientation.

== Passengers ==

Passengers ([[Pax]] called ingame) have an origin station and a destination station, on their way between these two stations pax can transfer in stations, but also do Out-of-Station Interchanges (walking).

'''Out-of-Station Interchnages (OSI) '''
The max radius at which a OSI is possible is 2.3km. There are two ways to achieve such a link between two stations. First using the auto walk transfer range of the station or using the create walk link function [not assigned] in the station building tool. The transfer between two stations via walking takes time, because the pax are walking at a speed of 1m/s. While the pax are walking they appear in the station hall of the of their destination (of the OSI) with a timer.

== Station properties ==
[[File:Station properties 1.14.png|thumb|Station properties]]
The station properties window is used in the [[Tracks menu]] to edit the station's properties, including:
*The station name
*The station label display settings
*The station coverage area (affecting the reach of the station, and hence the [[spawn rate]] of passengers)
*The auto walk transfer range (this is the range in which the station will automatically create a walking link between stations)
*The platforms pax capacity (a slider for the capacity of the station from 50 pax to 100,000 pax)
*The checkbox to allow Transfer pax overflow into the Station Hall
The station properties window also has a locator button (next to the "Done" button) to jump to the location of the station.

=== Station names ===
There are two options for the station name:
*Automatic naming: Is enabled by default and has to be disabled manually. There is a button with which you can switch between multiple auto-generated names.
*Manual naming: Is activated by unchecking the box for automatic naming under the name. You can then enter your own name.

==== Using station names as tags ====
As of [[Version 1.5]], NIMBY rails does not support station tags. An advanced strategy is to use the station name as a kind of station tag system, which can help in understanding certain menus that do not support tagged listings, as well as the [[Accounting export]]. For example, starting the station name with the stations [https://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Units_for_Statistics|NUTS] regional code can make it easier to do regional aggregations on the accounting export.

== Station window ==
[[File:Station_window.png|400px|thumb|right|Station window]]
=== Passengers ===
Passengers can be show in
*Show all
*Show best current trip. This functions as an "in game routeplanner" for the current time.
*Show dominating trips. This functions as an "in game routeplanner" across time.
*Group by destination
*Group by origin
*Group by waited line stop
*Group by next stop

=== Platforms ===
A platform is a special piece of track which a train can use for loading/unloading passengers.

=== Accounting ===
Stations have their own [[Accounting]] window, showing the accounting events that occurred at this station.

== Stations as depots ==
[[Depot|Depots]] are technically just stations that are used for a particular purpose, storing trains for longer periods of time. Depots do not require any kind of special building to function.
*The station coverage area can be set to zero. This prevents pax from spawning or choosing the depot as a destination.
*The station label display settings can be made less prominent.

[[Category:Concepts]]

Signal

2024-09-18T18:36:07Z

Schatty:

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the [[How to build track|track editor]] [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, the signal will check the [[path]] of the train (visible in a map mode), and if this train intersects with another train's path, the train will be stopped and the signal will turn red. The signal will check again until it can give the train a green light. The path of the path signal that it checks, will end if it hits a balise or a one way signal, that looks against the direction of the path. 
The bound option: 
''Only for same direction:''This is the default option. The signal will let every path through that is against its own direction, but block every path that is in the same direction. 
''Always:''The signal will block every path form very signal, ignoring their direction. It can also be used by trains from both sides. 

As with the Balise, there is a cosmetic option to shift the signal to either side. 
There is also an option to set a time after which you will be alerted about a waiting train. The default option is the global setting, which you can change in the settings. You can also set a custom time between 1 minute and 24 hours.
 

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

Signal

2024-09-18T18:04:35Z

Schatty:

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the track editor [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, it will consider the remaining path to its destination, up to the next same-facing path signal or block balise. If the path is clear of other trains or track reservations, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole path of track segments for itself, until the next same-facing path signal or block balise.
 
''Applies to all trains:'' 
''Ignored by all trains:''

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

Signal

2024-09-18T17:57:55Z

Schatty:

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
The signal menu is accessible in the track editor [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. There you can change the type of the signal, flip it or have additional settings. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.
<gallery>
Signal menu modes 1.14.png|thumb|The two signal menu modes
</gallery>

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
==== One way [1]====
This signal only allows trains to travel in the direction of the arrow. it will also block all paths of path signals that are against its own direction.

==== Platform train stop point [2]====
If you place this signal, trains will stop at it, when you assign the platform via basic stop assignment mode.

==== Block balise [3]====
[[File:Block balise menu 1.14.png|thumb|Block balise menu]]
|thumb|Block balise menu
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.
There are additional options accessible, if you select the signal. The second one allows you to shift the balise to the side of the track, it is purely cosmetic.
The third option lets you choose how the balise should work. The option already selected is the most frequently used option and behaves as described above. There is also a field where you can assign tags to the balise. 
The two options and how they interact with tagged trains: 
''Applies to all trains:'' This is the default option. If you now assign tags to the balise, it will work normally for all trains that do not have this tag assigned, but it will not be seen as a balise by trains that do have the tags. 
''Ignored by all trains:'' If you select this option, the balise will be ignored by all trains without a selected tag, but will be seen as a normal balise by any train that has a selected tag.

==== Path signal [4]====
[[File:Path signal menu 1.14.png|thumb|Path signal menu]]
When a train arrives at this signal, it will consider the remaining path to its destination, up to the next same-facing path signal or block balise. If the path is clear of other trains or track reservations, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole path of track segments for itself, until the next same-facing path signal or block balise.
 
''Applies to all trains:'' 
''Ignored by all trains:''

==== No-way [5]====
[[File:No way signal menu 1.14.png|thumb|No-way signal menu]]
This signal blocks trains from passing over it. There is a option to change the mode of the signals and a field to assign tags to the signal. 
The two options and how they interact with tagged trains: 
''Applies to all trains:''Without a assigned tag to the signal, any train will be blocked from passing it. If you assign a tag, all trains with that tag will be able to pass the signal. 
''Ignored by all trains:''Without a assigned tag to the signal, every train can pass the signal. If you assign a tag, all trains with that tag will be blocked from passing the signal.

==== Block signal (Removed from the game)====
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game.

File:No way signal menu 1.14.png

2024-09-18T17:46:24Z

Schatty:

No-way signal menu (1.14)

File:Path signal menu 1.14.png

2024-09-18T17:36:23Z

Schatty:

Path signal menu (1.14)

File:Block balise menu 1.14.png

2024-09-18T17:16:38Z

Schatty:

Block balise menu (1.14)

Signal

2024-09-18T17:09:10Z

Schatty:

Signal

2024-09-18T17:08:20Z

Schatty: /* Signal menu */

Signal

2024-09-18T17:07:02Z

Schatty:

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

== Signal menu ==
[[File:Signal menu modes 1.14.png|thumb|The two signal menu modes]]
The signal menu is accessible in the track editor [F2] and has two different modes:
*'''Move, delete, edit signals''' [K]: This mode allows you to move, delete and edit signals. You can move them by selecting them and then just dragging them and delete them when pressing [delete]. Every signal type has an own menu to edit them, you can access it by by selecting the signal and looking at the let top side. Pressing [F] while signals are selected will flip them.
*'''Create new Signals''' [L]: This mode allows to create new signals.

== Signal types ==
<gallery>
One way signal 1.14.png|thumb|One way signal
Platform train stop point 1.14.png|thumb|Platform train stop point
Block balise 1.14.png|thumb|Block balise
Path signal 1.14.png|thumb|Path signal (unbound)
No way signal 1.14.png|thumb|No-way signal
</gallery>
=== One way ===
This is a hard rule for the train [[path]] finder to only run over the track in the signal direction. Trains will never consider tracing a path in the opposite direction.

=== Platform train stop point ===
This is a hint for the train AI to stop at the signal position when stopping in a [[station]] [[platform]].

=== Block balise ===
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.

=== Path signal ===
When a train arrives at this signal, it will consider the remaining path to its destination, up to the next same-facing path signal or block balise. If the path is clear of other trains or track reservations, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole path of track segments for itself, until the next same-facing path signal or block balise.

=== No way ===
Trains will never trace a path crossing over this signal, from either direction.

=== Block signal (Removed from the game)===
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game

File:No way signal 1.14.png

2024-09-18T17:03:34Z

Schatty:

No way signal

File:Path signal 1.14.png

2024-09-18T17:02:55Z

Schatty:

Path signal (unbound)

File:Block balise 1.14.png

2024-09-18T17:00:53Z

Schatty:

Block balise

File:Platform train stop point 1.14.png

2024-09-18T17:00:19Z

Schatty:

Platform train stop point

File:One way signal 1.14.png

2024-09-18T16:58:12Z

Schatty:

One way signal

File:Signal menu modes 1.14.png

2024-09-18T16:45:46Z

Schatty:

The two signal menus (1.14)

Signal

2024-09-18T16:42:49Z

Schatty:

Signal

2024-09-18T16:22:07Z

Schatty: /* Block signal */

{{Concepts sidebar}}
Signals make it possible to influence the behavior of [[train]]s running over [[track]]s.

= Platform train stop point =
This is a hint for the train AI to stop at the signal position when stopping in a [[station]] [[platform]].

= One way =
This is a hard rule for the train [[path]] finder to only run over the track in the signal direction. Trains will never consider tracing a path in the opposite direction.

= No way =
Trains will never trace a path crossing over this signal, from either direction.

= Path signal =
When a train arrives at this signal, it will consider the remaining path to its destination, up to the next same-facing path signal or block balise. If the path is clear of other trains or track reservations, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole path of track segments for itself, until the next same-facing path signal or block balise.

= Block balise =
Block balises stop a train path check or path reservation from going beyond their point in the track, from both directions.

= Block signal (Removed from the game)=
When a train arrives at this signal, it will check if the block is clear of other trains, if it is, it will proceed. If it's not, it will stop at the signal and check again in the future until it becomes clear. After the train proceeds past the signal it reserves the whole block of track for itself, until the next block signal or block balise. As of now it is removed from the game