[rickloader]

I`m getting an out of range exception - log attached.
This in timetable mode using New forest Route from github.
U2022.09.13-1336 Out of range
U2022.08.07-1321 Ok (and also 15August ok)
ORNYMG 1.4-709Rev130 - Ok
ORNYMG 1.4-531Rev125- not ok , exception
Rick

Attached File(s)

•  OpenRailsLog1336.txt (69.07K)
  Number of downloads: 130

[charland]

While running an activity in v1.5-rc1 today the program crashed to desktop. Appears to be the same problem with precipitation in both cases.
 ORlogCrash1.txt (13.06K)
Number of downloads: 122

 ORlogCrash2.txt (13.49K)
Number of downloads: 117


Paul :-)

[engmod]

Paul,

Carlo has already fixed the precipitation issue.
We have to wait for the 1.5 team to put it into rc2.

I have isolated when the buzzer problem started, notified which ORMG it started with.
So we need to wait for rc2 as well.

[charland]

Thanks Derek. The buzzer warnings, yesterday while running I had one in Johnstown and for the rest of the activity every time I uncoupled, I waited a full second before applying the throttle and never had another buzzer, not even in the usual places. Try that and see if it works for you too.

Paul :-)

[cesarbl]

I'll try to see what can be done to suppress the wheelslip warning. When starting from zero speed the model needs a small amount of time to stabilize.

[cjakeman]

 engmod, on 16 September 2022 - 10:51 PM, said:

Carlo has already fixed the precipitation issue.
We have to wait for the 1.5 team to put it into rc2.

Yes, Carlo's fix will definitely be included in v1.5.

Thanks to Carlo and everyone who reported it.

[charland]

Ran another activity today. Had more buzzers then I had expected but noticed something. If you hear the sound of the uncoupling, then you do not get buzzed. If you don't hear it, then you do get buzzed. I don't know if it's a coincidence or not but the lack of the sound of the uncoupling was in both Johnstown and Gloversville, two areas where they are several background sounds going on at the same time and I started to wonder if one or more of these sounds were interfering with the uncoupling sound and somehow causing the buzzer and traction warning. This didn't occur while "out in the country" where the tiles are low density and might have two sounds at the most.

Paul :-)

[cjakeman]

Hi Dan,

 A D REID, on 18 August 2022 - 10:23 AM, said:

While investigating this problem, I encountered another issue -- the simulator crashed when I tried to resume at a point that was 01:00:00 into the activity -- OpenRailsLog 2022-08-17b.txt

I also encountered another crash when I attempted to resume from a point 00:47:40 into the activity -- OpenRailsLog 2022-08-17-c.txt

Your crash at 00:47:00 appears to be due to a multi-threading issue in the code, which I believe James Ross is looking into.

This log file also suggests why "the simulator crashed at 01:00:00". When I restore from the Save file that you provided - 2022-08-17 09.40.03.save - the log file contains the statements:

Information: Invalid reservation for train : PLAYER [1], section : 452 not restored
Information: Invalid reservation for train : PLAYER [1], section : 479 not restored
Information: Invalid reservation for train : PLAYER [0], section : 564 not restored
Information: Invalid reservation for train : PLAYER [0], section : 575 not restored
Information: Invalid reservation for train : PLAYER [0], section : 731 not restored
Information: Invalid reservation for train : PLAYER [0], section : 732 not restored
Information: Invalid reservation for train : PLAYER [0], section : 733 not restored
Information: Invalid reservation for train : PLAYER [0], section : 734 not restored
Information: Invalid reservation for train : PLAYER [0], section : 735 not restored

Because of these missing reservations, the AI train KC-AI-2C which is due to start 60 mins into the simulation cannot be located in the appropriate track circuit and the simulation cannot continue.

So it looks like a bad Save is causing this problem. How the Save came to be bad is another issue. When I save the activity during those first 47 minutes, these statements are nowhere to be seen.

Any thoughts?

Attached File(s)

•  OpenRailsLog 2022-08-17b.txt (14.25K)
  Number of downloads: 156
•  OpenRailsLog 2022-08-17-c.txt (18.3K)
  Number of downloads: 128

[A D REID]

 cjakeman, on 18 September 2022 - 07:59 AM, said:

Because of these missing reservations, the AI train KC-AI-2C which is due to start 60 mins into the simulation cannot be located in the appropriate track circuit and the simulation cannot continue.

So it looks like a bad Save is causing this problem. How the Save came to be bad is another issue. When I save the activity during those first 47 minutes, these statements are nowhere to be seen.

Any thoughts?

Hi Chris,

When I resume from 2022-08-17 09.40.03.save, the player train is stopped before a RED signal. The simulation time (shown on the F5 display) is 18:45:00. I can shut down the simulator after a few moments, and my log file shows the same messages that you have seen.

There is a wait point in the player path prior to this signal and the wait point should expire at 18:45.

Coincidence? Perhaps not! Maybe the save was taken while the signal script was running.

When I resume from the previous save (2022-08-17 09.36.01.save), the simulation time is 18:35:21 -- and if I close the simulator a few moments later, the log file does NOT show any invalid reservations. I am attaching that save file as:  NYD-8.zip (728.46K)
Number of downloads: 110

Today, I have resumed from 2022-08-17 09.56.01.save and made several attempts to save at 18:45:00 or shortly after. This is what happened:


1) 2022-09-18 16.04.23.save (simulation time 18:45:00) -- NO invalid reservation messages.
2) 2022-09-18 20.29.16.save (simulation time 18:45:05) -- "bad" save file -- resulting in invalid reservations on resuming.  NYD-9.zip (1.11MB)
Number of downloads: 124
3) 2022-09-18 20.29.17.save (simulation time 18:45:06) -- "bad" save file -- resulting in invalid reservations on resuming.  NYD-10.zip (1.12MB)
Number of downloads: 121
4) 2022-09-18 16.05.30.save (simulation time 18:46:07) -- NO invalid reservation messages.

Regards,
Dan

[cjakeman]

 A D REID, on 18 September 2022 - 06:27 PM, said:

1) 2022-09-18 16.04.23.save (simulation time 18:45:00) -- NO invalid reservation messages.
2) 2022-09-18 20.29.16.save (simulation time 18:45:05) -- "bad" save file -- resulting in invalid reservations on resuming. NYD-9.zip
3) 2022-09-18 20.29.17.save (simulation time 18:45:06) -- "bad" save file -- resulting in invalid reservations on resuming. NYD-10.zip
4) 2022-09-18 16.05.30.save (simulation time 18:46:07) -- NO invalid reservation messages.

Dan, you've done a terrific job pinning the issue down to a brief time window like this. I think it shows how difficult it is to develop code which works in every route, activity, script etc.!

Unless we are really lucky, I don't think there will be a solution in time for the v1.5 release, although we should change the log message from "information" to "warning" with maybe a bit more detail. I do think we ought to try to find the root cause and I'll do what I can towards that.