Transfer problem

[caveatemptor]

In my game I have two towns linked by rail, each with a bank out of reach of the train station. So I have armoured vans transport valuables from one bank to the train station, valuables then transported by train to the other town, armoured vans then bring the valuables from that station to the second bank, drop them off, and then the valuables from that bank go along the same route to the other bank. or at least that's what's supposed to happen. In order to do this I have set my vans in each town to load and unload as normal at the bank, and transfer and take cargo at the train station. The problem is that vans are transporting valuables from the bank to the van, and then picking up valuables they have just dropped off, taking them back to the bank where they can't drop them off, taking them back to the trains station and so on. Does anyone know if/how I can fix this?

[petert]

Sounds just like a problem that can be fixed with CargoDist (http://www.tt-forums.net/viewtopic.php?f=33&t=41992, grab binary in latest few posts). CargoDist lets cargo choose its destination(s), so your valuables can't end up in the same place.

I've observed that 2 out of the 3 transfer problems can usually be solved with CargoDist.

[Alberth]

Either by using two stations (one for each direction), or by using a crago-dist/dest version. See also Feederservice for Airport while thinking about passengers as 'valuables'.

Edit: I added a description of a Two-way feeder service page to the wiki describing the solution.

[sportbotaniker]

Hi, happy new year.

I still have troubles getting this.
Read about the Cargo Dist/Dest thing and now I am completely irritated

pity it is a 65 page thread and a sticky of how to would be nice

What is the difference between
Cargo dest and Cargo dist ?
Do these affect all cargos or passengers only ?
Do they work with ECS ?
Do they work in 075 , I only read about the R-nightlies versions ?

Thanks & Best Regards
Sportbotaniker

[Alberth]

I still have troubles getting this.
Read about the Cargo Dist/Dest thing and now I am completely irritated

Sorry to hear that.

With OpenTTD (like almost all open source programs), everything is done by unpaid volunteers. (The donations for the forum and the OpenTTD project are only used to pay for hosting the servers.)
It means a lot of things are not neatly organized (not in the last place because it changes constantly). It also means normal users like yourself, have a lot of freedom to decide what direction you want to go with playing and/or developing OpenTTD. In other words, OpenTTD is literally developed by and for the users.

So instead of being irritated (which doesn't help anybody), please try to turn it into positive energy, eg by helping to improve the situation.

pity it is a 65 page thread and a sticky of how to would be nice

Point is that all cargo d*st programs are highly experimental. Nobody knows exactly how to handle the new situation in the game. Giving each cargo a destination is easy (kind of), but new problems pop up as a result, and it is not entirely clear how to deal with them in a good way in the game at this time, afaik. (I don't keep track of it exactly, so I may be wrong here.) That is what the 65 pages of discussion are about.

What is the difference between
Cargo dest and Cargo dist ?

They are different experiments. I only played one of them, so I cannot compare them for you.

Do these affect all cargos or passengers only ?

Most likely it is configurable.

Do they work with ECS ?

I would guess so, ECS is about new cargo types and new industries (say, new buildings). They have nothing to do with cargo destinations (ie the decision where the cargo should go to), as far as I can see.
The simplest way is to try it and see what happens, I think.

Do they work in 075 , I only read about the R-nightlies versions ?

Neither.
Both 0.7.5 and rXYZ nightlies are binary (ready to run) programs *without* cargo d[ei]st.

The versions with cargo destinations are *extensions* on the official program (ie a 'patched version') and are built seperately (and published in the thread). Your confusion may arise from the fact that the cargo d*st extensions also use rXYZ as indication of their version.

[Trako]

What happened to good old "unload all" or "transfer all"? I'd like those to be options, and I don't like the idea of needing an addon to "correct" the problem presented in the program itself. I have a station that is supposed to be the dump off point to feed a much larger train. When the train is in the station it is being fed, otherwise the trains take back what they were supposed to offload and leave, and end up going back to the origin station. I really don't see the whole point of "unload and take cargo" even if there are more than one car types, because I can imagine that each cargo type would be loaded on again anyway. Change it back to unload all or transfer all, or implement a better system without having to rely on a third party kludge. As it is, there is no fathomable way for this transfer station configuration to work properly.

[Rubidium]

Then select 'no loading' from the 'loading' dropdown. Doesn't require any third party stuff.

[planetmaker]

What happened to good old "unload all" or "transfer all"?

Rest assured that those options still exist. If you want to cash in on the passengers, though, it has always been a good idea to NOT use "unload all", but to just issue a order to the station without anything special. Then cargo will be delivered and payed for - if it is accepted by the station while "unload all" will unload it, no matter what.

[oberhümer]

Do these affect all cargos or passengers only ?

Most likely it is configurable.

Not entirely correct, all cargos always have destinations, the only thing that can be changed is the way they are assigned them(although I don´t understand what changes either).

Do they work with ECS ?

Yes. Cargo distribution/destinations will always work with any GRFs you want to use.