zypa wrote:Thank you! Now I know it. Anyway: Is there any documentation?
There currently is no documentation except what michi_cc has posted in this thread about this patch. However, this information is partially outdated, as he has released many new versions in the mean time. I think the best piece of information is
this post by michi_cc which shows you how you can build a bi-directional station with the new PBS signals.
zypa wrote:Do all signals have to be PBS signals? Or just one signal per PBS block?
It is enough for one signal of a PBS block to be PBS, in order to make all other signals also behave as PBS signals. However, I recommend you upgrade all signals to PBS. In my opinion, there is no reason to use the old signal types, unless you want to do exotic things like priority lines using pre-signals.
zypa wrote:Does YAPP work exactly like the ttdpatch PBS?
I think this patch is similar to TTDPatch with
through-signals (alpha feature). But I haven't been playing much TTDPatch, so I don't know if there are any differences, except for the graphics of the through-signals.
zypa wrote:computing time compared to presignals
When I play ottd online I do get some problems with lagging. (Better: I do not have any problems, my patner has some, I host the game)
As far as I know ships with long routes without shipyards and buoyes are a reason for that problem.
Can big YAPP crossings be a problem, too?
I'm not sure about multiplayer, but in single-player, large YAPP junctions are no problem. The main performance problem currently is that trains waiting at a red signal for a free PBS path are big performance hogs, because they try to find a new path every tick (=about 40 times per second). However, michi_cc already stated that he would address this issue in his next release.
zypa wrote:Bi-directional double tracks
The openttd wiki says that these tracks are not possible with this patch.
WIKI LINK wrote:his implementation does not support bi-directional double track due to lack of support of "weak" reservations.
Is this still correct? Will these "weak" reservations be implemented?
I am the one who wrote that wiki article. As far as I know, michi_cc has no intention to implement a train scheduler which requires weak reservations. I plan to implement this myself if necessary, but the current YAPP pathfinder/reservation system requires many more optimizations before it is ready for these additional features, in my opinion.