2D Tilemaps not working

[aron_granberg]

@Chazz

I’m really struggling to use the plugin. I don’t see many updated tutorials of how to use a recent version and even something which feels like it should be a single line of code like moving the center of the graph seems incredibly complex (my world is procedurally generated and I only want to generate a specified area around the player from time to time).

This seems like you want to use the ProceduralGraphMover, to keep the graph centered on the player. It’s an out-of-the-box solution that just requires you to assign the “center” GameObject.

See the bottom of this page Moving a graph at runtime - A* Pathfinding Project

@Chazz

I have a single Recast Graph for now (2D) and it tends to find the map object colliders (e.g. trees, rocks etc.) well enough. However no matter what I’ve tried, I cannot get it to take the tiles that exist on each of the tilemap layers (separate GameObjects for each terrain type) and make them show up in the generated NavMesh with the proper tags (or at all even without tags).

I cannot see anything immediately wrong in your setup. Have you checked the Recast2D example scene for reference? That one uses tilemaps. None of them use any tags, but I just tried to add a RecastNavmeshModifier to the “Walls” tilemap and make the walls use a different tag, and that worked perfectly.

Note that the recast graph only supports colliders as the source information in 2D mode. This means your tilemaps need colliders for them to affect the system. If you have composite colliders, they need to be marked as Polygonal, not Edges (but this doesn’t seem to be an issue in your case).

@Chazz

They didn’t compile out of box due to repeated definition includes in both assembly definition files (had to manually remove to fix)

Interesting. I’ve only heard of one other user that saw this. And in their case, it was something else in their project (perhaps another plugin, unclear). Issues importing version 5.4.5 via Unity Package Manager with Unity 6 - #4 by aron_granberg

This package doesn’t include duplicate assembly definitions by default.

@Chazz

They don’t seem to support URP (I have pink textures everywhere)

Yeah. The unity asset store sadly doesn’t have a good workflow for supporting this without a lot of manual pain. I recommend running the automatic URP material converter after you import the samples.

@Chazz

Incompatible with new Unity Input system which I’m using (spamming errors in most scenes every frame)

True. I’ll see if I can get a compatibility layer in place so that it can support both input systems at the same time.

@Chazz

Very often it will simply stop drawing the graph whatsoever which makes it effectively impossible to know if something I’ve done even works.

Even if I haven’t changed anything since the last run, it will simply stop rendering (even if I use the rescan button and use Solid Colours). Turning random things off and on a bunch of times will sometimes fix it, sometimes not.

That’s strange. When this happens, can you verify that:

• Show Graphs is enabled
• Gizmos are enabled in the scene view
• Clicking on the small “i” button at the top right corner of the graph inspector shows that the graph has nodes in it.

Are you using any non-standard post processing effects that could be interfering?