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 00:15]
blockhead Adding my notes 		events:conf:2021-10-23 [2023-01-17 17: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 39: Line 39:
     * A presence at Linux and Free Software events. Giving away the stickers to entice people?     * A presence at Linux and Free Software events. Giving away the stickers to entice people?
     * Our strengths: Best in class automation, signalling, track system, full programmability. Our weaknesses: art, usability     * Our strengths: Best in class automation, signalling, track system, full programmability. Our weaknesses: art, usability
 +
 +==== Who is our community / user base? ====
 +    * LinuxForks (formerly LinuxWorks NG) was always considered 'the' advtrains server in the past.
 +    * @orwell even mentioned that he recommends people visit LinuxWorks to learn about advrains.
 +    * Nowadays there are at least 3 other servers that run advtrains: Tunneler's Abyss, SurvivalWorks Urban Edition, and VanessaE's Train Table. This means server admins affected by the project are at least CalebJ/Hume2, Edgy1 and VanessaE. These have had different levels of involvement:
 +      * Hume2: Authored linetrack, which added the need for the suitable substrate feature to advtrains core. Also authored the lines 11-99 display colours for the [[usage:trains:basic_trains:advtrains_subway|Subway Train]]. Had extensive experience on LinuxWorks before separating.
 +      * VanessaE: Forgiving collision mode was added at her request.
 +      * Edgy1: The train copy tool was requested by a moderator/admin on the SurvivalWorks Urban Edition server, which is part of EdgyNet, but not by Edgy1 himself. Edgy1 formerly played as Trump on LinuxWorks NG so had prior experience with advtrains as well.
 +    * Other less notable servers include 56independent's server and C&C City server, the admins of which also both play/played on LinuxForks.
 +    * We also have a (not very quantifiable) number of people who play singleplayer. The number of ContentDB downloads gives some indication of how many people have tried the base game, as well as each of the train packs also available on ContentDB. Some of these people post in the minetest forums.
  
 ===== Automated Testing ===== ===== Automated Testing =====
Line 55: 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 90: 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.1635120929.txt.gz · Last modified: 2021-10-25 00:15 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