Error with ORTS 0.6.2.776 on ATSF Marceline Sub. V1.0

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • norbertdx
    Senior Member
    • Jun 2005
    • 202
    • New Orleans, La, USA.
    • DTG

    #1

    Error with ORTS 0.6.2.776 on ATSF Marceline Sub. V1.0

    System.IndexOutOfRangeException: Index was outside the bounds of the array
    at ORTS.SignalObject.NexSignal()
    at ORTS.SignalObject.next_sig_lr(SIGFN fn_type)
    at ORTS.SignalHead.Update()
    at ORTS.SignalObject.Update()
    at ORTS.Signals.Update(Single elapsedClockSeconds)
    at ORTS.Simulator.Update(Single elapsedClockSeconds)
    at ORTS.UpdaterProcess.Update()
    at ORTS.UpdaterProcess.UpdateLoop()

    any ideas?

    SPECS
    Win 7 Home Prem
    Processor: AMD Athlon 64x2 Dual-Core Processor TK-53 1.70 GHZ
    Installed mem: 4.00 GB (2.69 GB usable)
    System type: 32-bit Op System


    And yes, I did follow the instructions..
    HP ENVY x360 m6
    Windows 10 Home
    Process: Intel(R) Core(TM) i5-7200U CPU @ 2.50 GHz 2.71 GHz
    RAM: 12.00 GB 64 bit
  • kraus
    1000 Post Veteran

    • Jan 2001
    • 1086
    • Madison, Wisconsin
    • General

    #2
    The program is failing on track vector 2514 looking for signal 1817. I was able to get the program to run by altering line 672 in file Signals.cs to

    if ( sigIndex !=-1 && signalObjects[sigIndex] != null && signalObjects[sigIndex].thisRef != thisRef) // Not a signal head for this signal

    The code above it returns a sigIndex of -1. Still remaining to determine is why it is returning -1 for this signal.

    Edit: I have identified the track in the route that is causing the problem with the signal. I missed repairing this in my patch. The next patch will include this repair. If you would like to repair this yourself add a section of track to the junction node with the red pole as show in the attached picture. The junction node is near -94.60330963 39.08187485.

    This problem was detected by TsUtils which reported

    'TrackNode(2515)-TrPin(0)': '0-Reference' of the Node-Definition may cause error(s).
    Attached Files
    Last edited by kraus; 07-31-2011, 16:52. Reason: found cause

    Comment

    Working...