Errors keep popping up in edit mode

I keep getting the following errors in edit mode. I’m not sure why.

NullReferenceException: Object reference not set to an instance of an object
AstarPath.OnDrawGizmos () (at Assets/AstarPathfindingProject/Core/AstarPath.cs:773)
UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal(RenderPipelineAsset, Camera[], IntPtr, AtomicSafetyHandle) (at /Users/builduser/buildslave/unity/build/Runtime/Export/RenderPipeline/RenderPipelineManager.cs:67)

and

NullReferenceException: Object reference not set to an instance of an object
Pathfinding.RVO.RVOSimulator.OnDrawGizmos () (at Assets/AstarPathfindingProject/RVO/RVOSimulator.cs:138)
UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal(RenderPipelineAsset, Camera[], IntPtr, AtomicSafetyHandle) (at /Users/builduser/buildslave/unity/build/Runtime/Export/RenderPipeline/RenderPipelineManager.cs:67)

Everything works fine in play mode, but these errors can get a little spammy at times. Any ideas?

Hi

Which version are you using?
Do you think you could post the contents of the lines the error is referring to? The line numbers change all the time so it’s hard for me to know exactly where they are coming from.

Sure! In both cases, the line causing the error is:

if (Event.current.type != EventType.Repaint) return;

Thanks!

And the version you are using?

Right. Sorry. 4.3.10.

Do you think you could try 4.3.13? There have been a few fixes related to render pipelines since 4.3.10.
See https://www.arongranberg.com/astar/download

I’m currently using 2019.2. Maybe 4.3.12 instead?

Hmm. 4.3.10 isn’t really compatible with 2019.2 either though. The whole 4.3.x branch requires 2019.3. At least I thought so, if 4.3.10 works with your version then 4.3.13 will probably work as well.

Sorry for the delay. I wanted to back up my project before importing the new version. The new version gives me the following error:
Assets/AstarPathfindingProject/PackageTools/Editor/EditorBase.cs(23,20): error CS0103: The name ‘EditorResourceHelper’ does not exist in the current context

Since the errors aren’t really causing any run time issues, I suppose I can just deal with them until such time as I can safely upgrade to 2019.3.

I’ve upgraded to 2019.3 successfully and all of the above mentioned issues are resolved with 4.3.13. Thanks!

1 Like