Timetable bugs
Bug #1817878 reported by
r.roeterdink
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Rails |
Fix Released
|
Undecided
|
r.roeterdink |
Bug Description
Various small bugs in timetable mode :
- on attach/transfer, player train is not always recognized as target train
- station stop check : error in check on train position, only TC is checked, not position within TC
- use of multiple consists in detach and transfer command is not processed correctly
- approach control does not always work properly when there are no further signals in the train's path
Changed in or: | |
milestone: | none → 1.4 |
To post a comment you must log in.
Proposed changes :
- on attach/transfer, player train is not always recognized as target train.
When checking for target train, in Number does not match, check OrgAINumber.
- station stop check : error in check on train position, only TC is checked, not position within TC.
Check if position of rear of train is within platform position.
- use of multiple consists in detach and transfer command is not processed correctly.
Check list of input.
- approach control does not always work properly when there are no further signals in the train's path.
Variable DistanceToSignal is now a float, set to default value when there is no signal. Therefor it is not possible to check if there is a signal or not.
Proposal is to change variable to float?, such that it only has a value when there is an actual signal.