kingy tested
Tested repair · Kingy Blender starter script · Blender 5.2.1 LTS, build 9e2066aef7ef; bundled Python 3.13.13; script SHA-256 11fee75acf5b9 (full hash in evidence ZIP)
Check this fix
- Applies when
- FileExistsError: Preserving existing file: ROOT_DIR/scenes/product_v001.blend. Choose a new root folder.
- Change to inspect
- Keep the existing file and choose a new, empty project root for a new build. To continue the same scene, open the saved .blend instead of running the scene-building script again.
- Expected result
- The refused rerun left the first .blend byte-for-byte unchanged and did not increase the scene count. A build into a new root saved successfully and the new .blend reopened. The original script was unchanged.
- If it still fails
- Keep the original failed output and check the conditions and verification steps below. Retained failed attempt: After a successful first product build, rerunning the unmodified script with the same root raised FileExistsError before adding a new scene.
Tested or reviewed 2026-09-21. Verify the original task on your own version and settings; this case does not prove a universal fix.
Read the verification steps ↓ · Report your outcome ↓What happened
Symptom
FileExistsError: Preserving existing file: ROOT_DIR/scenes/product_v001.blend. Choose a new root folder.
Exact environment and tested conditions
Kingy Blender starter scripts/build_scene.py with project product.
The chosen root already contains scenes/product_v001.blend.
A second build uses the same project and root.
Correction
Keep the existing file and choose a new, empty project root for a new build. To continue the same scene, open the saved .blend instead of running the scene-building script again.
Result
The refused rerun left the first .blend byte-for-byte unchanged and did not increase the scene count. A build into a new root saved successfully and the new .blend reopened. The original script was unchanged.
What did not work
After a successful first product build, rerunning the unmodified script with the same root raised FileExistsError before adding a new scene.
- Read the complete traceback and check that its final message is the starter’s Preserving existing file message. Locate the named .blend.
- To continue editing the first result, open that .blend in Blender. Save a new version before making changes you may want to undo.
- To generate another scene from the terminal, pass a new absolute folder with --root and keep --project product. A local example is blender --background --python build_scene.py -- --project product --root /absolute/new-project-folder --no-render.
- When using Blender’s Text Editor, change the script’s ROOT setting to a new folder before Run Script. The fresh verification used the build function with rendering disabled; it did not exercise the Text Editor UI.
- Confirm scenes/product_v001.blend exists in the new root and opens with the product scene. Keep the first build until you have reviewed the new one.
- Fallback: if the new folder also triggers the guard, choose another unused root. If the final error differs, stop and report that complete traceback; do not remove the guard or delete the original to force progress.
Sources & limits
Kingy.ai Blender guide and original editable starter package
Python FileExistsError reference
September 21 Fix Finder reproduction scripts and results (ZIP)
Record checked 2026-09-21.
The fresh test rebuilt the product scene without rendering, then reopened the saved file. Rendering and other project variants were not retested for this case.
This is the Kingy starter script’s intentional overwrite guard. A different FileExistsError elsewhere may need a different correction.
The guard checks the expected .blend destination. It is not a general concurrent-writer lock or a guarantee against every kind of overwrite. Use a new folder for each build.