planetmaker wrote:

Only checks for void orders and invalid stations are done prior to this - too few orders and duplicate entries after this. Yet this sort order is ok for me.

I'd go for a clearer warning message, though, which explicitly tells about the too short landing strip.

This comment was imported from FlySpray: https://bugs.openttd.org/task/6009#comment13297

3298 wrote:

Wrt. message priorities: I'm not too sure whether this one or "too few orders" should have higher priority, but other than that, a fast plane on a small airport should have a low priority. After all, the plane can use the airport (okay, with a risk), so the order is not as pointless as e.g. one with a station without any landing strip.
Wrt. message text: "{VEHICLE} has a too small airport in its orders" sounded weird to me, so I substituted "too small" for "unsuitable". I undid that in the attached version. I'm still not satisfied because now it feels like we're telling the user that the plane cannot land somewhere at all. If you have a better text, I assume you know how to deal with language files. ;)
Something else I forgot: if _settings_game.vehicle.plane_crashes is 0, not only the random crashes, but also the fast-plane-on-small-airport crashes are disabled. The warning would have triggered still, so I inserted the missing check for that in the attached version.

Attachments

• fastplanewarning.diff (1.61 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/6009#comment13298

3298 wrote:

Crap, uploaded the old version again, and I still do not know how to edit comments (if that's possible at all)... let's try again.

Attachments

• fastplanewarning.diff (1.66 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/6009#comment13299

planetmaker wrote:

Thanks for the patch and the update, I missed that setting for no crashes, too :)
You missed the place where the warnings are cleared in DeleteOrderWarnings (see r26566).

To answer your other question: unless you're an admin of the bug tracker you cannot edit entries. Amending new versions to the tracker is quite fine

This comment was imported from FlySpray: https://bugs.openttd.org/task/6009#comment13300

planetmaker closed the ticket.

Reason for closing: Implemented

In r26566

This comment was imported from FlySpray: https://bugs.openttd.org/task/6009