WORKZONE TREE : HOW IT WORKS
The Workzone is the main working area where all intermediate and resulting files are created and managed.
When you use Prepare or Presplit functions:
- Repaired parts
- Oriented parts
- Scaled parts
- ...
are automatically added to the Workzone.
The Workzone allows you to:
- Visualize all generated elements related to the current project
- Select which file or plane is active
- Keep track of the different steps of the preparation process
- Files created in the Workzone are linked to the original model and reflect the operations performed on it.
- The Workzone acts as a staging area before exporting or further processing the parts.
- ...
.s3r project file = Workzone settings.
The .s3r file stores Workzone parameters: selected printer, plane positions, UI options, and other session data for this project.
VISIBILITY LOGIC.
Checked = the part/file is visible (shaded) in the 3D view.
Unchecked but selected (clicked in the tree) = the part/file is shown transparent, for quick inspection.
Checked in the WorkZone Tree
ACTIVE FILE
The Active File is the file currently used by all functions in the Prepare workspace and by the Presplit process.
Only one file can be active at a time. The Active File is displayed in Bold in the Workzone tree.
All operations such as Analyse, Repair, Orientation, Autoshell,... and splitting are applied to the Active File.
Before using any Prepare or Presplit function, make sure the correct file is set as active.
Activate STL: Double clic on it in the tree or Right-click and choose Activate to make it the Active file
Only one file can be Active at a time.
DELETE
Delete: Right-click and choose Delete to remove unneeded files/folders results from the Workzone.
Note : you cannot Delete an Active file, activate one other before
The Reality of 3D Files
After analysing support tickets from over 2,500 users during the first six weeks of Split3r's beta release, we identified a consistent trend: over 80% of reported issues stemmed from problems inherent in the files themselves, rather than software or user error.
We all download models from popular repositories like Thingiverse, Cults3D, Printables, or Thangs.... While these platforms are great resources, many uploaded files are modeled for visual purposes rather than manufacturing.
Consequently, they often carry severe geometric defects that make them unsuitable for operations like cutting or splitting.
To help you identify these "dead-end" files before you waste time trying to split them, we are introducing a raw Analyze command. It doesn't modify your file, it simply exposes the truth about its geometry.
What it detects:
The tool scans for specific defects that cause boolean operations to fail:
- Multi-Body STLs: The Blender mathematical engine we utilize cannot perform cuts on files containing multiple disconnected bodies.
- Non-Watertight Meshes: Open edges and holes.
- Self-Intersections: Geometry folding into itself (often invisible from the outside).
- Multi-Body Collisions: Internal overlapping volumes that confuse slicers.
- Non-Manifold Geometry: Mathematically impossible shapes.
Simply click on the icon, it analyses the Active file (the file displayed in Bold in the Workzone).
At the end of the analysis, if the software detects multiple bodies, it will prompt you to keep only the most significant ones.
We recommend keeping this option enabled, as it performs a preliminary cleanup of your model.
REPAIR (Stable but subject to evolution)
The Repair function has been fully redesigned and now provides three distinct repair options, allowing users to choose the most appropriate strategy depending on the geometry and origin of the file.
1. Repair using standard algorithms
This option first merges internal bodies (when technically possible), then repairs common mesh issues such as self-intersections, inverted faces, holes, and duplicated or overlapping faces.
This method successfully repairs the majority of files.
2. Repair using Split3r algorithms (organic part)
This option can be applied after a standard repair if analysis still detects issues.
It is particularly effective on organic or scanned parts, but may deform some mechanical parts.
3. Repair using Blender algorithms
This option is intended as a last alternative when previous repair methods do not produce satisfactory results.
Repairs can be executed individually (1, 2, or 3 only) or in sequence (for example, 1 followed by 2).
Repaired files are clearly identified:
Files repaired with method 1 are named R1
Files repaired with method 2 are named R2
Files repaired with method 3 are named R3
If multiple repairs are applied, file names reflect the sequence (e.g. R1-R2)
The Rotate command allows you to rotate/orient your part before further operations.
Rotating the part
Rotate the model by clicking on the colored arcs:
Red: rotation around the X axis
Orange: rotation around the Y axis
Green: rotation around the Z axis
By default, the rotation is applied in 5° steps.
Hold CTRL to switch to 1° rotation steps for fine adjustments.
Hold SHIFT for free (continuous) rotation.
Validating the orientation
Click OK to confirm the orientation.
The rotated part is saved in the Workzone with the suffix _O (for oriented) added to its name.
Scales the active model before splitting (useful to match target size or compensate for shrink).
Input: Active file (e.g., Demo-Rep.stl).
Output: Demo-Rep-Sca.stl added to the Workzone.
Modes: Percentage (%), Absolute dimension (X/Y/Z ) or Factor : eg :1.5 .
Safety: Non-destructive; creates a new step in the pipeline.
Project behavior: The current Pre-Split setup is automatically disabled before scaling, you’ll c-onfirm the change if the scale factor is very large (> 20×).
Tip: Verify the new scaled file is Active before proceeding.
HOW IT WORKS
Input format: Enter a value with factor, unit or %, so the app can compute correctly.
Percentage: 150%
Millimeters: 855mm IMPORTANT do not forget to add mm after the value 855mm not 855
Factor (unitless): 1000 for example with a STL file stored in meters unit (leave unit empty)
Per-axis inputs (X, Y, Z): You can fill 1, 2, or 3 fields.
One value only: The other axes are computed automatically to keep proportions (no deformation). (Most common case.)
Two values: The specified axes are scaled independently; the unspecified axis does not change.
Example: X=120%, Y=130%, Z= (empty) → deform X and Y, keep Z unchanged.
Three values: The part is scaled/deformed independently on each axis using the three inputs.
Mixing units is allowed:
Example: X=120%, Y=568mm, Z=1.6 (factor)
TIPS & NOTES:
Use percent for relative growth/shrink, mm for targeting a precise dimension, or factor for quick ratios.
Very large factors (> 20×) trigger a confirmation.
After scaling, a new file (e.g., *-Sca.stl) is added to the Workzone, make sure it is Active before PRE-SPLIT.
Creates a printable shell (hollowing) on the active model with a specified wall thickness.
Input: Active file (e.g., Demo-Rep-Sca.stl).
Output: Demo-Rep-Sca-She.stl added to the Workzone.
Use cases: Reduce material, speed up print, enable lightweight parts while keeping exterior shape.
THICKNESS GUIDELINE
Note on limitations: Depending on the shell thickness you choose, the numbering of parts may no longer be possible if the shell is too weak.
Recommendation: Avoid creating shells thinner than 15 mm to preserve enough space for tenons and tolerances.
Why: Thicker shells provide reliable tenon seating, reduce breakthrough risk, and improve bonding area.
Tip: If your tenon template is large or includes fillets/chamfers, consider ≥18–20 mm shell thickness. Adjust tenon spacing and offsets accordingly before running Split.
Of course, avoid trying to create an autoshell on small parts that are smaller than the thickness of the shell!
VOXELS AND MODEL SIZE
AutoShell uses a voxel-based representation of the model for the internal shell.
A voxel can be seen as a 3D pixel: a small cube used to describe the volume of a part.
The voxel size defines the size of these cubes and therefore the size of the internal facets generated by the software.
Small voxels = high precision, many internal facets, high memory usage
Large voxels = lower precision, fewer facets, better performance
The number of voxels increases very quickly with the size of the model.
For example, a part measuring 3000 × 2000 × 1000 mm with a voxel size of 3 mm generates more than 220 million voxels, which can easily exhaust your PC’s memory.
Recommendations
The voxel size must be adapted to the overall size of the part and the power of your PC:
Parts larger than 1 meter: approximately 5–7 mm
Parts around 2 meters: approximately 10–15 mm
Using a voxel size that is too small for large parts may lead to severe slowdowns or crashes.
Always start with a larger voxel size and reduce it only if higher precision is required.
Note : This function is expected to evolve in future versions, with the introduction of an automatic voxel size adjustment based on the part dimensions, in order to improve usability and reduce the risk of excessive memory usage.
CREATE CUT PLANE (Beta, NOT STABLE will evolve a lot)
The Create Cut Plane function allows you to orient and create cutting planes directly on the model.
Each cutting plane is currently created in the Workzone, with one plane per part section.
At this stage, only one plane can be active at a time.
The active plane is the one that will be used by the Cut by Plane command.
You can:
Orient the cutting plane relative to the model
Position the plane to define where the cut will occur
This function is still under development and will evolve significantly in future versions.
Upcoming improvements will mainly focus on:
The graphical user interface (simplification)
The management of different types of tenons (multiple small connectors, pyramidal connectors, large single connectors, etc.)
CUT BY PLANE (Beta, NOT STABLE will evolve a lot)
The Cut by Plane command starts the cutting process of the active part using the currently active cutting plane.
When executed, the command:
Cuts the model according to the active plane
Adds the preselected connectors to the cut surfaces
Make sure that the correct cutting plane is active before launching the command.
This function is still under development and will evolve significantly in future versions.
Upcoming improvements will mainly focus on:
The graphical user interface (simplification)
The management of different types of tenons (multiple small connectors, pyramidal connectors, large single connectors, etc.)
