# Render Meshes vs Physics Colliders

Unity’s `NavMeshSurface` supports two source modes:

* **Render Meshes** — Bakes directly from mesh data. Requires meshes to be marked *read/write enabled* and breaks on static batching.
* **Physics Colliders** — Bakes from colliders in the scene. This is safer, faster, and does not require mesh read/write access.

#### Runtime NavMesh Baker behavior (v1.3.0 and newer)

* **DynamicNavMeshSurface automatically overrides surfaces to use Physics Colliders.**
* This avoids common errors like:

  > *“Source mesh XXX does not allow read access.”*
* If you intentionally want to bake from Render Meshes, you can still switch the `NavMeshSurface` manually — but you must ensure all contributing meshes are readable.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://megacrush.gitbook.io/megacrush-unity-assets/runtime-navmesh-baker/runtime-navmesh-baker-user-manual/frequently-asked-questions/render-meshes-vs-physics-colliders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.