System.NullReferenceException at ORTS.SignalWorldObject..ctor (Paris Metro route fails to open)
Bug #1159180 reported by
David Martin Lewis
This bug report is a duplicate of:
Bug #1159025: System.NullReferenceException at ORTS.SignalWorldObject..ctor.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Rails |
Triaged
|
High
|
Unassigned |
Bug Description
The Paris Metro route (RFSP-V3_6) crashes at startup.
Log file is attached.
Dave (J72fan)
tags: | added: crash |
summary: |
- Paris Metro route fails to open (all OR versions) + System.NullReferenceException at ORTS.SignalWorldObject..ctor (Paris + Metro route fails to open) |
Changed in or: | |
importance: | Undecided → Medium |
milestone: | none → 0.9 |
status: | New → Triaged |
tags: | added: signals |
Changed in or: | |
importance: | Medium → High |
To post a comment you must log in.
It has not been possible to determine the cause of this crash.
However, for other routes with similar problems it has been found that these problems were caused by spurious world files in the WORLD directocy.
These spurious world-files often also contain signals which have references to tdb-entries within the valid range, but which are double as these tdb reference actually refer to signals in other world-files that are still valid. These double references causes severe errors as various cross-references will either point to invalid items or not be set at all. This invariable causes a program crash.
To change the program in order to be able to handle these errors would require extensive changes to the processing and probably even to the data structure itself, which would lead to more extensive changes being required throughout the signalling process.
In view of the limited resources in the project team and given the fact that very few routes are affected and the cause of the problem is within the route data rather than with the program, it has been decided that no effort will be made to resolve this problem.
So, no fix will be provided for this crash for the foreseeable future.