What beta testers get

  • Early access builds and feature previews
  • Priority support and direct bug-report feedback loop
  • Lemon Squeezy code redemption path for build download
  • Input on firmware/slicer compatibility priorities

Current features vs coming soon

โœ… Current (V1 focus)

  • On-Plate recovery as the default workflow
  • Mode-prefixed output naming (On-Plate_*)
  • Firmware auto-detect for Marlin, Klipper, RepRapFirmware, Anycubic, and initial Bambu/Orca markers

๐Ÿšง Coming soon (beta track)

  • In-Place (in-air) recovery re-enabled after safety hardening
  • Expanded Bambu/Orca + AMS/ACE startup compatibility
  • Larger startup sample corpus and normalization rules by vendor
  • More guided troubleshooting and profile recommendations in-app

Beta application

Complete this form and accept the beta terms below. We review applications manually and follow up by email.

Beta Terms Acceptance (required): I understand this is pre-release software and I agree not to resell, redistribute, sublicense, publish, crack, reverse engineer, decompile, disassemble, or otherwise misuse the beta build, license codes, or download links. I will use the beta only for my own testing, provide honest feedback, and report issues responsibly.

Lemon Squeezy code redemption flow

  1. Approval email includes your beta code/invite instructions.
  2. Open the Lemon Squeezy checkout/redeem link from the email.
  3. Apply your beta code/coupon in checkout (price may reduce to $0 based on campaign setup).
  4. Complete checkout to generate your order + license record.
  5. Use the download link and license key from the Lemon Squeezy receipt email inside FailFixer.

If code redemption fails, contact support@failfixer.com with the email used during checkout and (if available) the order number.

How to test each FailFixer mode

Please test with low-risk parts first and never leave the printer unattended during first runs.

Mode A: Resume In-Air (advanced)

  1. Use a print that failed mid-job but is still firmly attached to the bed.
  2. In FailFixer, choose Resume in air at fail height.
  3. Start with a conservative layer selection and verify preview details before generating.
  4. On printer start, watch closely for: safe Z lift before XY movement, no crash into existing part, and stable re-entry at resumed layer.
  5. Record outcome: success/fail, printer model, slicer, firmware profile, and exact failure point if any.

Mode B: Restart From Plate (recommended)

  1. Use the same failed original file and choose Restart from plate.
  2. Generate the rebuilt top section and print it on an empty leveled plate.
  3. Confirm first layer adhesion, normal extrusion, and correct geometry for the replacement section.
  4. Verify the replacement part aligns with the failed section for post-print glue/join workflow.
  5. Record outcome: print quality, fit/alignment, and any startup or extrusion oddities.

What to send in bug reports

  • Original source G-code (or first 150 lines + generated file first 150 lines)
  • Generated FailFixer G-code
  • Printer model + firmware + slicer version
  • Screenshots/video of startup and failure moment (if applicable)
  • Whether ACE/AMS-like multi-filament hardware was connected