What this does not do.
Read this before you plan an afternoon around it. Three grounds, and the difference between them is the whole point: what is not built is a decision with a date behind it, what is built and unwatched is a risk you would be taking, and what is deliberate is not going to change however politely you ask.
Nothing generates this page. It is written from the same notes the work is tracked in and reviewed against them, which is a weaker guarantee than the measured pages have, and it is why this one carries a review date and they do not.
Six tools
Sculpting, curve cuts, many-part splitting, articulated joints, moulds and rendering. Six of the category’s fourteen tools; see features for which halves of the other eight are thinner than the tool they are measured against.
ScheduledA checkout
Tilas Pro is described on the pricing page and cannot be bought yet. Prices are announced at launch, on the first of November, and there is no checkout until then — the upgrade buttons in the app open that page and nothing else.
Not builtUpdates
The desktop app checks for a new version only in a release build signed with the update key, and installs it only when you press Install. No such build has shipped, so updating from one version to the next has never been tested — until it has, a new version is a download you fetch yourself.
UntestedTranslation
English only. Every string is still a literal inside a component, so this is real work rather than a setting.
Not builtOther formats
Reading: STL, OBJ, PLY, 3MF, GLB and glTF — no STEP and no point clouds. A glTF whose geometry sits in a separate file, or is Draco or meshopt compressed, is refused with what to do instead; a texture kept as a separate file, or in the compressed KTX format, is left out and the import says so. An OBJ’s material library is not read, only its vertex colours. Writing: 3MF and its own project file. It does not slice.
Not builtA drag handle
Transforms are numbers, not a gizmo. Move, rotate and scale the active part from the Select tool’s fields; there is nothing to drag in the viewport yet, and scale is uniform on purpose, because a non-uniform one distorts every keyed connector.
Not builtKeys on a separation
The control that existed only worked by taking a grid-based method that has since been removed, so it bought a worse separation rather than a keyed one. Split still cuts with keys.
RemovedThree colours at a point
Two colours separate on the paint itself, and any number separate when each body is a single colour — of the 48 corpus models auto-paint gives two colours, 19 are cut exactly on the paint. Where three meet at a point the boundary between any pair stops being a closed curve and there is nothing to span. Those models are divided on a grid instead, and the panel says so.
Falls backSupports
Built, and hidden for launch. Both styles generate and place, but nothing has been printed and pulled off a real model — the test that decides whether they work — and the add and block zones you would draw by hand are not built. Until that print has happened the tool is not on the tool bar, its shortcut or the command palette.
HiddenRemesh
Simplifying carries your paint onto the reduced surface, where a region edge can only be as fine as the triangles that remain — and there is nothing yet that puts the detail back.
Not builtBuilt, but nobody has watched it work
The code exists. Nobody has seen it.
This is the section that usually gets rounded up into the one above, and it is separate on purpose: the tests pass, and a passing test is not a person watching a thing happen. Everything below is shipped in the build you can download.
This is the half a release note flatters. Each line says what was tested and what was not, rather than how confident anybody is.
- Windows and macOS.Both are produced by the same job from the same commit as the build that works, and neither has ever been launched by anyone. On macOS, double-clicking a model file will not open it — that path is not connected at all.
- Installers, on a clean machine.Never run on one, for any platform. Nothing is signed or notarized either, so Windows will show SmartScreen and macOS will show Gatekeeper.
- Separate, driven from the interface.Every layer below the button is tested, including the message passing across the native boundary, and nobody has pressed Separate in a real window and watched parts come back.
- Activating a Pro key.Activation, monthly renewal, the offline allowance and freeing a machine are tested on both sides of the network, and no real purchase has produced a key yet, because there is no checkout.
- The too-big-for-this-machine refusal.Every piece of it is tested, and the one real session of it was wrong: the machine reported its memory, the estimate judged a very large file fine, and the import crashed. Treat it as unverified.
- The folder a plated export writes into.Both sides of the boundary are tested; nobody has picked a folder by hand and watched a batch land in it.
- Dragging a file from your file manager onto the window.Only the page’s own drop event has been exercised.
- The newer graphics backend in the desktop window.The open question is which backend the desktop webview picks, and the newer one has never rendered on hardware this project has; the browser version has not been tried on it either. The older one is verified and the app falls back to it automatically, so this is a missing upside rather than a missing feature.
- The slicer compatibility checks in CI.PrusaSlicer, OrcaSlicer and Bambu Studio each slice our exports with their own command-line tools, and the checks read the G-code they write. They pass on this project’s own machine; the build-server job, which pins OrcaSlicer and Bambu Studio to the verified versions and takes PrusaSlicer from Flathub’s current stable release, is new and has never executed.
Deliberate — and not going to change.
Your model never leaves this machine.
No account, no upload, no telemetry. The desktop app reaches the network for two things only — the update check, and activating or renewing a Pro key — and neither carries anything about your model. The in-app bug report gathers the inspection report, your recent steps and your system information onto your clipboard; it sends nothing anywhere.
This is the one on the list that is also a reason to pick it: for a model that is somebody’s paid commission, the upload is the problem.
Millimetres and Z-up, always.
Converted once when the file is read. The unit switch changes what you read and never what is stored, so no document ever carries two answers to the same question.
sixteen filament slots, because that is what the target slicers consume — not a ceiling anybody picked.
Repair is reported, never silent.
A clean file passes through byte-identical rather than being improved. Everything repair changes is listed, and so is everything it did not: self-intersections and genuinely branching edges are found and reported, never quietly corrected. The Repair tool’s actions — fill holes, remove small shells, fix the normals, run the whole repair again — each do one named thing, and each is one step of undo.
A branching edge is a shape that cannot exist rather than a defect in the file, which is why it is reported instead of repaired.
The canvas is never covered.
No dialog is ever drawn over your model. Anything that wants the screen gets a non-modal popover or a column beside the canvas.
It is a constraint on every feature that comes after this sentence rather than a preference about the ones already here, which is the only kind of rule worth writing down.
Anything that fails tells you what to do next.
A message that says something broke without saying what to do about it is a bug in its own right, not a rough edge.
Every change is run against 124 real models from two public corpora. 21 of them are refused — a point cloud, an empty export, one corrupt file — and the run fails if a refusal arrives without a remedy attached to it. A refusal is a result; a refusal with nothing to do about it is a white screen with extra words.
Still here?
Then you are the person this is being built for. Read it, download it anyway, and tell us which of the lines above you hit first — that is the one that moves.
The bug report action in the chrome collects everything and puts it on your clipboard, ready to paste. There is nowhere published to paste it yet, which is itself on the list above and is the next thing being fixed.