Skip to content
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

Ship automatic service causes them to be stuck in a loop #8022

Open
SamuXarick opened this issue Feb 25, 2020 · 2 comments · May be fixed by #12170
Open

Ship automatic service causes them to be stuck in a loop #8022

SamuXarick opened this issue Feb 25, 2020 · 2 comments · May be fixed by #12170
Labels
bug Something isn't working component: pathfinder This issue is related to Pathfinder

Comments

@SamuXarick
Copy link
Contributor

SamuXarick commented Feb 25, 2020

Version of OpenTTD

OpenTTD 20200223-master-gd1b7eb2de1 - Resolved by #11768
OpenTTD 20240128-master-g90084dc74d

Expected result

Ships either do service or not.

Actual result

Ships are stuck in a loop due to automatic servicing distance limit triggering it. They can't decide whether to head to ship depot or the dock, which are opposite directions.

Steps to reproduce

Charningstone Transport, 1960-11-25.zip - Resolved by #11768

Charningstone Transport, 1964-05-30.zip - Not resolved

@SamuXarick
Copy link
Contributor Author

SamuXarick commented Feb 25, 2020

I have a fix for this which involves using the pathfinder, but the idea has been rejected in the past, which was before ship path cache. Is it perhaps worth approaching it again?
https://github.com/SamuXarick/OpenTTD/tree/find-closest-reachable-ship-depot

@SamuXarick
Copy link
Contributor Author

SamuXarick commented Jan 28, 2024

Just found an edge case where this is still not resolved. See updated main topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component: pathfinder This issue is related to Pathfinder
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants