Quick answer: Add the instance to a node in the active tree with add_child, set its position on-screen, and check visibility and modulate.

An instanced scene not appearing is usually never added to the tree or positioned off-screen. Here is how to fix it.

How to fix it

1. Add it to the tree

After instantiating a scene, call add_child on a node that is in the active tree to make it part of the scene. An instance created but never added exists in memory but does not render.

2. Set the position

A new instance defaults to the origin (or its parent's position). If that is off-screen or behind something, it will not be visible. Set its position to where you want it to appear.

3. Check visibility and modulate

Confirm the instance and its parents are visible and not made transparent by modulate. A visible-false parent or a zero-alpha modulate hides the instance even though it is in the tree and positioned correctly.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.