Seeker not responding to path request

Yes, could be InvalidOperationException as it is thrown from CircularBuffer.PopStart(), if length is 0.

We are using Unity 2022.3.22f1 and using IL2CPP scripting backend and .NET Standard 2.1

Our user base is mostly Android and all issues are reported are from Android devices.

The current issue is that we are in the middle of a feature sprint and not in a state to change Unity version which may invite compatibility issues with rest of our codebase and plugins. Also we normally don’t update to non LTS Unity versions and Unity 6 is still in preview. We are exploring possibilities of trying single threaded path finding. The most number of pathfinding units at a time in a scene averages at 150 and we are using a sequential Seeker system of around 35 Seeker pool as we only need path and movement is managed by us.

Last but not least, What are your thoughts on using single threaded path finding, if it is working for us?

Thank you

I see.
I think this is an IL2CPP bug. So upgrading to Unity 2023.2.19f1 would be a likely solution.

You can definitely go with single-threaded pathfinding if the performance is ok for you.
Try first with threads set to 1, and if you still get exceptions, set it to None.

That sounds complex. Sure you don’t want to use the AstarPath component directly, in that case?
You can use seeker.PostProcess(path) if you want to apply path modifiers on an already calculated path.

We indeed tried single threaded path calculation and performance downgrade is hardly noticeable, but fingers crossed for live test results. We have already rolled out single thread pathfinding internal test build to some of our users who are volunteering to debug the issue and waiting for their feedback. As I mentioned in my first post, this issue is yet to be reproduced in our QA or dev test environment.

We haven’t really checked the possibility of using Seeker.PostProcess(Path) for our use-case. Thank you for the advice. Will check it.

Thank you for the support

We found that the fix is there in Unity 2022.3.23f1 which is an update one above our current Unity version.

So there should be minimal impact on our current codebase and plugins with Unity 2022.3.23f1 update. We are trying that. But not sure why Unity is specifying(or fixing) this multiple times in later versions also. Seems like the issue is getting reopened in various later versions also. Even we tracked the fix back in a 2021 version also. Also I couldn’t find an issue tracker link to check what was the actual impact of the issue.

Again the process of testing itself is bit tedious for us to wait for the live users to respond with updated Unity build. Will keep you posted.

Thank you,

1 Like

Hi @aron_granberg, We updated to last Month’s latest LTS update for Unity 2022(2022.3.47f1) which seems to have fixed the threading issue in Android. Now pathfinding is working as expected in both iOS and Android for us using multithreading. Everything seems stable now. Thank you for your leads and timely support. We waited for 2 weeks for the live update for maximum user adoption. That’s why we took some time to reply.

2 Likes