Documentation · Studio Scene Pilot Pro

Production control for Blender scenes.

Studio Scene Pilot Pro is a production workflow toolkit for Blender artists, freelancers and small teams working with complex scenes, assets, materials, rigs, animation clips, optimization and delivery requirements.

Start workflow Safety model Troubleshooting

Overview

What Studio Scene Pilot Pro is.

Studio Scene Pilot Pro is not only a cleanup addon. Its main value is to create a consistent production system inside Blender, so a file remains readable, reviewable and delivery-ready as it grows.

Structure

Create production collections, classify assets, control names and keep complex Blender files easier to understand.

Review

Track status, notes, issues, assignments and delivery blockers with metadata that stays inside the Blender file.

Deliver

Clean files safely, optimize production data, generate LODs and export HTML, TXT, CSV or JSON reports.

Index

Documentation sections.

Use this page as a practical map for the addon. Each section focuses on a production task inside Blender.

01 · First use

Installation and first launch.

Install the addon

Open Blender.
Go to Edit > Preferences > Add-ons.
Click Install.
Select the Studio Scene Pilot Pro .py file.
Enable the addon checkbox.
Open the 3D Viewport and press N.
Open the Studio Scene Pilot tab.

First launch recommendation

Keep Simple Mode enabled unless you are testing advanced features. Simple Mode keeps the main workflow visible and hides advanced panels so the addon is easier to learn.

Do not test destructive tools on an important file. Save a copy of your production scene first.

02 · Core workflow

Recommended production workflow.

This is the safest way to use Studio Scene Pilot Pro on both new scenes and existing production files.

Start project

Choose a template, create collection structure, set production phase and define rules.

Classify assets

Assign production types to objects and material types to materials.

Change names

Rename selected objects or related data only after classification is clear.

Review scene

Run scan, check issues, add notes, assign status and reviewers.

Clean & optimize

Analyze scene, model and material problems before applying fixes. Then check heavy objects, modifiers and LOD needs.

Prepare delivery

Run delivery check, inspect blockers and export HTML, TXT, CSV or JSON reports.

Classify first when possible. Rename only when you know the intended name. Renaming does not change asset classification.

03 · Production logic

Core concepts.

Production phase

The production phase changes how the addon evaluates the scene. A file in Build phase should not be judged like a file in Delivery phase.

Build Review Optimize Delivery

Studio metadata

Studio Scene Pilot Pro stores production metadata using Blender custom properties. It may create collections, preview helpers, LOD copies, backup objects, reports and generated data when you use those tools.

System	Question it answers	Example	What it changes
Asset Classification	What is this in production?	Furniture, Prop, Character, Rig, Product, Camera	Custom metadata, optional colors, collection organization and reports.
Naming · Change Names	What should this be called?	FUR_OfficeChair_001, PROP_Box_014, MAT_Glass_Clear	Only names of selected targets and optional related data. It does not reclassify assets.

04 · UI map

Interface overview.

Area	Purpose
Team / Server Setup	Optional metadata sync, local JSON exchange, team templates and server settings.
Production Workflow	Guided steps for starting, classifying, reviewing, optimizing and delivering.
HEALTH · Overview	Scene health, next steps, scan status and production summary.
SETUP	Project structure, scenes, view layers, libraries and asset browser handoff.
BUILD	Asset classification, naming and intake of new/imported objects.
REVIEW	Status, notes, colors, visibility modes and issue review.
ANIMATION	Animation clips and rig retarget utilities.
PERFORMANCE	LODs, modifiers, subdivision and heavy object handling.
CLEANUP	Scene, model and material cleanup by area.
DELIVERY	Delivery check, reports and rules.
HELP	Workflow notes, safety notes, PDF documentation and support info.

05 · Team workflows

Team / Server setup.

Server sync is optional. Studio Scene Pilot Pro works fully offline and server workflows should only handle production metadata.

Available modes

Off: all metadata stays in the Blender file.
Local JSON: small teams exchange metadata manually.
HTTP Server: a studio connects its own server/API.

Server sync scope

Server sync should only send production metadata: status, notes, asset types, assignments, issues, rules and reports. It should not upload .blend files, meshes, rigs, textures or geometry.

Template	Best for
General Studio	Balanced production scenes with common review and delivery rules.
Animation Environment	Set, props, cameras, lighting, rigs and shots for animation.
Video Game / Realtime	LOD, UV, texture size, origin, scale and engine-ready checks.
Showroom / Archviz	Architecture, furniture, props, cameras, lights and scene organization.
Product Visualization	Products, parts, materials, cameras, lights and clean delivery.
Character / Rig / Animation	Armatures, actions, retarget, clips and rig-safe warnings.
Asset Library / Pack	Asset Browser handoff, naming, metadata, descriptions and pack delivery.

06 · Scene foundations

Setup tools.

Project Structure

Create production collections for assets, environment, props, lighting, cameras, references, review, approved, final, export and temporary work.

Scenes & View Layers

Create work, review, lighting or delivery variants. Use view layers to avoid manually toggling many objects and collections.

Linked / Appended Assets

Inspect objects coming from external libraries or linked files. Move selected items to Incoming for controlled classification.

Asset Library Handoff

Mark approved or selected objects as Blender assets, sync metadata and prepare assets with type, description, tags and catalog information.

07 · Classification and names

Build tools.

Asset Classification

Defines what each object or material represents in production. This is the recommended first step for large existing scenes and newly imported assets.

Assign object asset type.
Assign material type.
Use classification as context for reports and organization.
Activate or deactivate viewport outlines.
Use right-click menus for faster classification.

Naming · Change Names

Naming is intentionally literal. It changes names. It does not change asset classification.

Choose what you want to change.
Enter a New Base Name only when replacing the existing base name.
Leave New Base Name empty to keep current names.
Use Preview before applying changes to many objects.
Use assigned Asset Type as prefix only if you want classification to inform naming.

Use ACTIVATE OUTLINE / DEACTIVATE OUTLINE to show or hide Studio Scene Pilot viewport outlines. In very large scenes, use conservative modes such as Selected Only, Issues Only or Review Only.

08 · Production review

Review tools.

Status & Notes

Track production state and record review feedback. Use To Do, In Progress, Needs Review, Approved, Final, Blocked, Client Change and Do Not Touch.

Visibility & Work Modes

Focus on editable, review, approved, delivery or performance-friendly subsets without manually hiding hundreds of objects.

Scan & Issues

Scanning finds production and technical issues. Review by Critical, Warning and Info. Use Select, Ignore, Add Note or Assign to Artist.

09 · Advanced animation tools

Animation tools.

Animation Clips

Scan clips and read frame ranges.
Assign a selected clip to an armature.
Set the timeline to the clip range.
Rename clips with production rules.
Enable fake user and push clips to NLA.
Export clips as GLB or FBX when required.

Rig Retarget

Advanced tool for controlled animation transfer from a source armature to a target armature. It includes hip/root bone detection, scale matching, presets and visual bake.

Duplicate rigs first, check hip/root bones, preview mapping and bake on a test range before using final production data.

10 · Optimization

Performance tools.

LODs

Generate lower-detail copies using Blender tools such as Decimate and Remesh. Useful for quick production optimization, preview objects, realtime assets and delivery variants.

Create LOD0, LOD1, LOD2 and LOD3.
Use Decimate Collapse, Decimate Planar or Voxel Remesh.
Export generated LODs as GLB or FBX.

Modifiers & Subdivision

Find and control objects with Subdivision, Weighted Normal, Bevel, Decimate, Remesh, Triangulate or Geometry Nodes. Disable viewport subdivision for performance and apply modifiers only after dry run and backup.

Automatic LOD generation can damage UVs, topology, skinning or product-quality surfaces. Use duplicates and previews, especially for characters, rigs, shape keys and high-value assets.

11 · Safe cleanup

Cleanup tools.

Cleanup is separated by area so the user knows what kind of data may be affected.

Cleanup · Scene

Find and remove empty collections after review.
Detect visibility mismatches.
Clean structure and move unorganized objects when appropriate.
Purge orphan data only when you understand what will be removed.

Cleanup · Models

Follow Analyze → Select → Fix Selected. This avoids changing hundreds of objects blindly.

Ngons
Duplicate vertices
Loose geometry
Non-manifold
Possible interior faces
Negative scale
Far origins

Cleanup · Materials

Find objects without materials.
Find empty material slots.
Detect duplicate material names.
Find missing image texture paths.
Find large textures.
Assign placeholder materials for review.

12 · Final handoff

Delivery tools.

Delivery Check

Delivery Check answers one question: is this scene ready to deliver according to the current rules? It should be stricter than Build or Review phase scanning.

No required assets should be unclassified.
No delivery object should be in Needs Review or Blocked status.
Required materials and UVs should exist.
Required names should follow production rules.
No accidental hidden/render visibility mismatch should block delivery.

Reports

HTML: most readable summary for review and delivery.
TXT: quick human-readable report.
CSV: spreadsheet-friendly issue or task lists.
JSON: machine-readable metadata for local/team workflows.

13 · Trust and control

Safety model.

Label	Meaning
Analyze	Reads data and updates results. It should not modify production geometry.
Select	Selects affected objects, faces or materials for review.
Preview	Shows what would change without applying it.
Fix Selected	Modifies only selected objects or elements.
Apply	Changes data, modifiers, transforms or names. Use preview and backup first.
Remove	Deletes or removes data. Treat as destructive.
Clean	May remove or change data. Use Safe Mode and confirmation.

Keep Safe Mode on for production scenes, enable backups before destructive operations, use Dry Run / Preview, and save a new file version before major cleanup or optimization passes.

14 · Support

Troubleshooting.

Problem	Likely cause	What to do
The scene shows many issues immediately.	The scene has not been classified or prepared for SSP yet.	Start with Asset Classification and project structure before treating all issues as errors.
Viewport colors are distracting.	SSP outline or color mode is active.	Use DEACTIVATE OUTLINE or switch outline mode to Selected Only / Off.
Naming feels risky.	Mass rename without preview is dangerous in large scenes.	Use Preview Name Changes and leave New Base Name empty if you only want related names changed.
LOD result damages a mesh.	Decimate/Remesh can alter topology, UVs or skinning.	Use backups, skip unsafe objects and avoid automatic LODs on rigged/shape-keyed meshes.
Retarget produces wrong motion.	Bone mapping, scale, rest pose or hip/root selection may be wrong.	Detect hips, match scale, preview mapping and test on duplicated rigs.
Server sync is unclear.	Server mode is optional and only handles metadata.	Use Local JSON first or export the API/schema example for technical setup.

Support checklist

Addon version.
Blender version and operating system.
Screenshot of the UI or error.
Full console traceback.
Exact steps to reproduce the issue.

Glossary

Asset Classification: production type assigned to objects or materials.
Safe Mode: backups, warnings and skipped unsafe objects.
Dry Run: preview of what an operation would affect.
LOD: lower-detail version of an object.
SSP Metadata: custom properties stored inside Blender data.

Final recommendation.

Use Studio Scene Pilot Pro as a workflow, not only as a toolbox. The strongest production flow is: create or inspect the project structure, classify assets, change names carefully, run scans, fix only selected problems, optimize with Safe Mode, then deliver with reports.