Support

Something broke. Tell us properly.

A good bug report is worth more to us than a good review. Fill this in and it lands in the development queue with everything needed to reproduce it — no back-and-forth asking which version you are on, because the form already asked.

Bug report

AlgoNest version Help › About, or the window title bar.

Windows version

Where it happened

How bad is it

What did you expect, and what happened instead

Steps to get there

Machine and controller

Files that show it The nest file (.algonest), the DXF that misbehaved, the G-code it produced. Attach whatever you have — we will not ask what is in them beyond what is needed to fix this, and they are deleted once it is fixed.

Your email Only used to reply about this report, and to tell you which release fixed it.

The form is not wired up yet — until it is, send the same information to [email protected] and it will get the same treatment.

What happens to it

Every report is read by a person and reproduced against the current build before anything else happens. If it reproduces, it becomes a failing automated test first and a fix second — which is why bugs in AlgoNest tend not to come back. If it does not reproduce, you get an email asking for the one detail that would make it, not silence.

Fixes ship often

Small releases, frequently, rather than a big one twice a year. A bug reported on Tuesday with a file attached has a decent chance of being fixed by the weekend — no promises, but that is the shape of it.

Licence and invoice questions

Lost key, new computer, wrong VAT number on an invoice, a purchase order your accounts department insists on: [email protected]. Include the email address the licence was bought with and it will be quick.

We do not publish a phone number. One person writing this program can either answer the telephone or fix your bug, and we have made our choice.