It's very strange that I haven't received much feedback about PathFinder. As a path-finding solution I have expect there should be a lot of bug, little tweak that can improve the package. But that hasn't been the case.
Anyway, I have just submitted a new update to AssetStore. Nothing new, just a series of bug fix following recent feedback I got from user. Thanks to AssetStore sales, now it's finally being used by someone who is not me. Anyway, the list of the fixes included in the update are as follow:
- fixed bug where clustering error occur when the are specified doesn't have similar widht and length.
- fixed bug where agent would stop before just before reaching final waypoint.
- fixed bug where node generation would encounter error when negative start value for x and z is specified for the area.
- example scripts (chase.js, patrol.js and RTSUnit.js) is now compatible for iOS compilation.
To be honest I don't think path-finding solution is no longer as in demand as it used to be now unity has their built-in path-finding solution. I'm sure Unity will keep on improving the built-in path-finding. That makes me wonder how helpful will a 3rd party solution like PathFinder is going to be come Unity4 in the near future. For that reason, I don't think there's a lot sense in putting more effort into improving this package.
Anyway, I hope user who have made the purchase got what they are looking for.
Edit 1Sep: A hot fix(v1.0f2) has been uploaded and now live on AssetStore following a bug report.
Edit 1Sep: A hot fix(v1.0f2) has been uploaded and now live on AssetStore following a bug report.