Hiltwright docs
How to install Hiltwright, set up a saber with it, and what every page does.
New here? Read the install guide, then the quick start. The walkthrough shows every page in pictures, and the same tour is built into the app: press "Take the tour" at the bottom of the sidebar.
The pages below follow the app's own sidebar. The saber path is the four numbered steps that take one saber from a plan to installed firmware. The workshop is where styles and fonts are kept, built and tried.
Getting started
Install guideFrom the download to your first firmware install, including every Windows warning for unsigned software.
Quick startThe whole path for a first saber, from plugging in to an installed board, in ten steps.
The saber path
ArmoryWhere you choose which saber you are working on, plan a new one, and see how far each has got.
WiringTell Hiltwright which board, buttons, prop file and blades your saber has, and confirm the pins before anything is installed.
PresetsEdit the saber's presets (font, track, style and colours), save sets of them, and undo changes from History.
Fonts & SDGet the sound fonts your presets use onto the saber's SD card, and check the card and its fonts.
Build & InstallTurn the saber's setup into firmware, install it over USB with a backup first, and put an old backup back if you need to.
The workshop
StylesBrowse the built-in styles, try colours on a live preview, put a style on a preset, or paste one from the Fett263 library.
Style editorBuild your own style from plain blocks, or edit every ProffieOS layer, and watch it on a live blade before you save it.
Font libraryKeep your sound fonts in one place on this computer, check them, hear them, and copy them to a saber's SD card.
Demo roomTry any style with any sound font on a saber in a dark room, before anything goes near a real saber.
ContributorsSee everyone whose fonts, styles and hilts you use, and how to credit a maker with a name, a logo and a link.
Help
DiagnosticsChange a saber's volume and brightness, try effects, send ProffieOS commands, and save a file to attach to a problem report.
TroubleshootingSymptoms, causes and fixes for the problems beta testers are most likely to meet, from Windows warnings to a saber that says "font directory not found".
FAQShort answers to the questions beta testers ask most, from which boards work to what Hiltwright sends over the internet.
GlossaryPlain-word meanings for the terms you will meet in Hiltwright and in the ProffieOS world.
Release notes: 0.2.0-beta.3What this beta promises, what is hidden, and what is not in it yet.
Written for Hiltwright 0.2.0-beta.3. Something wrong or missing? Tell us.