System.NullReferenceException at ORTS.MSTSDieselLocomotive.Update (X2903, timetable $create)

[Phil Moser]

After the $create option was introduced, I modified the timetable I have been working on (modified Surfliner2) to use the command instead of using separate columns for staging trains. I have 14 trains that use the $create command and if I select 4 of those as player trains, the program will error out with "Error: System.NullReferenceException: Object reference not set to an instance of an object.". I can't find a reason in the timetable for this and these same trains will run normally as AI trains. I can run the trains that these become at the end of their run (via dispose command) and they all start at the correct time. This same error is in the beginning of the log file as a warning no matter what train I run, but doesn't seem to cause any problems. I've attached the log file.

[r.roeterdink (r-roeterdink)]

<quote>
I've attached the log file.
<unquote>
I see no sign of it, though - apparently something has gone wrong.
Could you please attach the timetable file as well, please.

[Phil Moser (phil-moser1)]

Hi Rob,

Files attached. The trains that cause the crash when I select them as the player train are in columns E, K, M, and AU in the attached Excel file. These same trains run normally as AI trains if I select any other train to run. Also, if I remove the create command from the affected trains, they will start up normally.

Regards,
Phil

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of r.roeterdink
Sent: Sunday, March 01, 2015 5:10 PM
To: <email address hidden>
Subject: [Bug 1426944] Re: Timetable $create option problem

<quote>
I've attached the log file.
<unquote>
I see no sign of it, though - apparently something has gone wrong.
Could you please attach the timetable file as well, please.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1426944

Title:
  Timetable $create option problem

Status in Open Rails Tracker:
  New

Bug description:
  After the $create option was introduced, I modified the timetable I
  have been working on (modified Surfliner2) to use the command instead
  of using separate columns for staging trains. I have 14 trains that
  use the $create command and if I select 4 of those as player trains,
  the program will error out with "Error: System.NullReferenceException:
  Object reference not set to an instance of an object.". I can't find a
  reason in the timetable for this and these same trains will run
  normally as AI trains. I can run the trains that these become at the
  end of their run (via dispose command) and they all start at the
  correct time. This same error is in the beginning of the log file as a
  warning no matter what train I run, but doesn't seem to cause any
  problems. I've attached the log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/or/+bug/1426944/+subscriptions

[r.roeterdink (r-roeterdink)]

Can you please check version 2916 if this problem is now corrected?

[Phil Moser (phil-moser1)]

Rob,

X2916 seems to have fixed the problem I described, however I was running a train to see if other problems I was having were fixed as well since I believe they were related. When I tried to restore a save for continuing a run, I get the now infamous "Save file is incompatible with this version of Open Rails.", "Saved Version X2916", "Current Version X2916" (same versions). The last I saw, this error was last corrected in X2893.

Phil

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of r.roeterdink
Sent: Monday, March 09, 2015 7:39 PM
To: <email address hidden>
Subject: [Bug 1426944] Re: Timetable $create option problem

Can you please check version 2916 if this problem is now corrected?

** Changed in: or
     Assignee: (unassigned) => r.roeterdink (r-roeterdink)

** Changed in: or
       Status: New => In Progress

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1426944

Title:
  Timetable $create option problem

Status in Open Rails Tracker:
  In Progress

Bug description:
  After the $create option was introduced, I modified the timetable I
  have been working on (modified Surfliner2) to use the command instead
  of using separate columns for staging trains. I have 14 trains that
  use the $create command and if I select 4 of those as player trains,
  the program will error out with "Error: System.NullReferenceException:
  Object reference not set to an instance of an object.". I can't find a
  reason in the timetable for this and these same trains will run
  normally as AI trains. I can run the trains that these become at the
  end of their run (via dispose command) and they all start at the
  correct time. This same error is in the beginning of the log file as a
  warning no matter what train I run, but doesn't seem to cause any
  problems. I've attached the log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/or/+bug/1426944/+subscriptions

[r.roeterdink (r-roeterdink)]

Restore problem corrected in version 2918.

[James Ross (twpol)]

Looking at the comments, this issue seems to be fixed. Please can any further issues, with different errors, be reported as new bugs.