You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[17:46:03] when a train comes into depot, only the first engine gets date_of_last_service updated.
[17:46:55] when a consist is split into vehicles, the other engines have date_of_last_service not updated
[17:47:13] equal to day of build
All the engines in consist should have the date of service updated.
Why is it important.
When all the trains should change a livery after a certain date, it looks very silly when they do a change on the fly (on a speed on over 100km/h). So I decided to change current date check to date of last service. Unfortunately it works only for the front engines, but not the other.
It is possible to check the date of the first engine, but when the train is split into parts (to assemble several smaller trains from one large train), the engines become magically transformed into old one. It looks stupid, because it was updated together with the old front engine.
To fix it the date_of_last_service should be updated for all the engines in consist.
In case date_of_last_service is stored for wagons, it should be updated for them too.
George opened the ticket and wrote:
Reported version: trunk
Operating system: Windows
This issue was imported from FlySpray: https://bugs.openttd.org/task/5550
The text was updated successfully, but these errors were encountered: