![openttd signals examples openttd signals examples](https://i.pinimg.com/originals/d6/af/9b/d6af9beaef7b64b6b1a3bd52750008f0.jpg)
To have things work as designed, you need allowed yellow signals, YAAM acceleration model for trains, turned on looking at next signal and turned on allow slowing down in stations. Code need some refectoring, settings need refactoring, but things kind of work.Ģ) Nothing done yet, I need more free time.Īdvanced settings are mess.
OPENTTD SIGNALS EXAMPLES PATCH
In my opion this patch is best for speed limits in such situations.ġ) Functionality almost done. If we think about this, then we need something effective for certain speed limits. Also going too fast on brigdes is option for this. There are other options to include in hardcore mode - Train can derail on too sharp curve (for example train going 200km/h on 90°turn should derail instead of instant braking). This can happen if signals are too dense, because green signals have unlimited speed limit. Tl dr there will be unsafe switch button in setting for allowing trains to pass red light on signal.
![openttd signals examples openttd signals examples](https://wiki.openttd.org/uploads/en/Manual/Station%20roro%20single%20load%20pathsignals.png)
When trains have ability to brake, there is place for not braking on time. With more signal colors make braking more sense.Ģ) If we say, the physics is important here. Also useful thing here is my yellow path signal patch. You can literally put signal on every tile, do basic station scheme and you are making billions.ġ) Obviously some programming - making trains to compute braking distance, making them brake at right moment. Second - too easy track designing and signal designing. This doesn't look nice and behaves weird compared to reality. Everybody can notice, trains in trunk/stable openttd accelerate gradually, but brakes instantly. This patch tries to solve 2 issues that bothers me.įirst - decelerating.