[Eldorado.Railroad]

Unfortunately I have known about this one for quite some time...but lost track of it. The title of the O/P tells it all. I invite others to please see if it also happens to them. Please specify your O/S too!

Thanks!

Added on March 8, 2016:

Oops..yes it works in simple cases..but otherwise you can replicate the bug!

1) This can happen in activities ONLY!

2) You have a player path ABCD and an AI path DCBA. Please note that the two paths are NOT exactly the same and the BC/CB sections are single track. Also note that the the BC/CB sections are the same for BOTH paths, I.E. SHARED. Also note the paths are in OPPOSITE directions!

3) The activity is designed such that the player and AI train follow the full length of their paths, no waiting points etc.

4) In my case I used multiple AI trains to create ample traffic.

5) One of the AI trains is ON the CB section and the player train is waiting to access its BC section. PLEASE NOTE, that CB and BC are the SAME section of single track! It is implied here that the look ahead paths in the DispatchViewer are in collision, overlaid on top of each other.

6) Press CTRL-ALT F11...and bang, the sim freezes up and eventually crashes

QED

[copperpen]

Windows 10, X3458. No crash. Tried two routes, one with semaphores and one with colour lights.

[Eldorado.Railroad]

Sorry..bumped...I hope this post will be reread. Important info updated.

Thanks!

[James Ross]

Eldorado.Railroad, on 07 March 2016 - 12:24 PM, said:

Unfortunately I have known about this one for quite some time...but lost track of it. The title of the O/P tells it all. I invite others to please see if it also happens to them. Please specify your O/S too!

Please attach the log file and, if you know of one, tell us about a freely available (in box or downloadable) route/activity which exhibits this. It's just a bug and you need to report it as such, thanks! :)

[Eldorado.Railroad]

James,

The route is Maple Leaf Tracks, Kicking Horse Pass 2.0. If you have this route..that would be an extra bonus. Otherwise I will have to recreate the problem on a similar non payware route.

For the present, I have attached a focused log file...which shows what happens when CTRL-ALT-F11 is pressed and the crash occurs.

Thanks so much for your time and patience,
Steve

 OpenRailsLog.txt (10.87K)
Number of downloads: 392

[engmod]

Hi Steve,

If you can package up the activity, I will test for you.

cheers
Derek

[Csantucci]

Hi Eldorado,
try to replace the two runactivity exes with the attached ones in release x.3476 and check if the problem persists.
 Runactivities.zip (614.12K)
Number of downloads: 257

[James Ross]

Eldorado.Railroad, on 15 March 2016 - 04:20 PM, said:

James,

The route is Maple Leaf Tracks, Kicking Horse Pass 2.0. If you have this route..that would be an extra bonus. Otherwise I will have to recreate the problem on a similar non payware route.

For the present, I have attached a focused log file...which shows what happens when CTRL-ALT-F11 is pressed and the crash occurs.

Thanks so much for your time and patience,
Steve

OpenRailsLog.txt

Error: Orts.Viewer3D.Processes.ThreadHangException: Thread 'Updater Process' has hung; the consistent stack trace is shown below:
   at Orts.Viewer3D.Popups.SignallingDebugWindow.PrepareFrame(ElapsedTime elapsedTime, Boolean updateFull) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Popups\SignallingDebugWindow.cs:line 110

I'm going to guess that something has gotten itself in to a loop in here. :(

Unfortunately, I don't have the route in question, but may have a look at the code if I get a moment.

[engmod]

Another crash for you

Attached File(s)

•  OpenRailsLog.txt (15.37K)
  Number of downloads: 212

[Eldorado.Railroad]

Csantucci, on 16 March 2016 - 12:41 AM, said:

try to replace the two runactivity exes with the attached ones in release x.3476 and check if the problem persists.

Hi Carlo,

Replaced the executables with the ones you provided. It still hangs, and keyboard remains unresponsive, the only way to get back control is to is to kill the process in the taskmanager.

BUT, judging by what I see I think you have taken the watchdog timer code out of these special compilations...is that correct?
If that is so, I am sure it will help with this bug :
http://www.elvastowe...ental-releases/
I will test your executables against the bug mentioned above, it may solve the problem I have been having..I will see.

Molto gracie,
Steve