Troubleshooting

Each entry gives the symptom, then the fix. Messages in quotes appear in the Worldprint window or in the Console.

Baking

“Worldprint cannot draw this scene, because it has no ground”

Symptom. Bake Scene Map stops with a red message about a scene with no ground.

Fix. The bake needs an active Terrain, or ground meshes marked with Map Ground. Enable the Terrain, or add a Map Ground component to the meshes of your ground (Detect Objects adds it to the large ones). Then bake again.

“Worldprint is already baking a map”

Symptom. A warning in the Console when you press Bake again.

Fix. Wait for the running bake to finish, or cancel it in Unity’s Background Tasks window.

“The bake stopped on an unexpected error” or “the terrain was refused”

Symptom. The bake fails with a red message that ends with “The previous map, if any, is unchanged.”

Fix. Your last good map is still there. If the message says the terrain was refused, read the reason that follows it and fix the terrain. For an unexpected error that comes back, report the message with your scene.

The map went to the “Untitled” folder

Symptom. Warning: “The scene is not saved, so the map went to the Untitled folder.”

Fix. Save the scene, then bake again.

“The terrain is larger than … samples a side”

Symptom. A warning after the bake says the map uses a coarser grid.

Fix. Nothing is broken: the relief is just less detailed than the terrain.

“The map is older than the scene”

Symptom. A yellow box in the Worldprint window.

Fix. Objects, components or terrains changed since the bake. Press Rebake.

Seeing the map

The map is empty or black in Play mode

Symptom. The map object is there, but nothing is drawn.

Fix. Check these in order:

Select the map. If the inspector says “No map yet”, it has no style and no tile source. Bake the scene and use Add Map to Scene, or pick Online Tiles for a real-world map.
If a style path is set, check that the file exists. A relative path is looked up in StreamingAssets first, then in the project folder. A wrong path throws an error in the Console when Play starts.
Check that the map has a size on the Canvas (the full-screen map fills it; a minimap is 280 by 280).
Look at the Console for warnings that start with “Worldprint:”. They name what the style could not load.

The map is not visible outside Play mode

Symptom. The map object is in the scene, but the Game view shows nothing until you press Play.

Fix. This is expected: the map in the scene is drawn while the game runs. To see the result without playing, open Window > Worldprint. Its preview shows the baked map with the theme you picked.

Some parts of my style are not drawn

Symptom. The Worldprint window shows “This style has parts the map does not draw”, and the Console has warnings like Worldprint: layers[3].line-dasharray: not rendered yet.

Fix. Each warning gives the place in the style and the reason. The map skips that part and draws the rest. Remove it from the style, or accept the difference. The list of what is drawn is in Your own style. In code, the same messages arrive through MapView.Diagnostic (see Advanced: queries, styles and editing).

Input

The map does not react to the mouse

Symptom. You cannot drag, zoom or click the map in Play mode.

Fix. The map takes its input from Unity’s UI EventSystem. The scene needs one EventSystem object, with an input module that matches your input setting (Input Manager or Input System). Add Map to Scene creates it if the scene has none. If you built the canvas yourself, add one with GameObject > UI > Event System. Also check that no other UI element with Raycast Target on covers the map. A round minimap ignores clicks in its corners, on purpose.

The map cannot be dragged while it follows an object

Fix. This is expected: while Follow is set, the followed object decides the centre. Clear Follow to drag the map again.

Positions and markers

“This map has no scene placement”

Symptom. An exception or error with this text appears when you pass a scene position to a map. Related messages: “the map cannot follow …”, and “annotations at scene positions are not drawn”.

Fix. A scene position (a Vector3) only means something on a map baked from your scene, which knows where the terrain lies. A real-world map does not. On those maps, give longitude and latitude instead, as in MapCoordinate.LngLat(lng, lat). See Coordinates.

“A longitude and latitude has no scene position by itself”

Symptom. An exception when you read a longitude and latitude as a Vector3.

Fix. Convert it with the map first: coordinate.To(MapSpace.World, map).ToVector3(). This works only on a map baked from the scene, as above.

My call did nothing

Symptom. You called EaseTo, AddPoint or another method right after creating the map, and nothing seems to happen.

Fix. Calls made before the map is loaded are kept and run once it is. To react when the map is ready, use map.Loaded += ... or check map.IsLoaded.

“A … annotation needs at least … places”

Symptom. An exception from AddLine or AddPolygon.

Fix. Pass enough places: a line needs two, a polygon three.

Components

“This shape is not on the map, because it has fewer than … points”

Symptom. A warning in the inspector of a Map Line or Map Polygon.

Fix. Add points in the Scene view, or reset the component.

“no object tagged Player and no Main Camera”

Symptom. A warning when you add a minimap.

Fix. The minimap follows the object tagged Player, else the main camera. Tag your player, or set Follow on the minimap and Target on its player icon by hand. See Minimap and world map.

Fog of war

“the fog of war needs an area”

Symptom. A warning from the fog of war component, and no fog.

Fix. The fog needs to know which area to cover. A map baked from the scene provides it. On any other map, call MapFog.SetArea. See Fog of war.

“These bytes are not a fog of war saved by MapFog.Save”

Symptom. An exception from fog.Load. Related: “This fog was saved for a … mask”, and “This fog save is truncated”.

Fix. The bytes did not come from fog.Save, or are cut short. The “saved for a … mask” message means the area, the map or Metres Per Cell changed since you saved. Load only a save made with the same settings.

Real-world maps

“Replace YOUR_KEY with the key of your account at this provider”

Symptom. A red box under Tiles URL, and tiles that do not load.

Fix. MapTiler and Thunderforest need your own key. Put it in the URL in place of YOUR_KEY. See Real-world maps.