Signal/WP deadlock
Bug #1685916 reported by
Carlo Santucci
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Open Rails |
Fix Released
|
Low
|
Carlo Santucci | ||
Bug Description
An Italian signal set foresees that some signals do not open if next signal is closed. If before next signal a WP is placed, both signals will never open. For standard WPs there's no way out, however absolute WPs should open signals when time comes. This does not occur now, as a precondition to start absolute WP count is that next signal in front of the train is the one in front of the WP too.
This precondition is too restrictive and should be removed, leaving as precondition only that all path from train to WP signal is reserved by the train.
Revision history for this message
| Carlo Santucci (carlosanit1) wrote | #1 |
| tags: | added: signals |
| Changed in or: | |
| assignee: | nobody → Carlo Santucci (carlosanit1) |
| status: | New → Fix Committed |
| Changed in or: | |
| milestone: | none → 1.3 |
| importance: | Undecided → Low |
| Changed in or: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in x.3834.