Advanced Trains

User Tools

Site Tools

You are here: Advanced Trains » Events » Conferences » 2021-10-23
events:conf:2021-10-23

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
events:conf:2021-10-23 [2021-10-25 02:39]
blockhead Who is our community? - a bit more depth than the meeting but still.. 		events:conf:2021-10-23 [2023-01-17 18:23] (current)
ywang old revision restored (2022-08-07 21:50)
Line 5: Line 5:
  
 ===== Timetable ===== ===== Timetable =====
-    * **@orwell** mentioned the [[dev:lines:timetable_plan|timetable system]] as one of the current priorities. In the future, when the timetable system is mature, it might be possible to change the signaling system in a way that respects timetables (e.g. to prioritize late trains).+    * **@orwell** mentioned the [[dev:proposals:timetable_plan|timetable system]] as one of the current priorities. In the future, when the timetable system is mature, it might be possible to change the signaling system in a way that respects timetables (e.g. to prioritize late trains).
     * The summary is that it will allow building a timetable based on recorded timing information on station/stop rails.     * The summary is that it will allow building a timetable based on recorded timing information on station/stop rails.
     * @orwell floated the possibility of a LuaATC interface to the scheduling code     * @orwell floated the possibility of a LuaATC interface to the scheduling code
Line 65: Line 65:
         * Takes priority over line speed restriction.         * Takes priority over line speed restriction.
     * @ywang added speed indicators for ks signals     * @ywang added speed indicators for ks signals
 +
 +(notes by @ywang)
 +    * The Ks signals are changed to (hopefully) be realistic.
 +    * Distant signaling will be removed from the branch.
 +      * It is far from maturity, and implementing it properly would likely extend the development time by a lot and move the focus away from the signals themselves.
 +      * The Zs3v signal will be kept.
 +      * Distant signaling will be implemented as a separate feature.
 +      * This will affect worlds that already use distant signaling, but it will //not// affect the actual operation of the train. (It should also be noted that using a WIP branch on a production server is not recommended for obvious reasons)
  
  
Line 100: Line 108:
  
 The following points were briefly discussed: The following points were briefly discussed:
-  * Distant signaling in the ''new-ks'' branch will be removed as it is way too far from maturity. +  * A "line speed" signal aspect (the maximum speed at which a train is allowed to pass a line) should be implemented, which should override the max speed restriction if necessary. (Refer to notes on the ''new-ks'' branch)
-  * A "line speed" signal aspect (the maximum speed at which a train is allowed to pass a line) should be implemented, which should override the max speed restriction if necessary.+
   * The ''trainhud'' branch is ready for review, although the custom train HUD feature still needs to be tested.   * The ''trainhud'' branch is ready for review, although the custom train HUD feature still needs to be tested.
   * **@orwell**: Minetest currently lacks a mechanism for custom auxiliary keys.   * **@orwell**: Minetest currently lacks a mechanism for custom auxiliary keys.
events/conf/2021-10-23.1635122374.txt.gz · Last modified: 2021-10-25 02:39 by blockhead

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki