Troubleshooting

Report a problem

Found a bug, or something that does not behave the way the reference says it should?

No account or sign-in is required. The form asks what you saw and how to reproduce it.

Easiest — from inside Grasshopper (Antlion 1.0.2 or later): right-click the License component → Report a problem. It opens this form with your Antlion, Rhino and Windows versions already attached. It also attaches the document’s units, the last six characters of your license key and the most recent error message, which can contain file paths — see the privacy policy.

If the plugin does not load, use the link above and include your Rhino and Windows details: run SystemInfo in Rhino, right-click the text in the window that opens → Copy All, and paste it into the form.

Two things that make a report fixable

New to Grasshopper? These are the two steps people most often miss. Either one on its own usually lets us find the cause without asking you anything further.

1 — Internalise the geometry before you save the file. A Grasshopper definition only references the curves and surfaces in your Rhino document. Sent as-is, it opens empty on our side and there is nothing to look at.

Select the components you used, or just the input parameters holding your Rhino geometry
Right-click that input → Internalise data
The wire to Rhino disappears and the geometry is now stored inside the definition
File → Save Document As…, and attach that copy

The internalised file contains only the geometry you internalised — not your Rhino document.

2 — Or paste the debug output instead. Most Antlion components have a Debug output, and it is often faster than sending files.

Double-click empty canvas, type panel, press Enter
Drag a wire from the component’s Debug output into that panel
Right-click the panel → Copy Data Only
Paste it into the report form

If the component shows an orange or red bubble, copy that message too: right-click the component → Runtime warnings (or Runtime errors) and click the message — that puts it on the clipboard.

Attaching the Grasshopper definition that shows the problem is the single most useful thing you can do — please internalize the input geometry first, so the definition reproduces on its own without your Rhino model. Screenshots are fine for anything visual. We do not ask for your model file.

Every fix ships in a release and is listed in the changelog. Leave an email if you want to be told when yours is fixed, and a display name if you would like the credit in the release notes.

Subscription, payment and invoice questions are handled by Polar, the merchant of record for this product — use the customer portal (the link in your purchase email, or right-click License → Manage subscription) rather than the report form.