System.ArgumentOutOfRangeException at Orts.Simulation.Activity..ctor (X4263, ATSF Seligman Sub 2.0, Amtrak 3 From ABQ, Warning: PlatformStartID 503 is not present in TDB file)
Bug #1798494 reported by
Derek Morton
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Open Rails |
Fix Released
|
Medium
|
Carlo Santucci | ||
Bug Description
OR should not crash when platform not present
Revision history for this message
| Derek Morton (derek-a) wrote | #1 |
Revision history for this message
| Carlo Santucci (carlosanit1) wrote | #2 |
Revision history for this message
| Carlo Santucci (carlosanit1) wrote | #3 |
| Changed in or: | |
| assignee: | nobody → Carlo Santucci (carlosanit1) |
| status: | New → In Progress |
| status: | In Progress → Fix Committed |
| tags: | added: activity crash |
| summary: |
- Warning: PlatformStartID 503 is not present in TDB file + System.ArgumentOutOfRangeException at Orts.Simulation.Activity..ctor + (X4263, ATSF Seligman Sub 2.0, Amtrak 3 From ABQ, Warning: + PlatformStartID 503 is not present in TDB file) |
| Changed in or: | |
| importance: | Undecided → Medium |
| milestone: | none → 1.3 |
| Changed in or: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I agree only partly. Such event occurs if the activity has been built for a different route version. One could protect the code from this crash, but he could get further crashes in other locations of the code because of this incompatibility.
Looking at the code it comes out that there were more than one not present platforms: the first one could be catched and generated the warning, while the second one generated the crash. So there were at least two incompatible platforms. How many other? And maybe some AI train has a broken path.