OpenTTD

Tasklist

FS#5901 - Cargo not loading

Attached to Project: OpenTTD
Opened by James (Jam35) - Sunday, 09 February 2014, 11:56 GMT
Last edited by fonsinchen (fonsinchen) - Sunday, 09 February 2014, 21:11 GMT
Type Bug
Category Core
Status Closed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 1.4.0-beta4
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

See savegame: Coal does not load !here.
This task depends upon

Closed by  fonsinchen (fonsinchen)
Sunday, 09 February 2014, 21:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  in r26327
Comment by frosch (frosch) - Sunday, 09 February 2014, 12:58 GMT
The orders of the trains say "unload and leave empty".
Adjust the orders if you did not meant to order them to do that.
Comment by James (Jam35) - Sunday, 09 February 2014, 13:05 GMT
See train #129.
(Full load any cargo)
Comment by James (Jam35) - Sunday, 09 February 2014, 13:18 GMT
  • Field changed: Percent Complete (100% → 0%)
Please check train #129
Comment by frosch (frosch) - Sunday, 09 February 2014, 13:18 GMT
Ah, it is loading at the same station as it unloads.
I think that used to work, but was disabled for cdist or something. Likely should still work, if cdist is disabled.
Comment by James (Jam35) - Sunday, 09 February 2014, 13:22 GMT
That trains only purpose is to remove the erroneous cargo.
The cargo could be sent anywhere but I cannot load it :)
Comment by fonsinchen (fonsinchen) - Sunday, 09 February 2014, 14:26 GMT
Do you remember how the waiting cargo got there? It has an invalid station, but not the constant INVALID_STATION (which it should have) as its next hop. I wonder how that happened.
Comment by James (Jam35) - Sunday, 09 February 2014, 15:05 GMT
Unfortunately I was not online at the time the cargo got there.
A team member says that the cargo acceptance was lost there for a short time, hence cargo is at the station.
We obviously have no idea why it cannot now be picked up as usual.
Comment by fonsinchen (fonsinchen) - Sunday, 09 February 2014, 15:17 GMT
Apparently it used the wrong part of the loaded_at_xy / next_station union when inserting into the map. The numbers match up quite nicely then.

Loading...