New Feature: Unbuncher about expressbusservices

[Vectorial1024]

The current idea:

I do not set a hard limit on how long it should wait, but I have a separate curve X that will change as things change. When X intersects with T, then it means we have "found a solution", and the bus can depart.

X is a function of the "progress distance" to the previous bus in the line. If the distance is low (ie, previous bus has just departed), then X is large, and it decreases hyperbolically until it reaches the "safe unbunching distance" giving the standard waiting time of 64.

As a result, the unbunching distance is implicitly defined, and it tries to maintain a progress distance of approx slightly smaller than 100% / # of buses percent, which will (hopefully) collapse to an approx equal to the value itself of bus interval due to road conditions.

This provides some reasonable generality to the minimum-distance problem of unbunching. (The maximum-distance problem is rather trivial and is solved at #29)

(Hint: if anyone could make a framework to persistently remember the unbunching time beyond 255, then this would probably be much more powerful...)

[Vectorial1024]

However, while this works for low-budget cases, this breaks the high-budget situation: buses now wait too long to depart when there are many buses queued behind the terminus.

Therefore, one way to deal with this is to use the progress distance list and see if the terminus is crowded. If it is crowded (i.e. it is a high-budget situation), then don't use the unbunching soft limit. Let the vanilla decider take over instead.

[Vectorial1024]

This is now on Steam; closing.