ProceduralGraphMover throws exception on Start when no target is assigned [BUG?]

This is more like a suggestion to the script of the procedural mover, but for me, it seems like a bug.

When no target is assigned, it throws an exception on Start because at the start, UpdateGraph is called. However, in Update, there are checks for invariants, which include the target being null, so it does nothing, which seems correct.

I’m wondering whether this is intended to call UpdateGraph in Start or not.

My use case is to have an AstarPath on the same object as the GraphMover, but the target transform is spawned later, after the navmesh is calculated, so I assigned it later in the process.

Which version are you on? I’m not seeing this on 5.4.6. I started mine with nothing assigned to the transform, but no errors.

It’s 5.4.6 as well. I tried it again and it throws error. Check the code there is call to UpdateGraph in Start method that does not check target not null so it should throw as well.

Which Unity version?

It’s 6000.3.2f1.

I did this on 6000.3.4, which I wouldn’t think is far off enough to cause the issue. Can you send a repro project of this happening?