Messages
Fabricator speaks in four places. This page lists the messages you can meet in each, what they mean and what to do. The messages of the website’s own pages are on the pages that explain them: Create an account, Buy and manage a plan, Work as a team and Get help.
| Where | What it says |
|---|---|
| The status line under the account button of the Fabricator panel | Your login and updates. One message at a time, the most pressing first. |
| The status bar at the foot of the Fabricator panel | The result of the last thing you did in the panel. Red for an error. |
| The foot of the Atlas’s map | That the map or the panels are still being calculated. |
| Rhino’s command line | Solve results, refusals in the Atlas, plan messages, and the references support asks for. Lines start with Fabricator: or [Fabricator]. |
The panel’s status line
Section titled “The panel’s status line”| Message | Buttons | What to do |
|---|---|---|
| (none, the account button says Not logged in) | Log in | Log in: see Install and log in. |
| “Opening your browser…”, then “Approve code XXXX-XXXX in your browser” | Cancel | Check that the browser shows the same code and click Approve there. The code works for 10 minutes. |
| “You’ve been logged out” | Log in | The login was disconnected on the website or you were removed from a team. Log in again. |
| “Can’t reach the Fabricator server” | Try again | Check the internet connection, a firewall or a VPN, then click Try again. |
| “Couldn’t check your sign-in”, or another short reason | Try again | Click Try again. If it stays, ask for help. |
| “Fabricator 0.2.4 is available” (the number of the new version) | Update | Click Update to install it. Rest the pointer on the message for the full build number. |
| “Update required to keep working” | Update, or Download manually | This version is too old to use. Update it now. |
| “Downloading the update…” | None | Wait. |
| “Restart Rhino to finish the update” | None | Close Rhino and open it again. |
| “The update didn’t install” (red) | Try again, Download manually | Try again. Download manually opens the website’s Getting started page with the download. |
The update offer shows only while you are logged in. See Updates.
The panel’s status bar
Section titled “The panel’s status bar”These are the messages you are most likely to see. Each reports the last action and stays until the next one.
| Message | Means |
|---|---|
| “Frame connectivity on” / “Frame connectivity off” | FrameConnect was switched. |
| “Healed … snap(s), … end(s) onto corners, joined … curve(s) in … chain(s)” | Heal Frame worked; the numbers say what it did. |
| “Selection already clean” | Heal Frame found nothing to heal. |
| “Select curves to heal” | Select the curves first. |
| “Broke into … panels, … shared edge(s) split.” | Break Panels worked. |
| “No shared edges to break, so nothing changed.” | The wireframes share no edges. |
| “Projected … curve(s) onto … face(s).” | Project worked. Curves that cross no closed face are left as drawn, and the message says so. |
| “Select the curves to project first.” | Select the curves first. |
| “Imported …: … lines, … curves, … details, … closed, … joins” | Import Leica worked. See From a Leica measurement. |
| “Prepared … drawn panel(s) as one card, … edge(s) on Fixed edge.” | Import Drawn Panels worked. |
| “Solving: waiting for the Atlas map…” | Run 3D Solver was pressed; the Atlas starts the solve when its map is ready. |
| “Select a wireframe in the viewport to solve” | The drawing has several wireframes: select the one to solve. |
| “The Atlas is not ready for this document yet” | Wait for the Atlas to show this drawing, then press again. |
| “The Atlas could not be loaded; click FAB2D” | Open the Atlas with the FAB2D chip or the map button in the panel. |
| “Baking the solved 3D mesh…” | Output 3D Model is working. |
| “Open the Atlas to change a material colour” | Colours are changed through the Atlas; open it, then change the colour again. |
| “Cleared” | Clear Results removed the 3D preview and the solver results. |
| “Debug info copied to clipboard” | Debug worked: paste it into your message to support. |
| “Not a Leica export: no P_### shot labels in …” | The file is not a Leica device export. |
The foot of the Atlas’s map
Section titled “The foot of the Atlas’s map”| Message | Means |
|---|---|
| “Waiting for the server map.” | The Atlas is waiting for the first map of this drawing. |
| “Calculating… 3 panels pending” | Panels you changed are being calculated; a small spinner sits where their numbers go. |
| “3 panels pending — the server map was not updated: …” | The map could not be calculated; the reason follows. Click Sync in the Atlas’s header to calculate it again. |
| “A seam edit is waiting for the map to update; it is made when the map has.” | Your seam change is held until the map is ready. Nothing to do. |
| “Fabrication out of date — recalculate” | The panels’ fabrication is older than the drawing and is not being calculated. Click Sync. |
| “Calculating…” | The fabrication is being calculated again. |
The Run 3D Solver button in the Atlas also reports while it waits: “Waiting for the map…”, “Connecting to Rhino…”, “Reading Rhino changes…”, “Waiting for Rhino to confirm…”, “Waiting for the drawing…”. Press it again to cancel.
Rhino’s command line
Section titled “Rhino’s command line”From the Atlas
Section titled “From the Atlas”The Atlas writes to Rhino’s command line only what you must see. Its lines
start with [Fabricator] Atlas JS:.
| Line starts with | Means | What to do |
|---|---|---|
cut refused: |
A cut you drew in the Atlas was not made; the reason follows. | Draw the cut again where the reason allows. |
join refused: |
A join was not made; the reason follows. | As the reason says. |
feature refused: |
A detail, cutout, reinforcement, pocket, seam or other edit was not made; the reason follows. | As the reason says. |
plan: |
“The free plan shows the panel shapes. Cut lines, notches and labels come with a plan. Choose one under Plan & billing in the Fabricator panel.” | See Plans. |
support: |
A calculation failed or was refused. The line holds what failed, a code, a reference and the message. | Try again; if it keeps failing, send the line to support. |
From the solve
Section titled “From the solve”| Message | What to do |
|---|---|
| “Fabricator: submitting identity solve (…)…” | The solve has been sent. Wait for the result. |
| “Fabricator: solve not started — The map found no panels in this drawing. A panel needs a closed outline of curves on the Fixed edge, Seam, Cable or Join layer; Detail curves mark a panel but do not outline one.” | Close the outlines and put them on an edge type. Press Check in the panel. |
| “Fabricator: the solve failed (…).” The reason is in brackets. “Your previous solve is kept.” follows when there was one. | Read the reason; the table below explains the usual ones. |
| “Fabricator: the solve returned no panels, so nothing was saved. Run the solve again.” | Run the solve again. A previous solve, if any, stays. |
| “Fabricator: solve result superseded by a drawing change or newer solve” | You changed the drawing, or started another solve, while it ran. Solve again when the drawing is ready. |
| “Fabricator: the solve finished, but it could not be saved in this drawing. Run the solve again.” | Run the solve again. |
| “Fabricator: solve saved. Open the Atlas to see it.” | The solve worked; open the Atlas. |
Plan and seat messages
Section titled “Plan and seat messages”| Message | Where | What to do | Code |
|---|---|---|---|
| “Full solves, 2D patterns and nesting need an active plan (plan=free). Choose one on the Billing page: …/billing. On a team, the team owner chooses the plan.” | A solve, 2D output or nest on a free account | Choose a plan: Buy and manage a plan. On a team, ask the owner. | SUBSCRIPTION_INACTIVE |
| “Full solves, 2D patterns and nesting need an active plan (plan=pro). Renew or update it on the Billing page: …/billing. On a team, the team owner manages the plan.” | The same, when a plan has ended or a payment failed (the plan named may be pro or day_pass) |
Renew the plan or fix the payment on Billing. | SUBSCRIPTION_INACTIVE |
| “Full pipeline (3D / 2D solve) requires an active subscription. Visit fabricator.hr to subscribe.” | The same, when the server gives no reason | As above. | SUBSCRIPTION_INACTIVE |
| “Your team has no paid seat for you, so full solves, 2D patterns and nesting are off. Every tool and the preview still work.” | A solve, 2D output or nest by a team member without a seat, where seats count | Ask the team owner to buy a seat or give you one. See Work as a team. | SEAT_REQUIRED |
| “All the seats your team pays for are in use. Buy another seat on the Billing page, or remove someone first.” | The Team page, inviting or accepting, where seats count | Buy another seat, or remove someone. | SEAT_LIMIT_REACHED |
| “Fabricator Plugin too old: click Update in the Fabricator panel, or update Fabricator in Rhino’s Package Manager.” | Any request from an old plugin | Update the plugin. | PLUGIN_VERSION_UNSUPPORTED |
Solver and calculation messages
Section titled “Solver and calculation messages”These come from Fabricator’s servers. In Rhino they reach the command line,
in a support: line from the Atlas or in brackets after “the solve failed”.
Support may ask for the code in the second column.
| Message | What to do | Code |
|---|---|---|
“Edge has disallowed role none” |
An edge has no edge type. Put every wireframe curve on an edge type layer. | EDGE_ROLE_NONE |
| “One or more edges are missing a role assignment” | As above. | MISSING_EDGE_ROLE |
| “One or more input fields failed validation” | Something in the drawing could not be used; the details follow. Press Check and Heal Frame, then try again. | USER_INPUT_INVALID |
| “Geometry exceeds per-project caps” | The drawing is too large to solve in one go. Solve fewer wireframes at a time, or simplify them. | GEOMETRY_LIMIT_EXCEEDED |
| “Units mismatch: your Rhino document is in Millimeters (metric) but the Fabricator solver is configured for imperial. …” | Make the drawing’s units and Settings → General → Units agree, then solve again. | UNITS_MISMATCH |
| “The solve did not finish within Rhino.Compute’s time limit (100 s), which usually means the model cannot converge” | Check the edge types and the frame, or simplify the model. The same model fails the same way if you send it again unchanged. | COMPUTE_TIME_LIMIT_EXCEEDED |
| “Solver exceeded the allowed time limit” | Simplify the geometry, or try again later. | COMPUTE_TIMEOUT |
| “Solver encountered an internal failure” | Try again; if it keeps happening, contact support. | COMPUTE_INTERNAL_ERROR |
| “Network or HTTP error communicating with the compute backend” | Try again later; if it keeps happening, contact support. | COMPUTE_HTTP_ERROR |
| “System capacity exceeded; unable to accept new runs” | Wait a few minutes and try again. | SYSTEM_OVERLOAD |
| “Calculation is temporarily unavailable” | Keep working; your last results stay. Try again shortly. | FABRICATION_ENGINE_UNAVAILABLE |
| “The calculation failed unexpectedly” | Try again. If it keeps failing for this project, send the support: line, with its reference, to support. |
FABRICATION_ENGINE_ERROR |
| “The calculation did not finish in time” | Try again. If this project always times out, make it smaller or contact support. | FABRICATION_ENGINE_TIMEOUT |
| “The calculation service is at capacity” | Wait a moment and try again. | FABRICATION_ENGINE_CAPACITY |
| “Per-IP submission rate limit exceeded”, “Organisation concurrent active-run limit exceeded”, “Same-project cooldown is active”, “Per-org plugin API rate limit exceeded” | You sent many requests in a short time. Wait a moment, or until your other solves have finished, and try again. | RATE_LIMIT_IP, RATE_LIMIT_ORG_CONCURRENT, RATE_LIMIT_PROJECT_COOLDOWN, RATE_LIMIT_ORG_API |
| “Request body exceeds the maximum allowed size” | The drawing sent is too large. Solve fewer wireframes at a time. | PAYLOAD_TOO_LARGE |