3D Pathfinding in Godot using Navigation Mesh

Learn how to add 3D Pathfinding in Godot using Navigation Mesh in your projects by following this simple Godot tutorial.
You'll learn how to move a KinematicBody using the Navigation and NavigationMesh nodes in Godot. You could use this technique in a number of different games, for example an RTS or MOBA in Godot where you click to move around the map, or for controlling enemy pathfinding AI in Godot.
---
Patreon: / codewithtom
Discord: / discord
Twitter: / codewithtom
Github: github.com/codewithtom

[@greg7987]

A clear, simple and amazing video for learning 3D pathfinding in Godot it is.

[@CodeWithTom]

Thank you Greg I appreciate that.

[@Crisisdarkness]

Wow, you came back with a great tutorial, thanks Tom

[@CodeWithTom]

Thank you I really appreciate it!

[@Gabirell]

Man… I was asking myself how this is implemented… (I’m a totally curious noob) and this seems so logic… saved for when I learn enough to understand it all. 🙏 thanks!!!

[@zyxoto1264]

The legend is back

[@CodeWithTom]

Haha thank you, good to be back!

[@malcolminthemetal4992]

This is great. Thank you very much.

[@__Rizzler__]

Broo thank you. 🙏🙏🌹❤

[@CodeWithTom]

You're very welcome :)

[@p.w.5813]

Thanks for that tutorial, but I still have a problem. My map is not flat like yours, it has hills and valleys. Is there a way to use path finding in such conditions?

[@al-oh8fq]

would it work with non static obstacles (like moving walls for example)?

[@mounaimchakroun6923]

Thank you so much

[@projectavalongame]

Hey mate thanks for the tutorial. Could you do a tutorial on making the character face towards the direction they are moving? I use the look_at function but it will look directly at where I clicked, so they will do a crab walk around an obstacle (move sidways while looking directly at the mouse click rather than the direction they are moving.)

[@Pirochiro]

Not sure if you figured this out but you if you look at direction instead of the target, the player will always look in the direction they are moving.

[@IMidgetManI]

He's back

[@CodeWithTom]

Glad to be back :)

[@tjspeirs75]

Great video! Am I right in thinking that that navigation code could be sectioned off into it's own script and used as a component? And then that component could just be dropped onto anything that needs it? Seems like it'd work great!

[@Alternalo]

What happens when you click on the top of the smaller cubes?

[@PunyFlash]

The ray is colliding with the collision shape of the kinematic body

[@Ceisriel]

is navmesh as useless as gmesh? in the sense it's only for demos or can you use that with actual 3d terrain sculpted in blender?

[@wexordante]

I can't search tutorial about turn-based strategy movement in 3d. If you can, pleace, say me what I should or create a tutorial in your chanel. Thanks )

[@chrisspamtest]

Anyone got this to work? Nothing happens when I mouse click.

[@ericomfg]

Where does global_transform come from?

[@thimkthimk]

It's the position of the node in world space. KinematicBody (now CharacterBody3D in Godot 4) inherits from Node3D and therefore can use it's properties, like global_transform.

[@bronxzoo8344]

nobody has anything that will help with enemy facing the player with navigation, Cane you help. Thank you.

[@zapman6528]

Make the enemy model a child of the kinematic, then through code have the model face the player. I cant help with the code part but thats how you'd have to organize it.

[@coder-serwin3545]

Bro can you make this with enemy that wants to follow player please

[@CodeWithTom]

Good suggestion :)

[@coder-serwin3545]

@@CodeWithTom :)

[@Arun--AK]

Start a new series to make TPS game bro

[@CodeWithTom]

I'd love to make a series on making a TPS, it's definitely on my list of things to cover.

[@zapman6528]

The code: extends KinematicBody export var speed = 10 onready var camera = $"../Camera" onready var navigation = $"../Navigation" var space_state : PhysicsDirectSpaceState var path = [] var path_index = 0 func _ready(): space_state = get_world().direct_space_state func _input(event): var mouse_event = event as InputEventMouseButton if mouse_event == null: return if mouse_event.pressed and mouse_event.button_index == 1: var from = camera.project_ray_origin(mouse_event.position) var to = from + camera.project_ray_normal(mouse_event.position) * 1000 var result = space_state.intersect_ray(from, to) if result.collider: path = navigation.get_simple_path(global_transform.origin, result.position) path_index = 0 func _physics_process(delta): if path_index < path.size(): var direction = path[path_index] if direction.length() < 1: path_index += 1 else: move_and_slide(direction.normalized() * speed)

[@p.w.5813]

Thanks for that tutorial, but I still have a problem. My map is not flat like yours, it has hills and valleys. Is there a way to use path finding in such conditions?

[@Ceisriel]

did you figure it out I'm asking everywhere and no one can answer

[@p.w.5813]

@@Ceisriel sorry mate, I didn't

[@Ceisriel]

@@p.w.5813 fortunately I did, you have to put your terrain mesh under the navmesh node, and if you can't do that, you right click on the main node of the terrain, and select "change type" you change it to navmesh and then click the bake mesh button , and then you need to re add all the collisions. It's very inefficient, slow and pretty much useless because if your terrain has more than 4k polygons the game engine starts to freeze or crash as it is baking