Hey,
I work for the company that makes the package in question so just wanted to chime in as I don’t think this is a problem for Aron to fix, although I noticed a few undocumented breaking changes.
-
Node.pathID is now internal (this makes it difficult to work out if a path that is currently cached is the same as a new path), I could do a comparison on the hashcode possibly to compare 2 paths… any advice on this one would be good
-
Node.duration is now internal, I can remove the action exposing that if users shouldnt be accessing it
-
Node.Destroy is now internal, not entirely sure how to best deal with this, I am happy to remove the action if end users should no longer be able to destroy nodes directly?
-
Node.RecalculateNodeConnectionCost no longer seems to exist
Any advice on the points above would be great Aron.
In terms of the RVOController conflict bits, it sounds like you have certain pragmas active in the actions package which will add polyfill classes to the free version so the actions dont cause compilation errors with the missing pro features (they would actually blow up if you tried to use pro actions with a free A* version).
Anyway we are updating the actions our side to account for the latest changes but ideally dont want to delete actions if there is a workaround for some of the points above.