Error after upgrade to A* 5.3.3 and Unity6

  • A* version: 5.3.3
  • Unity version: 6000.0.38f

Hi there,
We used Unity version 2021.3.36f and A* version 4.3.47 and everything worked fine.
Now we are in the process of upgrading our project to the versions above.
Unfortunately when using Scan from the AstarPath component we get the following error. It happens nine times in total for our current world.

Vertex has multiple shared edges. This should not happen. Navmesh must be corrupt. Trying to not make it worse.
0x00007ffa94cb727e (Unity) Stacktrace::GetStacktrace
0x00007ffa932120ea (Unity) DefaultBurstRuntimeLogCallback
0x00007ffa92b3cc9a (Unity) BurstCompilerService_CUSTOM_RuntimeLog
0x00007ffa55c3ab20 (791a93ac107c6c7e06899ffcd2a0f3e) Pathfinding.Graphs.Navmesh.Voxelization.Burst.JobBuildMesh.CanRemoveVertex (at D:/Projects/Persist_copy/NightFall/server/Assets/Shared/Modules/AstarPathfindingProject/Graphs/Navmesh/Voxels/VoxelMesh.cs:356)
0x00007ffa55c3bab5 (791a93ac107c6c7e06899ffcd2a0f3e) Pathfinding.Graphs.Navmesh.Voxelization.Burst.JobBuildMesh.RemoveTileBorderVertices (at D:/Projects/Persist_copy/NightFall/server/Assets/Shared/Modules/AstarPathfindingProject/Graphs/Navmesh/Voxels/VoxelMesh.cs:288)
0x00007ffa55c4df6b (791a93ac107c6c7e06899ffcd2a0f3e) Unity.Jobs.IJobExtensions.JobStruct`1<Pathfinding.Graphs.Navmesh.Jobs.JobBuildTileMeshFromVoxels>.Execute(ref Pathfinding.Graphs.Navmesh.Jobs.JobBuildTileMeshFromVoxels data, System.IntPtr additionalPtr, System.IntPtr bufferRangePatchData, ref Unity.Jobs.LowLevel.Unsafe.JobRanges ranges, int jobIndex) → void_0d64390541958b43604801c180219108 from UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null (at D:/Projects/Persist_copy/NightFall/server/Library/PackageCache/com.unity.burst@7a907cf5a459/.Runtime/unknown/unknown:0)
0x00007ffa55c380bd (791a93ac107c6c7e06899ffcd2a0f3e) c7bd43dad8afab74e2910a0eea3eeaf4
0x00007ffa9355f115 (Unity) ExecuteJob
0x00007ffa935601ad (Unity) ForwardJobToManaged
0x00007ffa9355b9d9 (Unity) ujob_execute_job
0x00007ffa9355ad94 (Unity) lane_guts
0x00007ffa9355e459 (Unity) worker_thread_routine
0x00007ffa9375435d (Unity) Thread::RunThreadWrapper
0x00007ffaf6d57374 (KERNEL32) BaseThreadInitThunk
0x00007ffaf6e9cc91 (ntdll) RtlUserThreadStart

Any hints on what might be happening here?
Is it possible for us to pinpoint the error to a world position at our side?

If you haven’t already update your Burst package? Looks like that may be what’s going on here.

Thanks for your answer.
com.unity.burst is at the latest version 1.8.19

We found a workaround.
Decreasing the Voxel Size from 0.125 to 0.1 in the Rasterization settings makes the errors disappear.
Maybe this helps in finding the root cause of the issue.

Interesting :upside_down_face: Thanks for posting that workaround! I’m gonna tag @aron_granberg on this to take a look. Never seen this particular issue and can’t find much on it myself.

No idea what could cause that… It sounds like an edge case. I haven’t heard of any other users reporting this. If you get it again after tweaking the voxel size, let me know.

Thanks for looking into the issue! We will keep you updated.
If you could give us some hints on how to locate the world position where the issue occurs, we might be able to create a small repo. We found out that moving some objects in the scene a bit also “solves” the issue.