Troubleshooting
What the tool's messages mean and what to do about each.
Capture
"Add your Google Maps API key" Capture has no key. Press Add API key. See API key and cost.
"Tiles could not load. Check your connection and that your Google Maps key has the Map Tiles API enabled." The first tile request failed. Common causes are a key without the Map Tiles API, a key restricted to other sites, a Google Cloud project without billing, or no connection. Fix the cause, then press
Retry loading, or Update key to enter another key.
"Failed to initialize the 3D capture view. WebGL may be unavailable." The browser could not start WebGL. Try another browser, or switch hardware acceleration on in the browser's settings.
A building is hollow at the edge of a shot Its walls facing the camera are missing, so you see through it. The near plane cut it: the street bends toward the camera's side there. If the settings show "The near plane cuts blocks in shots …", press the
set near to … button under it (with Clip to blocks on) and take the capture again.
The capture pauses by itself A capture runs only while its window is visible and in front. Bring the window back and it continues; nothing saved is lost.
"N need retry" Some shots did not get their tiles in time. Resume remaining N takes them again. If it keeps happening, raise Tile timeout (ms) under
Advanced Timing.
"Capture blocked: …"
Only photographed side could not be applied safely to this path. Press Turn off Only photographed side and check the preview: things on the camera's side of the street may then show.
"Settings could not be saved: …" The browser refused the write. The text after the colon is the reason it gave. Reload the path and try again. If the browser's storage is full, delete captures you have already exported.
Buildings are sliced off at the edge The clip follows the lot lines. Add an Expand Lots step to the path, or switch Clip to blocks off.
Stitch
"This browser doesn't support OffscreenCanvas — stitching is unavailable" Use a current version of Chrome, Edge, Firefox or Safari.
"The stitch worker crashed" This can happen when a capture needs more memory than the tab is given. Look at the memory estimate in the settings column. A narrower capture width, or a shorter path, makes a smaller stitch.
"N images are missing; those placements are skipped." The capture does not hold every shot. The print has holes where they belong. Resume the capture to fill them, then stitch again.
Many suspect seams Open Reports and read the reasons. Low texture means there was little to compare: blank walls, sky, water. That is expected there. Where suspect seams fall on ordinary facades, look at those shots in Capture. More overlap between shots (h-overlap (%)) gives the check more to compare.
The browser warns about memory when downloading Chrome and Edge write the ZIP straight to disk. Other browsers have to build it in memory first, which a large print can exceed. Download the panels one by one with Download panel N instead.
Library and Plan
The Library is empty Paths and captures live in the browser and at the address where they were made. Another browser, another profile, a private window or another address has its own, empty Library. Cleared site data is gone.
"Saved path not found" The link points at a path that has been deleted from this browser.
"Region not available for planning" The path belongs to a region this build has no data for. It can still be captured and stitched.
"This path has no planner steps" The path came from a capture plan file. It can be captured, not edited.
"The planner failed to load." (or the capture view, or the stitching view) Press Reload page. If it comes back, the message under the title says what failed.