3D Model Versions
Simplio3D automatically tracks versions when you upload updated 3D models with the same filename. This lets you iterate on designs without losing previous versions, and seamlessly update models already in use within your projects.
How Automatic Versioning Works
When you upload a 3D model file that has the same base name (ignoring case and extension) as an existing asset, Simplio3D automatically creates a version chain:
- 1Upload your first model file (e.g. "custom_shoe.glb"). It is stored normally — no version tag yet.
- 2Later, upload an updated model with the same name ("custom_shoe.glb"). Simplio3D detects the name match.
- 3The original model is retroactively tagged as "v1". The new upload is tagged as "v2".
- 4Each subsequent upload with the same name increments the version: v3, v4, and so on.
- 5Version tags appear as badges on the asset thumbnail in both grid and list views.
Custom_Shoe.glb, custom_shoe.glb, and custom_shoe.fbx are all considered the same asset and will form a version chain.Managing Version Tags
Version tags (e.g. "v1", "v2") are informational labels that help you identify which iteration of a model you're looking at. You can remove a version tag if you prefer a cleaner view.
- 1Navigate to Dashboard > Assets and locate the versioned model.
- 2In grid view, hover over the version badge on the thumbnail to reveal the × (remove) button.
- 3In list view, the version badge appears next to the asset name with the same × button.
- 4Click × to remove the version tag. The tag is removed from the UI, but the version history is preserved internally.
Replacing a Model Version in a Project
When you've iterated on a 3D model and uploaded a new version, you can replace the older version in any project that uses it. The replacement preserves all option block references, materials, and configurations.
- 1Open your project in the Project Editor.
- 2Click the "Asset Browser" button to open the asset library dialog.
- 3Browse or search for the updated model. Versioned assets show their version badge (e.g. "v2").
- 4Select the new version and click "Load". The system detects that a model with the same base name is already in the scene.
- 5A confirmation dialog appears explaining that the existing model will be replaced. Click "Yes, replace" to continue.
- 6The new model data replaces the old one while keeping the same internal model ID. All option blocks, material assignments, and transform references are preserved.
- 7After loading, the system compares 3D part names between the old and new model. You'll see a success or warning toast.
Part Name Matching
When a model is replaced, Simplio3D checks whether the 3D part names (mesh names) in the new model match those referenced by your option blocks. This ensures your configurator options continue to work correctly.
All Parts Match
If all part names referenced by option blocks exist in the new model, everything works seamlessly. A success toast confirms the replacement.
Some Parts Missing
If some part names have been renamed or removed in the new model, a warning toast lists the affected parts. You'll need to update those option blocks manually.
What Gets Preserved During Replacement
| Item | Preserved? | Details |
|---|---|---|
| Model ID in scene | Yes | The internal model identifier stays the same, so all references remain valid. |
| Option block references | Yes | All targetObjectId references in option blocks continue to point to the correct model. |
| Material assignments | Yes | Materials assigned by option blocks are re-applied if the part names match. |
| Part transforms (saved) | Reset | Custom part transforms are cleared since the new model may have different geometry. |
| Deleted parts list | Reset | Previously deleted parts are cleared to reflect the new model structure. |
| Animations | Updated | Animation clips from the new model replace the old ones. |
Best Practices
Consistent Naming
Keep the same filename when uploading iterations of a model. This ensures automatic version detection and easy replacement.
Keep Part Names Stable
Maintain consistent mesh/part names across versions so option blocks and conditional logic continue to work.
Preview Before Sharing
After replacing a model version, preview the project in Share view to verify all options, materials, and visibility toggles still behave correctly.
Version History
Upload multiple iterations freely. Each version is stored independently in your asset library, so you can always go back to a previous version.
Example Workflow
Updating a Shoe Configurator
You've built a shoe configurator with option blocks for sole material, upper colour, and lace style. The designer sends you an updated model with refined geometry.
- 1The designer exports the updated model as "custom_shoe.glb", keeping the same part names (sole, upper, laces, tongue).
- 2Upload "custom_shoe.glb" to Dashboard > Assets. It is automatically tagged as "v2". The original becomes "v1".
- 3Open the shoe project in the editor and click "Asset Browser".
- 4Select "custom_shoe.glb (v2)" and click Load.
- 5Confirm the replacement when prompted. The editor swaps the model data.
- 6A success toast appears: "Model replaced — all 4 referenced parts found in the new model."
- 7Save and preview. All option blocks (sole material, upper colour, lace style) work correctly with the new geometry.