aboutsummaryrefslogtreecommitdiff
path: root/src
ModeNameSize
-rw-r--r--CMakeLists.txt17801logplain
-rw-r--r--activeobject.h1584logplain
-rw-r--r--ban.cpp3997logplain
-rw-r--r--ban.h1505logplain
-rw-r--r--base64.cpp3900logplain
-rw-r--r--base64.h250logplain
-rw-r--r--biome.cpp7265logplain
-rw-r--r--biome.h2330logplain
-rw-r--r--camera.cpp19490logplain
-rw-r--r--camera.h4989logplain
-rw-r--r--cavegen.cpp16360logplain
-rw-r--r--cavegen.h2786logplain
d---------cguittfont248logplain
-rw-r--r--chat.cpp17078logplain
-rw-r--r--chat.h7207logplain
-rw-r--r--client.cpp71535logplain
-rw-r--r--client.h12265logplain
-rw-r--r--clientmap.cpp24401logplain
-rw-r--r--clientmap.h3525logplain
-rw-r--r--clientmedia.cpp19621logplain
-rw-r--r--clientmedia.h4455logplain
-rw-r--r--clientobject.cpp1773logplain
-rw-r--r--clientobject.h3687logplain
-rw-r--r--clientserver.h14236logplain
-rw-r--r--clientsimpleobject.h1113logplain
-rw-r--r--clouds.cpp9656logplain
-rw-r--r--clouds.h1678logplain
-rw-r--r--cmake_config.h.in827logplain
-rw-r--r--cmake_config_githash.h.in233logplain
-rw-r--r--collision.cpp17463logplain
-rw-r--r--collision.h2763logplain
-rw-r--r--config.h949logplain
-rw-r--r--connection.cpp41753logplain
-rw-r--r--connection.h14993logplain
-rw-r--r--constants.h2775logplain
-rw-r--r--content_abm.cpp8359logplain
-rw-r--r--content_abm.h1006logplain
-rw-r--r--content_cao.cpp52753logplain
-rw-r--r--content_cao.h853logplain
-rw-r--r--content_cso.cpp2889logplain
-rw-r--r--content_cso.h1032logplain
-rw-r--r--content_mapblock.cpp42857logplain
-rw-r--r--content_mapblock.h992logplain
-rw-r--r--content_mapnode.cpp8109logplain
-rw-r--r--content_mapnode.h1510logplain
-rw-r--r--content_nodemeta.cpp5541logplain
-rw-r--r--content_nodemeta.h1196logplain
-rw-r--r--content_object.h1263logplain
-rw-r--r--content_sao.cpp39170logplain
-rw-r--r--content_sao.h8293logplain
-rw-r--r--convert_json.cpp9878logplain
-rw-r--r--convert_json.h1169logplain
-rw-r--r--craftdef.cpp27130logplain
-rw-r--r--craftdef.h11691logplain
-rw-r--r--database-dummy.cpp5299logplain
-rw-r--r--database-dummy.h1376logplain
-rw-r--r--database-leveldb.cpp5014logplain
-rw-r--r--database-leveldb.h1432logplain
-rw-r--r--database-sqlite3.cpp10103logplain
-rw-r--r--database-sqlite3.h1719logplain
-rw-r--r--database.cpp1581logplain
-rw-r--r--database.h1280logplain
-rw-r--r--daynightratio.h1841logplain
-rw-r--r--debug.cpp7040logplain
-rw-r--r--debug.h4218logplain
-rw-r--r--defaultsettings.cpp15645logplain
-rw-r--r--defaultsettings.h989logplain
-rw-r--r--dungeongen.cpp17147logplain
-rw-r--r--dungeongen.h2711logplain
-rw-r--r--emerge.cpp16823logplain
-rw-r--r--emerge.h3474logplain
-rw-r--r--environment.cpp70536logplain
-rw-r--r--environment.h12736logplain
-rw-r--r--event.h1912logplain
-rw-r--r--event_manager.h2964logplain
-rw-r--r--exceptions.h3595logplain
-rw-r--r--filecache.cpp2258logplain
-rw-r--r--filecache.h1358logplain
-rw-r--r--filesys.cpp16717logplain
-rw-r--r--filesys.h3272logplain
-rw-r--r--game.cpp92134logplain
-rw-r--r--game.h3122logplain
-rw-r--r--gamedef.h2822logplain
-rw-r--r--genericobject.cpp4538logplain
-rw-r--r--genericobject.h2405logplain
-rw-r--r--gettext.cpp7700logplain
-rw-r--r--gettext.h2427logplain
-rw-r--r--gettime.h1568logplain
-rw-r--r--guiChatConsole.cpp14325logplain
-rw-r--r--guiChatConsole.h3571logplain
-rw-r--r--guiDeathScreen.cpp4108logplain
-rw-r--r--guiDeathScreen.h1504logplain
-rw-r--r--guiEngine.cpp15653logplain
-rw-r--r--guiEngine.h8446logplain
-rw-r--r--guiFileSelectMenu.cpp3240logplain
-rw-r--r--guiFileSelectMenu.h1757logplain
-rw-r--r--guiFormSpecMenu.cpp77187logplain
-rw-r--r--guiFormSpecMenu.h9000logplain
-rw-r--r--guiKeyChangeMenu.cpp11598logplain
-rw-r--r--guiKeyChangeMenu.h1946logplain
-rw-r--r--guiMainMenu.h1489logplain
-rw-r--r--guiMessageMenu.cpp3910logplain
-rw-r--r--guiMessageMenu.h1444logplain
-rw-r--r--guiPasswordChange.cpp6223logplain
-rw-r--r--guiPasswordChange.h1459logplain
-rw-r--r--guiPauseMenu.cpp6512logplain
-rw-r--r--guiPauseMenu.h1607logplain
-rw-r--r--guiTextInputMenu.cpp4867logplain
-rw-r--r--guiTextInputMenu.h1461logplain
-rw-r--r--guiVolumeChange.cpp4597logplain
-rw-r--r--guiVolumeChange.h1533logplain
-rw-r--r--hex.h1689logplain
-rw-r--r--httpfetch.cpp18563logplain
-rw-r--r--httpfetch.h3573logplain
-rw-r--r--hud.cpp15126logplain
-rw-r--r--hud.h3478logplain
-rw-r--r--intlGUIEditBox.cpp34197logplain
-rw-r--r--intlGUIEditBox.h5777logplain
-rw-r--r--inventory.cpp19832logplain
-rw-r--r--inventory.h7767logplain
-rw-r--r--inventorymanager.cpp20983logplain
-rw-r--r--inventorymanager.h5068logplain
-rw-r--r--irr_aabb3d.h939logplain
-rw-r--r--irr_v2d.h1070logplain
-rw-r--r--irr_v3d.h996logplain
-rw-r--r--irrlichttypes.h1209logplain
-rw-r--r--irrlichttypes_bloated.h989logplain
-rw-r--r--irrlichttypes_extrabloated.h1187logplain
-rw-r--r--itemdef.cpp17981logplain
-rw-r--r--itemdef.h4664logplain
-rw-r--r--itemgroup.h1143logplain
d---------json151logplain
d---------jthread340logplain
-rw-r--r--keycode.cpp11714logplain
-rw-r--r--keycode.h1724logplain
-rw-r--r--light.cpp3873logplain
-rw-r--r--light.h2988logplain
-rw-r--r--localplayer.cpp15410logplain
-rw-r--r--localplayer.h2080logplain
-rw-r--r--log.cpp3863logplain
-rw-r--r--log.h2490logplain
-rw-r--r--logoutputbuffer.h1351logplain
d---------lua109logplain
-rw-r--r--luaentity_common.h1050logplain
-rw-r--r--main.cpp47163logplain
-rw-r--r--main.h1698logplain
-rw-r--r--mainmenumanager.h3217logplain
-rw-r--r--map.cpp104403logplain
-rw-r--r--map.h14663logplain
-rw-r--r--mapblock.cpp26378logplain
-rw-r--r--mapblock.h13598logplain
-rw-r--r--mapblock_mesh.cpp38099logplain
-rw-r--r--mapblock_mesh.h4812logplain
-rw-r--r--mapchunk.h1831logplain
-rw-r--r--mapgen.cpp32186logplain
-rw-r--r--mapgen.h8186logplain
-rw-r--r--mapgen_indev.cpp16628logplain
-rw-r--r--mapgen_indev.h5471logplain
-rw-r--r--mapgen_math.cpp11474logplain
-rw-r--r--mapgen_math.h1777logplain
-rw-r--r--mapgen_singlenode.cpp3081logplain
-rw-r--r--mapgen_singlenode.h1610logplain
-rw-r--r--mapgen_v6.cpp28511logplain
-rw-r--r--mapgen_v6.h4900logplain
-rw-r--r--mapgen_v7.cpp21325logplain
-rw-r--r--mapgen_v7.h3946logplain
-rw-r--r--mapnode.cpp16146logplain
-rw-r--r--mapnode.h6789logplain
-rw-r--r--mapsector.cpp4870logplain
-rw-r--r--mapsector.h2753logplain
-rw-r--r--mesh.cpp12014logplain
-rw-r--r--mesh.h2207logplain
-rw-r--r--modalMenu.h3580logplain
-rw-r--r--modifiedstate.h1171logplain
-rw-r--r--mods.cpp10816logplain
-rw-r--r--mods.h5490logplain
-rw-r--r--nameidmapping.cpp1553logplain
-rw-r--r--nameidmapping.h2137logplain
-rw-r--r--nodedef.cpp28550logplain
-rw-r--r--nodedef.h9299logplain
-rw-r--r--nodemetadata.cpp4058logplain
-rw-r--r--nodemetadata.h2790logplain
-rw-r--r--nodetimer.cpp3683logplain
-rw-r--r--nodetimer.h2216logplain
-rw-r--r--noise.cpp14945logplain
-rw-r--r--noise.h4479logplain
-rw-r--r--object_properties.cpp4565logplain
-rw-r--r--object_properties.h1587logplain
-rw-r--r--particles.cpp10666logplain
-rw-r--r--particles.h3735logplain
-rw-r--r--pathfinder.cpp28856logplain
-rw-r--r--pathfinder.h10102logplain
-rw-r--r--player.cpp6923logplain
-rw-r--r--player.h6086logplain
-rw-r--r--porting.cpp10751logplain
-rw-r--r--porting.h5376logplain
-rw-r--r--profiler.h5101logplain
-rw-r--r--quicktune.cpp2618logplain
-rw-r--r--quicktune.h2837logplain
-rw-r--r--quicktune_shortcutter.h2148logplain
-rw-r--r--rollback.cpp34358logplain
-rw-r--r--rollback.h1911logplain
-rw-r--r--rollback_interface.cpp11938logplain
-rw-r--r--rollback_interface.h3662logplain
d---------script331logplain
-rw-r--r--serialization.cpp6079logplain
-rw-r--r--serialization.h3163logplain
-rw-r--r--server.cpp143536logplain
-rw-r--r--server.h21717logplain
-rw-r--r--serverlist.cpp7233logplain
-rw-r--r--serverlist.h1727logplain
-rw-r--r--serverobject.cpp2476logplain
-rw-r--r--serverobject.h7118logplain
-rw-r--r--settings.h20302logplain
-rw-r--r--sha1.cpp5680logplain
-rw-r--r--sha1.h1623logplain
-rw-r--r--shader.cpp23261logplain
-rw-r--r--shader.h3008logplain
-rw-r--r--sky.cpp20406logplain
-rw-r--r--sky.h3719logplain
-rw-r--r--socket.cpp12940logplain
-rw-r--r--socket.h3128logplain
-rw-r--r--sound.cpp882logplain
-rw-r--r--sound.h3234logplain
-rw-r--r--sound_openal.cpp14385logplain
-rw-r--r--sound_openal.h943logplain
d---------sqlite116logplain
-rw-r--r--staticobject.cpp2224logplain
-rw-r--r--staticobject.h2261logplain
-rw-r--r--strfnd.h4413logplain
-rw-r--r--subgame.cpp7779logplain
-rw-r--r--subgame.h2791logplain
-rw-r--r--test.cpp56289logplain
-rw-r--r--test.h853logplain
-rw-r--r--threads.h1141logplain
-rw-r--r--tile.cpp45851logplain
-rw-r--r--tile.h7271logplain
-rw-r--r--tool.cpp6206logplain
-rw-r--r--tool.h3166logplain
-rw-r--r--treegen.cpp19564logplain
-rw-r--r--treegen.h2728logplain
d---------util685logplain
-rw-r--r--version.cpp1255logplain
-rw-r--r--version.h988logplain
-rw-r--r--voxel.cpp15933logplain
-rw-r--r--voxel.h13184logplain
-rw-r--r--voxelalgorithms.cpp4681logplain
-rw-r--r--voxelalgorithms.h1678logplain
/span>="itemize">If you want to stop programming the entire route without saving it, use the &#8220;Cancel route programming&#8221; button. </li> <li class="itemize">The third button is especially useful for programming simple block sections on a main running line, since you can stay at the starting signal (punch starting TCB and select third button). </li> <li class="itemize">If a route should end in a dead end, you MUST use the &#8220;Finish in NEXT section&#8221; button, because there is no final TCB that you could punch. </li> <li class="itemize">The third button does NOT work on sections with more than 2 exits, because the system won&#8217;t be able to determine the final TCB of the route then.</li></ul> <!--l. 527--><p class="noindent" > <a id="x1-50r9"></a> <!--l. 527--><p class="noindent" ><span class="ecsx-1200">3.9</span> <span class="ecsx-1200">Route</span> <span class="ecsx-1200">information</span> <span class="ecsx-1200">screen</span> <a id="Q1-1-0"></a> <!--l. 529--><p class="noindent" ><img src="10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.png" alt="PIC" > <!--l. 531--><p class="noindent" >This is the screen that appears when you click &#8220;Edit Route&#8221;. It lets you change the route name and delete the route. Also, it shows a summary of the route and its elements. <!--l. 535--><p class="noindent" >The route summary lists information per track section on the route, so the line starting with &#8220;1&#8221; is the first section of the route. <!--l. 538--><p class="noindent" >The ARS rule list and its purpose is explained later. <!--l. 540--><p class="noindent" > <a id="x1-51r10"></a> <!--l. 540--><p class="noindent" ><span class="ecsx-1200">3.10</span> <span class="ecsx-1200">Specifying</span> <span class="ecsx-1200">signal</span> <span class="ecsx-1200">aspects</span> <a id="Q1-1-0"></a> <!--l. 542--><p class="noindent" >By default, newly programmed routes show an aspect that comes closest to &#8220;Proceed at maximum speed&#8221;. However, it can be desirable to change this behavior, like when the route passes a diverging turnout, the train should be signalled to drive slower, or the route is a shunt route and therefore only &#8220;Shunting allowed&#8221; should be shown. <!--l. 548--><p class="noindent" >This is the purpose of the &#8220;Change Aspect&#8221; button in the route info screen. <!--l. 551--><p class="noindent" >Signal aspects in advtrains consist of 4 sections: main (Information for train moves), dst (Distant signal information, not implemented yet), shunt (Information for shunt moves) and info (additional information, currently not in use). <ul class="itemize1"> <li class="itemize">Train may proceed as train move at maximum speed: &#8220;main: free, speed -1&#8221; </li> <li class="itemize">Train may proceed as train move at speed of 8: &#8220;main: free, speed 8&#8221; </li> <li class="itemize">Train may proceed as shunt move: &#8220;shunt: free&#8221;</li></ul> <!--l. 562--><p class="noindent" >There&#8217;s a field in the &#8220;shunt&#8221; part of signal aspects that is not displayed in the GUI, but is of potential interest to developers of signal addons: shunt.proceed_as_main. <ul class="itemize1"> <li class="itemize">A train move can always become a shunt move by passing a signal that shows &#8220;Halt for train moves, shunting permitted&#8221; </li> <li class="itemize">A shunt move can only pass a signal saying &#8220;Proceed as train move, shunting not permitted&#8221; when proceed_as_main is true.</li></ul> <!--l. 571--><p class="noindent" >The property is used by the Limit Of Shunt sign, where proceed_as_main is set to false. Shunt moves have to stop in front of it, while train moves are signalled &#8220;Proceed&#8221;. Regular main signals that show &#8220;green&#8221; have the field set to true, so that all trains can pass it. <!--l. 577--><p class="noindent" > <a id="x1-52r4"></a> <!--l. 577--><p class="noindent" ><span class="ecsx-1200">4</span> <span class="ecsx-1200">Interlocking</span> <span class="ecsx-1200">system</span> <span class="ecsx-1200">operation</span> <a id="Q1-1-0"></a> <!--l. 579--><p class="noindent" >Setting up the interlocking for a portion of a railway network requires some time, experience and planning, but once done, there&#8217;s not much to do anymore to make trains run on your, now safer, railway. This section covers some useful practices to route trains across your network. <!--l. 584--><p class="noindent" >At the moment, routes can either be set by clicking the signal or via LuaATC, or by using the &#8220;Remote Routesetting&#8221; button from the Onboard Computer. It is planned to control this via a &#8220;signal box&#8221; view based on the currently broken itrainmap. <!--l. 589--><p class="noindent" > <a id="x1-53r1"></a> <!--l. 589--><p class="noindent" ><span class="ecsx-1200">4.1</span> <span class="ecsx-1200">Train</span> <span class="ecsx-1200">Safety</span> <span class="ecsx-1200">System</span> <a id="Q1-1-0"></a> <!--l. 591--><p class="noindent" >The Train Safety System, called &#8220;LZB&#8221; in the code (from the german term Linienzugbeeinflussung, although this is a completely different system), ensures that trains obey any restrictions imposed by signals when influence points are set. This way, it is not possible to pass signals at danger or to bypass speed restrictions. <!--l. 597--><p class="noindent" >It is possible to overrun red signals, if a route is cancelled while a train is approaching. Real interlocking systems use a mechanism called Approach locking for this, however, as of now, there&#8217;s no similar system in this mod. If a red signal is overrun, the train brakes using emergency brake (&#8220;BB&#8221;) and can not be moved any further. You should then examine the situation and drive the train backwards out of the section. <!--l. 605--><p class="noindent" > <a id="x1-54r2"></a> <!--l. 605--><p class="noindent" ><span class="ecsx-1200">4.2</span> <span class="ecsx-1200">Simple</span> <span class="ecsx-1200">route</span> <span class="ecsx-1200">setting</span> <span class="ecsx-1200">and</span> <span class="ecsx-1200">cancelling</span> <a id="Q1-1-0"></a> <!--l. 607--><p class="noindent" >To set a route, simply right-click the signal, select a route and click &#8220;set route&#8221;. If there are no conflicts, the signal turns green and the train is allowed to proceed. <!--l. 611--><p class="noindent" >It may be possible that the route can not be set, because one or more other routes conflict with the current one, or a section is blocked. In this case, the signal stays red, and the conflicting item is shown in the formspec. As soon as the conflict is resolved (by cancellation or release of the conflicting route, or the section becoming free), the requested route will be set and the signal turns green. <!--l. 618--><p class="noindent" >If a route is either requested or set, it can be cancelled from the signalling formspec. This means that all turnouts and sections are released, and the signal reverts back to red. This of course only works when the train has not passed the signal yet. There is no mechanism for Approach Locking. <!--l. 624--><p class="noindent" > <a id="x1-55r3"></a> <!--l. 624--><p class="noindent" ><span class="ecsx-1200">4.3</span> <span class="ecsx-1200">Automatic</span> <span class="ecsx-1200">Working</span> <a id="Q1-1-0"></a> <!--l. 626--><p class="noindent" >Block signals on main running lines usually only have a single route to set, the one proceeding along the main line. Their purpose is only to show whether there are trains in the next section. So, it would be convenient if this only route would set itself again after a train passed. <!--l. 632--><p class="noindent" >This is what Automatic Working is for. Set a route, click &#8220;Enable Automatic Working&#8221;, and as soon as a train passes, the route is automatically re-set. <!--l. 636--><p class="noindent" >This function is nearly identical to SimSig automatic signals. It can also be useful on a line with high traffic, when there&#8217;s a low-frequented access to a siding. You&#8217;d enable automatic working for the main route and cancel it only when you need a train to go into the siding. <!--l. 641--><p class="noindent" > <a id="x1-56r4"></a> <!--l. 641--><p class="noindent" ><span class="ecsx-1200">4.4</span> <span class="ecsx-1200">Automatic</span> <span class="ecsx-1200">Route</span> <span class="ecsx-1200">Setting</span> <span class="ecsx-1200">(ARS)</span> <a id="Q1-1-0"></a> <!--l. 643--><p class="noindent" >As interlocking systems evolved, the goal always was to offload work from the human to the system, automating things. Modern interlocking systems can automatically set routes based on a pre-programmed routing table for each particular train. Since one outstanding feature of Advtrains is it&#8217;s high degree of automation, it has a similar system to automatically set routes for a train depending on certain parameters. <!--l. 650--><p class="noindent" >Every train in Advtrains has 2 internal properties that can be set through the Onboard Computer of every engine in the train, the &#8220;Line&#8221; and the &#8220;Routing Code&#8221; <ul class="itemize1"> <li class="itemize">The &#8220;Line&#8221; property is supposed to distinguish trains of multiple lines that share a track. </li> <li class="itemize">The &#8220;Routing Code&#8221; property is supposed to tell the target of a train or which route it should take to reach the target</li></ul> <!--l. 659--><p class="noindent" >Examples: <!--l. 661--><p class="noindent" ><img src="11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.png" alt="PIC" > <!--l. 663--><p class="noindent" >Both lines share the section between Blackbirdshire and Parktown. To divert them again, they can save their line number in the &#8220;Line&#8221; field. <!--l. 667--><p class="noindent" ><img src="12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.png" alt="PIC" > <!--l. 669--><p class="noindent" >Some trains should go to B, some to C, the direction can be set with a routing code. <!--l. 672--><p class="noindent" >One single routing code should not contain spaces. You can set multiple routing codes by just separating them with spaces in the Routing Code field. So, &#8220;Stn Ori&#8221; would be matched by ARS rules either containing &#8220;Stn&#8221; or &#8220;Ori&#8221;. This does not work for lines. <!--l. 677--><p class="noindent" > <a id="x1-57r1"></a> <!--l. 677--><p class="noindent" ><span class="ecsx-1000">4.4.1</span> <span class="ecsx-1000">Writing</span> <span class="ecsx-1000">ARS</span> <span class="ecsx-1000">Rules</span> <a id="Q1-1-0"></a> <!--l. 679--><p class="noindent" >Every route of every signal can be given a set of ARS rules. A single ARS rule can either match a line or a routing code (combinations, e.g. and&#8217;s, are not yet supported). The first rule in the first route that matches any of the properties of the train is selected, and that route is set for the train. <!--l. 685--><p class="noindent" ><img src="13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.png" alt="PIC" > <!--l. 687--><p class="noindent" >You can add an asterisk (&#8220;*&#8221;) to the ARS rules of one route. That route then becomes the default route. <!--l. 690--><p class="noindent" >If no explicit ARS rule matches the train, then the default route is chosen and set. If there is no default route, nothing happens and the signal remains red. <!--l. 694--><p class="noindent" > <a id="x1-58r2"></a> <!--l. 694--><p class="noindent" ><span class="ecsx-1000">4.4.2</span> <span class="ecsx-1000">Using</span> <span class="ecsx-1000">ARS</span> <a id="Q1-1-0"></a> <!--l. 696--><p class="noindent" >In contrast to Automatic working, where the route is re-set immediately after the train passed, ARS sets the route only when the train approaches the signal, e.g. is just about to start braking in front of it. <!--l. 700--><p class="noindent" >At any place where one of the following things take place, you should use the ARS system in favor of Automatic Working: <ul class="itemize1"> <li class="itemize">A main line diverts into 2 or more lines: Using ARS, you can direct the trains along the line where they should go </li> <li class="itemize">Two or more main lines join into one: You cannot use automatic working here, because all routes are tried to be set at the same time and it is a matter of luck which one &#8220;wins&#8221;. In a bad situation, you have a train coming from A, but it cannot proceed because Signal B has won the &#8220;route race&#8221; into the shared section, even if there&#8217;s no train coming from B. Using ARS, by just specifying the &#8220;default route&#8221; by a *, the inward route is only set when a train approaches. </li> <li class="itemize">Complex intersections, which are probably a combination of the above two </li> <li class="itemize">sometimes-used branching tracks on which only certain trains (with certain routing code or line) should head off, like the entrance to a factory where only one specific goods train should drive in.</li></ul> <!--l. 718--><p class="noindent" >In the route overview, you can see some information on the ARS settings: All routes that have ARS rules are highlighted red, the &#8220;default route&#8221; is highlighted green. <!--l. 722--><p class="noindent" >ARS does not affect signals which already have a route set, and signals which are operating under &#8220;Automatic Working&#8221;. <!--l. 725--><p class="noindent" > <a id="x1-59r5"></a> <!--l. 725--><p class="noindent" ><span class="ecsx-1200">5</span> <span class="ecsx-1200">Final</span> <span class="ecsx-1200">notes</span> <a id="Q1-1-0"></a> <!--l. 727--><p class="noindent" >The interlocking system is mainly finished, though there are still some plans and ideas. They include: <ul class="itemize1"> <li class="itemize">Signalbox panels, as revival of itrainmap </li> <li class="itemize">Distant signals </li> <li class="itemize">On-Train head-up display for oncoming signals (they have something like this in Czech Republic, I forgot how it&#8217;s called.)</li></ul> <!--l. 735--><p class="noindent" >Apart from this, there&#8217;s the large oncoming project of a new timetable-based train automation system, but this will take some time to evolve and is out of the scope of this document. <!--l. 739--><p class="noindent" >If you have any suggestions, corrections, improvements, criticism or cute kittens and stuff, you can always contact me by various means (Forum PM, E-Mail (orwell@bleipb.de), Linuxworks server chat a.s.o.). Have fun! <!--l. 744--><p class="noindent" >- orwell </body></html>