Troubleshooting

Check the obvious first.

Runebender is alpha, so many failures should be treated as useful evidence rather than user error. Start with the source checkout, command, UFO path, and exact behavior before assuming the docs are current.

StatusAlpha diagnostic notes
AudienceEarly users, testers, contributors, agents
SourceWebsite docs and Runebender Xilem README
StabilityExpected to change as packaging and UI mature

Build or launch

First checks
RustConfirm a current Rust toolchain. The source README currently lists MSRV 1.88.
CheckoutRun commands from the root of runebender-xilem, not from this website repo.
CommandTry cargo run before adding file paths or verbose flags.
LogsUse cargo run — —verbose when collecting detail for an issue.

Opening UFOs

  • Use an included example first: assets/untitled.ufo or assets/hyper-matisse.ufo.
  • Keep real font sources in version control before testing alpha editing behavior.
  • If a path fails, verify it relative to the source repo root.
  • Use Examples to choose which included UFO matches the behavior you are testing.

Tracing

Image-to-outline checks
Background imageImport, align, and scale the bitmap before judging tracing output.
Local tracingUse img2bez first when offline behavior or reproducibility matters.
Cloud tracingQuiverAI requires network access, API credentials, and API credits.
CleanupExpect traced outlines to need manual review and metric adjustment.

Format behavior

  • Use Format for orientation, then verify exact behavior in the source repo.
  • Use the canonical hyperbezier UFO extension spec for storage details.
  • Use assets/hyper-matisse.ufo when testing hyperbezier-specific behavior.
  • Convert hyperbeziers to cubic outlines before relying on tools that do not understand Runebender extensions.

Reporting

When a problem looks real, collect the smallest useful report.

  • Source repository commit or checkout date.
  • Command used to launch the app.
  • UFO path or example file name.
  • Expected behavior and actual behavior.
  • Whether the problem affects local tracing, QuiverAI tracing, normal cubic outlines, or hyperbezier outlines.