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
If rail type A is compatible with rail type B, rail type B is not by definition compatible with A. For example: normal trains may drive on 'high-speed rail', but high-speed trains not on normal rail. Of course this requires NewGRF railtypes.
A location where this may become an issue is the GetTrainForReservation function in pbs.cpp Here, the compatible rail types of the start tile instead of those of the vehicle are used. This may be logical, since the vehicle isn't known yet, but it can produce errors when the compatibility of the rail type differs from that of the vehicle.
Currently, this is of course a non-issue. It may however become one when NewGRF-controlled rail types are introduced. Therefore I wanted to file a bug report here, so the latent problem would not be forgotten.
Swallow opened the ticket and wrote:
Reported version: trunk
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/2685
The text was updated successfully, but these errors were encountered: