Advanced Trains

User Tools

Site Tools

You are here: Advanced Trains » Developer Reference » proposals » Interlocking Route Programming Rework
dev:proposals:newroute

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
dev:proposals:newroute [2023-02-23 12:25] – suggest ATC syntax for editing turnout locks maverick2797dev:proposals:newroute [2026-01-09 19:53] (current) – orwell
Line 5: Line 5:
 General action plan (steps): General action plan (steps):
   - Create a new, better formspec railway map (like itrainmap) with extension points   - Create a new, better formspec railway map (like itrainmap) with extension points
-  - Create a new route programming and editing procedure+  - Create a new route programming and editing procedure (DONE!)
   - (later) Signalbox view ([[https://de.wikipedia.org/wiki/Datei:Ausschnitt.png|Example]])   - (later) Signalbox view ([[https://de.wikipedia.org/wiki/Datei:Ausschnitt.png|Example]])
  
Line 17: Line 17:
  
 ===== New route programming ===== ===== New route programming =====
 +
 +**This is now done and released.**
  
 With the reworked system, it must be possible to edit routes after creation. Also, the process should be less manual. With the reworked system, it must be possible to edit routes after creation. Also, the process should be less manual.
Line 25: Line 27:
   * (Later) There may be special situations where you still want to add manual turnout locks. To be decided later.   * (Later) There may be special situations where you still want to add manual turnout locks. To be decided later.
     * Suggest using ATC-like syntax to edit individual turnout locks: ''cr | st | l | s |r''     * Suggest using ATC-like syntax to edit individual turnout locks: ''cr | st | l | s |r''
 +    * As implemented: just use the old route programmer for this.
  
 ===== Autorouter ===== ===== Autorouter =====
Line 41: Line 44:
  
 ===== Proper shunt routes ===== ===== Proper shunt routes =====
 +-> done
  
 The existing implementation does not allow for real shunt/call-on routes, because a route cannot be set into a section that is blocked. The existing implementation does not allow for real shunt/call-on routes, because a route cannot be set into a section that is blocked.
Line 46: Line 50:
   * Routes should get a flag allowing them to be set even if a section is blocked.   * Routes should get a flag allowing them to be set even if a section is blocked.
   * Turnout locks must still be settable, and no part must have a route set.   * Turnout locks must still be settable, and no part must have a route set.
-  * Note on Royston Problem: Occasion workaround by "manually" releasing last route section -> add LuaATC function for exceptional route release.+  * Note on Royston Problem: Occasion workaround by "manually" releasing last route section -> add LuaATC function for exceptional route release. -> ???
  
 ===== More things to fix along the way ===== ===== More things to fix along the way =====
  
-  * Find a solution for the multiple-times-in-same-block issue. Train can enter a section twice or more if it is particularily long, the interlocking must still work. Currently, train entering a section is counted at most once, it must be counted every time it enters. +  * Find a solution for the multiple-times-in-same-block issue. Train can enter a section twice or more if it is particularily long, the interlocking must still work. Currently, train entering a section is counted at most once, it must be counted every time it enters. -> done 
-  * Provision for distant signals and varying aspects along the route+  * Provision for distant signals and varying aspects along the route -> Done, we have full distant signalling support
  
 //Add more as it appears.// //Add more as it appears.//
dev/proposals/newroute.1677155153.txt.gz · Last modified: by maverick2797