Constant Clipper2Lib.dll Issues

  • A* version: 5.2.2 and newer
  • Unity version: 6000.2.6f2

Hi,

I’m getting compilation errors related to Clipper2Lib after installing A* Pathfinding Project Pro. The errors occur in TileHandler.cs:

Library\PackageCache\com.arongranberg.astar@1f4b22f35e70\Graphs\Navmesh\TileHandler.cs(4,19): error CS0234: The type or namespace name 'Clipper2Lib' does not exist in the namespace 'Pathfinding' (are you missing an assembly reference?)

Library\PackageCache\com.arongranberg.astar@1f4b22f35e70\Graphs\Navmesh\TileHandler.cs(279,19): error CS0246: The type or namespace name 'Clipper64' could not be found (are you missing a using directive or an assembly reference?)

Library\PackageCache\com.arongranberg.astar@1f4b22f35e70\Graphs\Navmesh\TileHandler.cs(1067,28): error CS0246: The type or namespace name 'Clipper64' could not be found (are you missing a using directive or an assembly reference?)

What I’ve tried:

  1. Removed any duplicate Clipper2 DLLs from Assets folder

  2. Reimported the package

  3. Restarted Unity

I’ve downgraded to v 5.2.1 and seems to be working fine but after that version, I cannot use A* because it gives this error. Any help would be greatly appreciated.

Thanks!

I’d try it in a fresh 6000.2 project, maybe even re-download as well to be sure.

I would like to implement this in an existing 6000.2 project and have tried redownloading.

Yes, the end goal is to get this functioning in your existing project, but for troubleshooting, can you see if you run into the same issue with a clean project? Also are you using any other Unity assets?

I have the exact same issue.

I am also using Storm asset from Procedural Worlds, they also use Clipper2Lib.dll, which is the cause of this issue for me .. I have tried tweaking assembly settings, based on some tutorials, but with no luck.

Any idea?

Ah I see. Thanks for that information. OP must’ve also had a plugin using this library. I’m assuming it works fine if you only either have Astar or the Storm asset?

Yes, that is correct.
It becomes issue when both are imported.

I have also messaged the Storm developers about it, no response yet.. but I’ll let you know if they come up with a meaningful solution/response.

1 Like

Thanks for that, keep us updated if they get back to you. Tagged Aron on this one as well. Since this is an external library I tried to web search and see if this issue may have popped up elsewhere but no dice :frowning: