[edwardk]

I am not sure if this is related to what has been discussed, but I did manage to find a bug where events that are initially set to 0 or less are left out of the update process. Initially, a location event would start off with an activation level of 0 and would be increased by one by an action event, but the location event in question would never register properly because the update process would only accept it if the activation code which is based on its initial value is > 0. By testing at >= 0, I was able to get a successful activity end once the location event was reached.

Edit: This was a quick and dirty test.

Edward K.

[edwardk]

I indicated I thought I found an issue, but this is not the case.

Edward K.

[edwardk]

As of V2361, cars that are now dropped off before the event DropOffWagonsAtLocation is activated will now be acknowledged and the event triggered. The only issue is that cars dropped off will not be checked if they are on the correct siding so in this case, read your work order carefully :whistling: .

[edwardk]

As of V2372, the fix needed to be reversed due to issues reported.


Edward K.

[edwardk]

I will have the proper fix for this issue shortly.

Edward K.

[edwardk]

As of V2432, cars can now be dropped off if the DropOffWagonsAtLocation event is not enabled by default. Once enabled by an event such as the location event, a test will check to see if the required cars are at the correct siding.

Edward K.