Elvas Tower: Incorrect Stop Position between X3960 and X3966 - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Incorrect Stop Position between X3960 and X3966 Rate Topic: -----

#1 User is offline   Railcat 

  • Hostler
  • Group: Status: Active Member
  • Posts: 51
  • Joined: 19-January 12
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 29 October 2017 - 01:08 AM

Attached Image: demo.jpg
Same timetable, same service, same action: An AI train goes to the end of the track, stops, reverses and goes back.

In X3960, everything's good.

In X3966, fatal errors occured. It seems that the AI train can not fully stop in the same distances before the end node of the track and thus go out of the track.

Any codes have been changed on AI's break action after X3960?

Error: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size.
parameter: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at Orts.Simulation.Timetables.TTTrain.CheckReadyToAttach() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\Timetables\TTTrain.cs:line 6378
at Orts.Simulation.Timetables.TTTrain.SwitchToNodeControl(Int32 thisSectionIndex) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\Timetables\TTTrain.cs:line 9863
at Orts.Simulation.Physics.Train.UpdateSignalState(Int32 backward) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\Physics\Train.cs:line 3267
at Orts.Simulation.Physics.Train.Update(Single elapsedClockSeconds) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\Physics\Train.cs:line 1613
at Orts.Simulation.AIs.AITrain.AIUpdate(Single elapsedClockSeconds, Double clockTime, Boolean preUpdate) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\AIs\AITrain.cs:line 680
at Orts.Simulation.AIs.AI.AITTUpdate(Single elapsedClockSeconds, Boolean preUpdate, Boolean& activeTrains) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\AIs\AI.cs:line 785
at Orts.Simulation.Simulator.Update(Single elapsedClockSeconds) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Simulation\Simulator.cs:line 694
at Orts.Viewer3D.Viewer.Update(RenderFrame frame, Single elapsedRealTime) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Viewer.cs:line 710
at Orts.Viewer3D.Processes.GameStateViewer3D.Update(RenderFrame frame, Double totalRealSeconds) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateViewer3D.cs:line 121
at Orts.Viewer3D.Processes.UpdaterProcess.Update() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Processes\UpdaterProcess.cs:line 128
at Orts.Viewer3D.Processes.UpdaterProcess.DoUpdate() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Processes\UpdaterProcess.cs:line 108
at Orts.Viewer3D.Processes.UpdaterProcess.UpdaterThread() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Processes\UpdaterProcess.cs:line 74
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

#2 User is offline   Coolhand101 

  • Foreman Of Engines
  • Group: Status: Contributing Member
  • Posts: 998
  • Joined: 13-June 15
  • Gender:Male
  • Simulator:MSTS
  • Country:

Posted 29 October 2017 - 05:33 AM

According to the logs, there does not appear to be anything obvious after x3960.
Maybe a bug has slipped through, causing your problem.

You can test each build after x3960 to narrow down what version first caused this.

Thanks

#3 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 7,000
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 29 October 2017 - 09:08 AM

3966 is an unwanted release; its changes were reverted in release x.3967. So pls. try again with actual releases.

#4 User is offline   Railcat 

  • Hostler
  • Group: Status: Active Member
  • Posts: 51
  • Joined: 19-January 12
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 30 October 2017 - 05:12 AM

View PostCsantucci, on 29 October 2017 - 09:08 AM, said:

3966 is an unwanted release; its changes were reverted in release x.3967. So pls. try again with actual releases.

You're right. Everything's good. :sign_thanks:

#5 User is offline   markyisri 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 27
  • Joined: 10-November 17
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 13 November 2017 - 04:56 AM

View PostCsantucci, on 29 October 2017 - 09:08 AM, said:

3966 is an unwanted release; its changes were reverted in release x.3967. So pls. try again with actual releases.


What was done in 3966 that needed to be reversed?
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users