NaN Power with latest Experimental Version

[Don6218]

Hello all, I upgraded to the latest Experimental Version of OR, I got "NaN Power" with no movement with all trains that I tried, even on different routes that were all working fine with the previous version.
The Log-Files are already deleted, unfortunately. But I changed back to the latest Stable-Version all is well now. Back to Simming.
Just a note to let you know. No reply is necessary. I will try the Experimental Version again later.

[geepster775]

Yea, there's an issue with the latest x237 testing version. It ran okay on straightaways until I hit a curve of any kind

I backed off to an older testing version x120 that I had on hand and was waiting until the next weekly.


https://www.youtube.com/watch?v=x971_m4_sVw



Nothing was showing in the log using OR equipment on OR routes. Nothing bombed either. It just lasped onto a stuck wheel spinning state. When I ran MSTS equipment on an MSTS route (Lasalle) then it would bomb back to desktop with an error


Error: System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(Double value)
at Orts.Simulation.Physics.Train.UpdateSectionStateEx plorer() in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulatio n\Physics\Train.cs:line 9018
at Orts.Simulation.Physics.Train.UpdateExplorer(Singl e elapsedClockSeconds) in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulatio n\Physics\Train.cs:line 2913
at Orts.Simulation.Physics.Train.Update(Single elapsedClockSeconds, Boolean auxiliaryUpdate) in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulatio n\Physics\Train.cs:line 1864
at Orts.Simulation.Simulator.Update(Single elapsedClockSeconds) in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulatio n\Simulator.cs:line 709
at Orts.Viewer3D.Viewer.Update(RenderFrame frame, Single elapsedRealTime) in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\View er.cs:line 815
at Orts.Viewer3D.Processes.GameStateViewer3D.Update(R enderFrame frame, Double totalRealSeconds) in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\GameStateViewer3D.cs:line 122
at Orts.Viewer3D.Processes.UpdaterProcess.Update() in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\UpdaterProcess.cs:line 128
at Orts.Viewer3D.Processes.UpdaterProcess.DoUpdate() in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\UpdaterProcess.cs:line 108
at Orts.Viewer3D.Processes.UpdaterProcess.UpdaterThre ad() in C:\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\UpdaterProcess.cs:line 74
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.RunInternal(Exec utionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[daniellouwrens]

So did you guys use the OR bug reporting system??