Navmesh & Collision

When you use a Generate Marching Cube Surface node, collision will be computed on visible chunks. You can disable that by using a body instance with no collision:

Visible chunks being used as a source for collision means collision will have lower resolution the further away you move from the camera. This is not desirable when you have NPCs or other colliding bodies moving around the map.

To fix that, the plugin has Voxel Invokers: components you can add to actors to generate collision (or navmesh) around them.

Adding a voxel invoker

Add a new Box Invoker or Sphere Invoker to your actor:

You can then move/rotate/scale the invoker as needed.

Setting up a Physics Scene

To generate collision or navmesh from invokers, we need to setup a new physics scene.

First, create a new Voxel Physics Scene in your content browser:

This is an empty asset that will be the link between nodes creating physics objects, and nodes processing them.

Then add a new Generate Marching Cube Collider node, link its distance & assign the physics scene to it:

This node will now generate marching cube colliders in the physics scene, on demand. We now need a node that will take these colliders & create actual collision components from them.

To do so, add a new Generate Collision from Physics Scene node, and set its physics scene:

Debugging

By default, no collision is generated in the editor. You can use voxel.collision.EnableInEditor 1 in the console to enable collision generation in the editor.

Once this is done, you should be able to see colliders generated when switching the viewport to the Player Collision view: