Login

Recent searches

No recent searches

Search options

Only available when logged in.
lepoulsdumonde.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Small french Mastodon instance for friends, family and useful bots

Administered by:

Server stats:

52
active users

lepoulsdumonde.com: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.4

#godotengine

80 posts20 participants0 posts today
Public
GamingOnLinux

Sometimes developers put up blog posts talking about developing their game, but it's not every day you read about how they had to deal with earthquakes, cockroaches and broken bones. And yet, Clumsy Bear Studio still managed to get the Hungry Horrors demo out on Steam.
gamingonlinux.com/2025/04/eart

GamingOnLinux · Earthquakes, cockroaches and broken bones didn't stop the Hungry Horrors demo releasingBy Liam Dawe
#Steam#IndieGame#Upcoming
Public
GamingOnLinux

Sometimes developers put up blog posts talking about developing their game, but it's not every day you read about how they had to deal with earthquakes, cockroaches and broken bones. And yet, Clumsy Bear Studio still managed to get the Hungry Horrors demo out on Steam.
gamingonlinux.com/2025/04/eart

GamingOnLinux · Earthquakes, cockroaches and broken bones didn't stop the Hungry Horrors demo releasingBy Liam Dawe
#Steam#IndieGame#Upcoming
Replied in thread
Public
Dana

Anyway, I ended up making my own nav-mesh generator, to satisfy my need for nice and orderly shapes.

It uses the vertices and surface normals in a given mesh, to decide what surfaces should be part of the nav-mesh.

And far as I can tell, it's working beautifully.

Edited screenshot from the Godot Editor, showing a chunk of 3D terrain, with a series of planes running along the uppermost surfaces. They change color for green to red, based on the steepness of the surface. Above this is a rough chart with dot-product reference numbers, for determining the surface angle mathematically.
A screenshot of a navigation mesh applied to a piece of layered 3D terrain, showing the simple triangles that make it up.
As the prior image, but shows a sample path marked in magenta through the environment, referencing the nav-mesh
#GameDev#Godot#GodotEngine
Replied in thread
Public *
Dana

I appreciate your work, author of the NavigationRegion3D node, I really do... but can you please not be so opinionated about how much floating point precision you think people need? So much so that you even override the user's floating point precision settings to round numbers up to 2 decimal places?

I can't even set the cell size to 1/8th or 1/16th, without this tool rounding cells up to an irregular value that creates all kinds of artifacting and errors in the navmesh of my otherwise nice, orderly grid tiles.

I'm about to just write my own navmesh editor, I swear...

GIF
#GameDev#Godot#GodotEngine
Public
dbat :godot:

#GodotEngine #Blender #PipeLine

So, this is a little bit exciting. One can get Geo-Node *instances* into Godot, and they use the *same* mesh data!

It's all down to the "Export Geometry Nodes Instances" toggle in the import panel.
(Oh, and set "Modifiers" to "All Modifiers".)

Just be sure, in your Geo Nodes, to *not* use a "Realize Instances" node. (When you do, it's the same as joining all the meshes into one.)

🦇

Screenshot showing the Import panel for a blend file (in Godot) and it's scrolled down the Meshes/Export Geometry Nodes Instances
ExploreLive feeds
About