Godot 4 NavigationAgent with Tilemap

Moguai

Hello all, I'm wondering if it is possible to handle the following problem with the new Navigation Server in Godot 4:

I have a characterbody in a scene, a tilemap and a NavigationRegion. I have two layers for the tilemap, one for floor, one for walls. Character should be moved by mouse click. The wall layer tiles have collision layers, so that the character can not run through it. This works so far.

But now I'm a little bit confused how to handle this problem: I want to use the new Navigation system, and with the agent it works as well, but the character bumps into the wall tiles if they are in the way of the path. The final question: Is it possible to automatically detect collision with tilemaps within the path finding? Or do you have to set up navigation for each tile?

What would be the best workflow to do this.

My idea would be: allow navigation over the complete scene (maybe I don't need a navigation region at all?) Add tilemaps with collision and without. Automatically let the navigation agent detect the collision with the tiles where collision is set. On click the character will walk around all walls/tiles with collision.

I'm not sure if the current navigation region overwrites all the tile settings (including navigation).

At the end it would be great to allow explicitly everything for navigation, except collision tiles (without setting navigation AND collision for all tiles)

Any idea what is the best way to solve this?

Moguai

I've made some progress on it, and it seems to work somehow...

But I don't get it to work properly. This is my scene.

NavgationRegion is set over nearly all the tiles

Tilemap: The floor tiles have no collision shape, but naviagtion shapes, the white walls the other way round

The water sink is the staticbody with collision shape

The agent has the default properties. I've played a little bit with them, but it is hard to understand what excatly these properties are doing..

I've made a video about the current behavior, which shows, that in parts is working but not in call cases:

https://youtu.be/stmCVpRNy60

Code of the character is quite simple

extends CharacterBody2D

const SPEED = 300.0
const JUMP_FORCE = -400.0

@onready var nav_agent: NavigationAgent2D = $PlayerNavigationAgent

# Get the gravity from the project settings to be synced with RigidDynamicBody nodes.
var gravity = ProjectSettings.get_setting("physics/2d/default_gravity")

var target = Vector2()
var moving = false

@onready var line: Line2D = get_node("../Line2D")

func _ready():
	target = position;
	
func _unhandled_input(event):		
	if event.is_action_pressed("click"):
		target = get_global_mouse_position() 		
		moving = true
		nav_agent.set_target_location(target)			

func _physics_process(_delta):	
	if moving:
		if nav_agent.is_target_reached():
			moving = false
		else:	
			var target = nav_agent.get_next_location()
			var vel = global_position.direction_to(target) * SPEED
			nav_agent.set_velocity(vel)
			var linePoints = nav_agent.get_nav_path()		
			line.points = linePoints

func _on_player_navigation_agent_velocity_computed(safe_velocity):
	motion_velocity = safe_velocity;
	if position.distance_to(target) > 5:
		moving = true				
		move_and_slide()
	else:
		moving = false

Any tips what properties I have to tweak? Or what I'm doing wrong?

Moguai

So to keep that up to date: I've had some strange side effects regarding my last video and I eliminated nearly everything to get rid of it. After setting it up with nearly the same scenes and settings the basic navigation is now working better, but still has some issues for tilemaps: I've made a new video.

I've let it all to "default" settings, means NavigationObstacle2D->Radius is set to "EstimateRadius = true".

For the water basin it looks fine (not perfect, but good).

The tilemap wall still has some issues.

The main problem for the wall is that when you have a path straight trought the wall it does not work.

I've played a little bit with the NavigationObstacle radius settings of the tilemap, but this brought no improvements (or better: resulted in other issues with path finding)

For me now it is okay, as I think this will get some love with next releases, but there still some improvements to do.