New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aircraft autoseeking depots result in out-of-range condition #5405
Labels
flyspray
This issue is imported from FlySpray (https://bugs.openttd.org/)
Comments
Pikka wrote:
Attachments
This comment was imported from FlySpray: https://bugs.openttd.org/task/5405#comment11798 |
michi_cc closed the ticket. Reason for closing: Fixed
This comment was imported from FlySpray: https://bugs.openttd.org/task/5405 |
DorpsGek
added
flyspray
This issue is imported from FlySpray (https://bugs.openttd.org/)
Vehicles
labels
Apr 7, 2018
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Oct 2, 2018
…next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Oct 5, 2018
…next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Nov 6, 2018
…next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Jan 12, 2019
…next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Jan 25, 2019
…next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Mar 1, 2019
…next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Apr 1, 2019
Determine the correct last and next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Apr 11, 2019
Determine the correct last and next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Apr 13, 2019
Determine the correct last and next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
SamuXarick
added a commit
to SamuXarick/OpenTTD
that referenced
this issue
Jul 17, 2019
Determine the correct last and next destinations and then ensure these are within range of each other This fix is to avoid out of range when using service at nearest hangar orders
LordAro
pushed a commit
that referenced
this issue
Nov 2, 2019
douiwby
pushed a commit
to douiwby/OpenTTD
that referenced
this issue
Apr 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pikka opened the ticket and wrote:
Reported version: trunk
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/5405
The text was updated successfully, but these errors were encountered: