What the studio does automatically
How the studio finds the stones
One button turns a CAD file into a dressed ring: stones become diamonds, everything else becomes gold, the lighting switches to the jewellery environment. Behind the button is a short list of tests, run in a fixed order, and knowing them is what lets you name your parts so the guess is never needed.
First: if the file already says, believe it
A glTF exported from a tool that marks gems as gems arrives with that flag on each part, and a file that has classified itself is not second-guessed. This matters because the heuristics below are aimed at files that could not classify themselves, and applied to one that had, they once turned a pair of prongs into crystal — a claw's bounding box is small enough to look like a stone. So a declared file skips every test that follows.
Then the name
A part called anything with stone, diamond, gem, brilliant, dia, cz, crystal or solitaire in it is a stone. A part with ruby, sapphire, emerald or amethyst in the name is that coloured stone. One trap is handled deliberately: 'emerald' is a cut at least as often as it is a colour, and a Rhino block named Diamond_Emerald Square is a diamond in an emerald-shaped cut. A name that says diamond outright means diamond, whatever else it says.
Underscores and hyphens are split into words before matching, because a name like Diamond_Round is one 'word' to a naive pattern and would never match.
Then size
In a multi-part file, any part whose bounding box is under two per cent of the largest part's volume is treated as a stone. That catches unnamed pavé and side stones, which are tiny beside a band. It also means a very small non-stone part — a tiny bead or a hallmark tag exported as its own body — will be caught, and you drag it back to Metal in the parts list.
Then shape, for CAD exports with generic names
A STEP or IGES from a program that names parts Part 7 and SOLID needs one more test. A cut stone is a chunky, roughly equidimensional solid that fills most of its bounding box; a band is a thin shell that fills little of its box; a prong is long and thin. Parts that look like a cut stone are treated as one — with no upper size limit, because a centre stone is often the largest part by bounding box, and that is exactly the case this test exists for.
- Declared by the file → believed, nothing else runs
- Name says stone or a stone colour → stone
- Under 2% of the largest part → stone
- Chunky solid that fills its box → stone
- Otherwise → the chosen metal
What to name your parts
If you control the export, put the word diamond (or the colour) in each stone's name and the word band, shank, head or prong in the metal parts, and the guess is never needed. From Rhino, keep the stones on a layer named for what they are — the layer name becomes the part name. Everything here happens on your own machine: the file is converted and rendered in the browser through your GPU and is never uploaded, so an unreleased design stays unreleased.
Questions
Auto Jewelry Setup turned my prongs into stones. Why?
Small prongs exported as separate bodies fall under the two-per-cent size test. Drag them from Diamonds to Metal in the parts list — one drag each — or name them prong in the CAD file and the name rule will keep them metal.
It found no stones at all in my file.
The file is metal-only, which is normal for an STL export — the stones were never in it. The studio offers to bring them in: place them from the design's 3DM in one click, or pick a cut and click each seat.
Why did my emerald-cut diamonds come out green?
They should not — a name that says diamond is read as a diamond whatever cut it names. If the part is named only Emerald with no diamond in it, the colour rule reads it as an emerald stone; rename it or switch it to diamond in the console.
Free · runs in your browser · your file is never uploaded