ProcGeometryNode builds its output children at runtime and gives them to nobody, which is why a saved scene does not carry the millions of vertices they hold — the right default for a live view. A PUBLISHED scene is the opposite case. blender-bridge now writes the baked mesh as a .res beside the scene and gives MeshOutput an owner so it is packed, precisely so the file opens without proc-nodes and without a bake. Creating a second MeshOutput on _ready would leave that baked mesh on a node nothing draws into, and the next evaluation writing into a stranger beside it. ⚠ Godot renames a clashing sibling, so the duplicate is called "MeshOutput2" — the gate that first covered this counted by NAME and reported "exactly one" with the bug present. It counts MeshInstance3D children of the ProcGeometryNode now, and goes 2 when this adoption is removed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>