- For example, if you have several trains with "wait for full load" orders, these trains will lose a significant amount of reliability by the time they are finished loading, so that they will often require servicing again after loading, even if they serviced immediately before loading.
- When a major deadlock occurs on my network, it can take a long time for me to clear the deadlock. By this time, the reliability of the trains will often have dropped to 0%, even though the trains were not moving and waiting in front of red signals. This reliability of 0% makes it take an absurd amount of time for trains to clear the area that was previously deadlocked, especially if there is a long queue of trains.
For discussion about whether it is realistic or not for trains to lose reliability when not moving, please refer to my previous thread in the suggestions forum.
Also, when playing with breakdowns disabled, the reliability of trains no longer drops to 0% if you do not service them. Instead, their reliability stays constant.
This patch is for r17840. It is a very simple patch, as it does not contain any new code. Instead, it merely changes the order of execution of a small piece of existing code. The only thing I actually added was a comment.
I have also attached a Win32 binary and scanned it using VirusTotal. No infections were found.
Legal Information regarding the Win32 binary:
Please note that this program is copyrighted and licensed under version 2 of the General Public License, which means -among other things- that it is distributed without any warranty and you are using it at your own risk. Please see the file COPYING.txt for further information, which is included in the attached .zip archive. I have supplied this notice because it is mandatory according to section 1 of the GPL.