Megacrush Unity Assets
Runtime Navmesh Baker
Runtime Navmesh Baker
  • Runtime Navmesh Baker User Manual
    • Introduction
    • Technical Details
      • Input System (Old)
    • Video Tutorials
    • Getting Started
    • Nav Mesh Baker Component
    • Installing Samples
      • Text Mesh Pro Essentials
      • The Runtime Navmesh Baker Demo scene
      • Scene View Overlays
      • Runtime Navmesh Baker Configuration
    • Preparing a scene for Runtime Navmesh Baking
      • Navmesh Render Geometry
      • Use Primitive Colliders instead of Mesh Colliders
      • Allow Read/Write access to ALL meshes used for Mesh Colliders
      • Disable Batching Static for Scene Elements
      • Page Third Party Mesh Combination Tools1
    • NavMeshBaker API
    • Frequently Asked Questions
    • Extras
      • ClickToMoveController
Powered by GitBook
On this page
  1. Runtime Navmesh Baker User Manual
  2. Preparing a scene for Runtime Navmesh Baking

Use Primitive Colliders instead of Mesh Colliders

The simple version is that in order to bake the navmesh at runtime, Unity requires read/write access to any meshes that use Mesh Colliders in your scene.

The best option for most geometry is to use primitive colliders (Box Collider, Capsule Collider) for your scene geometry. This is more performant in general, and is recommended for best performance.

PreviousNavmesh Render GeometryNextAllow Read/Write access to ALL meshes used for Mesh Colliders

Last updated 1 year ago