When a visitor picks two places and sees No route found, it almost always means the two points aren't connected in the path network. This guide walks through the usual causes, quickest first, and shows you how to use Mapvera's built-in diagnostics to pinpoint the break.
Read the message first
| What the visitor sees | What it means |
|---|---|
| No route found between these places. | The two places aren't connected in the network — a gap, an island, or a stranded destination. |
| No step-free route — it can only be reached using stairs. | A normal route exists but every path to the destination uses stairs. You need a lift or ramp, not a network fix. |
| Est. time and a line draw, but the route looks wrong | The network connects, but in an unintended way — usually a junction welded where it shouldn't be, or a missing shortcut. |
Use the connectivity report
Every time Mapvera builds the routing graph it logs what it found to the browser console. Open the map with the developer console visible (F12 → Console) and look for the [mapvera-routes] lines.
-
Check the component count
The report lists segments, nodes, components and destinations. More than one component means your network is split into that many separate islands — and places on different islands can't route to each other.
-
Read the island warning
When the network is split, Mapvera warns you and lists which landmarks fell into which island. The two places that won't route will be in different islands.
-
Turn on Developer mode to see the nodes
With the map's Developer option on, a dot is drawn at every junction node. A junction you expected but can't see is the gap — the lines there didn't actually meet.
Work through the usual causes
-
A gap at a junction
Two lines that look joined but don't quite touch never connect. Connection is judged from stroke overlap, so nudge the ends together (or, as a last resort, widen the snap buffer). See "Make paths connect at junctions".
-
A disconnected island
A whole branch of the network that never joins the rest. Find where it should meet the main network and close the gap.
-
A stranded destination
The place is marked for wayfinding but no path reaches it, so a route can't arrive. Extend a path up to (or into) it. See "Make places routable destinations".
-
A destination not marked at all
If a place can't even be chosen as a destination, its landmark Action isn't set to Wayfinding.
-
A cross-level portal mismatch
A route that won't cross floors usually means the two portal ends don't share the same portal group, or one end isn't connected to its level's network. See "Route across multiple levels".
-
A step-free dead end
If it only fails in step-free mode, the destination is reachable solely via stairs. Add a lift or ramp — including a lift portal for any floor change. See "Set up step-free routes".
A wrong route, not a missing one
If a route draws but takes a nonsensical path, the network is connected in a way you didn't intend. Common culprits: two corridors that cross in the artwork but shouldn't join (they're welded at the crossing), or two separate stairs sharing the same portal group so the router "jumps" between floors where there's no real stair. Separate the geometry, or give each stair its own portal group.