Un Coupling problem?

[rdamurphy]

I'm actually working on something related to that, perhaps I'll give it a try and see if I can replicate it. Is it any particular route or consist? Or any particular piece of rolling stock or is it across the board?

Robert

[seagoon]

..... Is it any particular route or consist? Or any particular piece of rolling stock or is it across the board?

Is that question for me, Robert?

If so, it happens in Explore mode only, in the X1413 version only, but any route and any locomotive/rolling stock combo.

Bruce

[Timbit]

Robert,
for me it is in Explore a route and it does it in all the routes, when I started having the problem it was when you uncoupled, but now with the latest update it seems to work ok uncoupling , but now the problem is re coupling back to anything ?
Thanks
Tim

[eric]

Just tested on Sunday's experimental release... drove a consist, coupled, pressed F9, ***BOOOM*** modal box and crash to the menu.

Build = 0.0.4787.22591 Fri 08/02/2013 12:33

Error: System.NullReferenceException: Object reference not set to an instance of an object.
   at ORTS.Train.UpdateTrackActionsUncoupling(Boolean originalTrain)
   at ORTS.Simulator.UncoupleBehind(TrainCar car)
   at ORTS.Simulator.UncoupleBehind(Int32 carPosition)
   at ORTS.UncoupleCommand.Redo()
   at ORTS.UncoupleCommand..ctor(CommandLog log, Int32 carPosition)
   at ORTS.Popups.TrainOperationsCoupler.TrainOperationsCoupler_Click(Control arg1, Point arg2)
   at ORTS.Popups.Control.OnClick(Point mouseControlLocation)
   at ORTS.Popups.Control.MouseClick(WindowMouseEvent e)
   at ORTS.Popups.Control.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.ControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.WindowControlLayout.HandleMouseUp(WindowMouseEvent e)
   at ORTS.Popups.Window.MouseUp()
   at ORTS.Popups.WindowManager.HandleUserInput(ElapsedTime elapsedTime)
   at ORTS.Viewer3D.HandleUserInput(ElapsedTime elapsedTime)
   at ORTS.Viewer3D.Update(Single elapsedRealTime, RenderFrame frame)
   at ORTS.UpdaterProcess.Update()
   at ORTS.UpdaterProcess.DoUpdate()
   at ORTS.UpdaterProcess.UpdaterThread()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Ran a different activity, different consist, different path.... Pulled up the F9 box, and as soon as I tried to scroll right, ***BOOM***

Got the same error.

Different route, different consist... Uncoupled 5 cars in, recoupled, uncoupled 15 cars in, tried to recouple, ***BOOM***

Error: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at ORTS.Signals.requestClearNode(TrainRouted thisTrain, TCSubpathRoute routePart)
   at ORTS.Train.UpdateTrackActionsCoupling(Boolean couple_to_front)
   at ORTS.Simulator.FinishCoupling(Train drivenTrain, Train train, Boolean couple_to_front)
   at ORTS.Simulator.FinishRearCoupling(Train drivenTrain, Train train)
   at ORTS.Simulator.CheckForCoupling(Train drivenTrain, Single elapsedClockSeconds)
   at ORTS.Simulator.Update(Single elapsedClockSeconds)
   at ORTS.Viewer3D.Update(Single elapsedRealTime, RenderFrame frame)
   at ORTS.UpdaterProcess.Update()
   at ORTS.UpdaterProcess.DoUpdate()
   at ORTS.UpdaterProcess.UpdaterThread()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

[apco25]

Explore mode Build 0.0.4775.13622 1/27/13 DEBUG BUILD

FYI, that is the build number of the menu interface, open up the revision.txt file to get the true build number. I just tried 1427 and it does indeed crash like the other have experienced. The last build I was using from 2/1/2013 (oddly no build number is shown for this one in the revision.txt file, just 000$) works just fine.

Obviously something got broken!

[milw2042]

FYI, that is the build number of the menu interface, open up the revision.txt file to get the true build number. I just tried 1427 and it does indeed crash like the other have experienced. The last build I was using from 2/1/2013 (oddly no build number is shown for this one in the revision.txt file, just 000$) works just fine.

Obviously something got broken!

No build number was to be found. It just said:

$Revision: 000 $
Sun 01/27/2013
07:34 AM

[jjtang]

This is due to an error in the new signalling code and I am sure the team is working on a solution.

[fredstev]

Hi Everyone
I'm a new guy here, and have been reading about the couple/uncouple issue with ORTS in the latest experimental releases. I'm having the same problem when I use Ver. 1427 (2-9-2013). Marias Pass, explore - I'm careful to set the handbrake, disconnect the airhose, and uncouple. That works. I move 20 ft. downtrack, stop and come back to a joint. Then I get this screen:

coupling crash-ver. 1427.jpg

If I try the same procedure without setting the handbrake, and disconnecting the airhose, ORTS simply crashes to a light grey screen. When I do the exact same exercise in the V-0.8.0.1251 release, no problem at all.

I thought about submitting a bug report, but the O.R. folks are obviously aware of the problem from what I've seen here. I just added a screenshot because I'm not aware of anyone else getting something like that.

(I should add that this does NOT happen during a "Activity", as others have said. No crashes for me unless in "explore" mode)

[sidp]

I am using X1427 - same problem with dump after trying to recouple in Explore mode. But, a lot of bugs that I found in OR 0.8 release have been fixed! It's looking good. Keep on truckin' !