Repository navigation
Releases: FlyingfrogFR/Sweatbox-Builder
Releases · FlyingfrogFR/Sweatbox-Builder
Release list
Sweatbox Builder v7.11.1
- Fixed: scenarios that would not open. Everything the app saves lives in
the webview's local storage, which has a hard limit of about 5 MB. When it
filled up, the app carried on as if it had saved: a scenario created at
that point was listed in the rail but never written, and clicking it later
did nothing at all — the "frozen" scenario. REWIND history was the usual
culprit: ten full copies of the traffic board per scenario add up fast.- A refused save now opens a STORAGE FULL dialog that shows what takes
the space (scenarios, REWIND history, navdata, pool) and offers
FREE SPACE — hold to confirm — which drops every scenario's REWIND
history, the one thing that is always safe to lose, and saves again. A
webview that refuses to store anything at all gets its own message
instead, since freeing space would not help there. - A new scenario, a clone, an import or a rename is only added to the rail
once it is actually saved; a refused rename or slot switch leaves the
scenario exactly where it was and says so. - Slots that already are ghosts show NO SAVED DATA on the rail; click
one and it opens empty with a note (there was nothing to lose). A slot
whose data is unreadable shows UNREADABLE and says so when clicked;
⋯ → DELETE removes it. - Each scenario's REWIND history is now capped by size as well as depth.
- A refused save now opens a STORAGE FULL dialog that shows what takes
- If the display ever stops on an error, a recovery screen now offers a
rescue copy — every saved scenario, the pool and the navdata as one
file, never your GitHub token — and a reload, instead of a blank window.
Full Changelog: v7.11.0...v7.11.1
Sweatbox Builder v7.11.0
- Departures carry on after the SID. A pool departure rule with a shared
SIM ROUTE TEMPLATE used to end every aircraft's sim route at the template's
last fix, so in EuroScope they stopped following a route one or two
waypoints out. A new JOIN FILED ROUTE latch (DEPARTURE ROUTING, next to
ROUTE MUST CONTAIN) makes each aircraft fly the template up to its SID exit
— the first fix of its plan that ROUTE MUST CONTAIN names, or failing that
the last template fix its plan shares — then its own filed route from
there.DCT, the destination and fixes not in your navdata are left out of
the tail, and FP RTE is untouched. A plan with no join point keeps the
template only and the rule's note says how many. Rulesets that already
carryjoinFiledRoute: truestart working as written; everything else
generates exactly as before. - Arrivals spawned on an IAF now sit on the STAR track. The pre-entry
offset reads the rule's STAR template as a last resort for the inbound
bearing. A real flight plan ends at the STAR entry and the sim route starts
at the spawn fix, so an aircraft placed on an IAF used to be backed off
along the reverse of the NEXT leg — off the STAR, as seen at OKIPA. The
editor's offset preview shows the same position the file gets, and the
rule's never-on-fix check reads the same routes, so a few aircraft it used
to skip for lack of an inbound leg are now kept. Scenarios whose aircraft
already had a fix before the spawn point are unchanged, and the parity
fixtures are byte-identical.
Full Changelog: v7.10.0...v7.11.0
Sweatbox Builder v7.10.0
- Strip the DCTs. Real filed routes are cluttered with
DCTtokens you
may not want in a sweatbox file. A STRIP DCT key, with a count of what it
will change, now appears wherever there is something to strip:- Aircraft editor — beside FP ROUTE and beside SIM ROUTE (the count is
the tokens in that field). Press, check the result, SAVE. - Traffic board — with the CLEAR keys, counting the airborne aircraft
still carrying DCT; one press cleans every one of them. A snapshot is
taken first, so REWIND brings the DCTs back. Ground traffic keeps its
routes: itsDCT <dest>placeholders are the ground generator's own. - FPLN POOL — in the row editor beside ROUTE, and in the footer for
the selected rows you can see. The footer key is hold-to-confirm,
because the pool has no REWIND. - Rule editor — in the ROUTE TEMPLATES header, covering the FP
template, the routes picked from the pool and the sim template, so
RUN RULES stops bringing the DCTs back.
- Aircraft editor — beside FP ROUTE and beside SIM ROUTE (the count is
- Only the
DCTtokens go; fixes, airways, speed and level suffixes stay
exactly as filed, and a route with no DCT is left untouched. The aircraft
then behaves exactly as if the route had been filed without them. Nothing
is removed unless you press the key — existing scenarios export exactly as
before.
Full Changelog: v7.9.0...v7.10.0
Sweatbox Builder v7.9.0
- Edit a flight plan without leaving the pool. Every row in FPLN POOL →
POOL now has a pencil. Press it and the row opens in place: callsign,
aircraft type, departure, arrival, flight level, squawk and the full route,
each in its own box. Enter saves, Escape cancels. A callsign that another
entry already uses is refused on the spot, with the reason shown — two
entries sharing one would silently merge the next time anything was added. - Copy a plan into a whole family. The copy button next to the pencil
makes a copy of the entry under the next free callsign: the last character
is swapped for a letter, A to Z —AFR1234becomesAFR123A, then
AFR123B, and so on. Select several entries and the footer offers
COPY ×N for up to 25 copies of each in one go. A copy is the entire entry
— route, squawk, type, level, where it came from — and a pool rule spawns
one aircraft per entry, so ten spaced inbounds on a route you fetched once
are a few clicks away. Copies sit right under their original, and copies of
a selected entry are selected too, ready for ADD TO BOARD. - Letters already taken in the pool are skipped, so copying twice never makes
a duplicate, two originals that differ only in their last digit never
collide, and the family stops when the alphabet runs out. The footer only
copies the selected rows you can see, and if the callsign filter would hide
the fresh copies it is cleared and the message says so. - The row actions (edit · copy · remove) appear when you hover a row, as they
do on the traffic board.
Full Changelog: v7.8.2...v7.9.0
Sweatbox Builder v7.8.2
- No more hard-coded LFPG. A rule with no home airport of its own used to
be given Paris — an old default from the app's LFPG origins. It now takes
this scenario's airport: the ICAO on the export plate (pinned, or read
from the slot name / your Setup controllers). Importing an older ruleset
stamps that airport onto each rule, visible and editable in HOME ICAO; a
rule left without one shows "inherits LFBB from the scenario" in the editor. - If the scenario has no airport yet and a rule needs one, RUN RULES says so —
"No home airport: set HOME ICAO on the rule, or give the scenario one" —
instead of quietly generating traffic for an airport nobody chose. - Rules with an explicit home, or an explicit blank (overflight), are
untouched. Pool-sourced rules never needed one and are unaffected.
Full Changelog: v7.8.1...v7.8.2
Sweatbox Builder v7.8.1
Housekeeping release — nothing you do changes, two things get quicker.
- The scenario rail no longer slows down as you save more sessions. It
used to re-read every saved slot from disk on every keystroke anywhere in
the app; it now only re-reads a slot when that slot actually changes. - Slightly smaller download. The old tabbed interface from before
FLIGHTDECK was still being shipped inside the app even though nothing could
reach it any more. It is gone from the build (and kept on theclassic
branch of the repository for reference). - Under the hood: a lookup table replaces a per-aircraft scan when writing the
.scn, and a duplicate autosave copy that only the old interface read is no
longer written. The generated file is byte-for-byte identical — the parity
suite against the original prototype still passes.
Full Changelog: v7.8.0...v7.8.1
Sweatbox Builder v7.8.0
- Name your export files whatever you like. The filename plate now has a
CONVENTION / CUSTOM switch. CONVENTION is what you had — ICAO, version,
config, number. CUSTOM is one field: type the name and that is the file, so a
session called "LFBB north — session 3" no longer has to be squeezed into
four boxes. The extension is still added for you, and characters Windows
rejects are dropped, so a custom name can never produce a file EuroScope
won't read. - The choice belongs to the save slot, like the rest of the plate: one scenario
on a typed name and the next on the convention, and neither borrows from the
other. - SAVE RULESET asks where to put it. It used to drop a file straight into
Downloads named after the scenario, with no dialog — which is how you lose
one. It now opens the same Save-As dialog as EXPORT and uses the same name
you chose on the plate, ending in_RULESET.json.
Full Changelog: v7.7.1...v7.8.0
Sweatbox Builder v7.7.1
- Release notes you can actually read. Every release now carries proper
notes, both on the Releases page and in the update prompt, instead of a bare
link to a list of commits. The history back to 7.0.0 is written up in
CHANGELOG.md. - Clearer sharing. The third block in FPLN POOL → SHARE was called PUBLISH,
which read as "publish to the library" — it does not. It is now SHARE THIS
POOL, it makes a private share code, and it says in as many words that a
code is not a library entry and that getting into the library means opening
a pull request. - Your share codes are listed. Codes you have made are kept in a list with
a COPY button each, instead of only ever showing the most recent one, so a
code from last week is still findable. Codes saved by 7.7.0 appear there too. - This is also the first release that installs itself: if you are on 7.7.0,
the app should offer it to you on launch rather than sending you to the
Releases page.
Full Changelog: v7.7.0...v7.7.1
Sweatbox Builder v7.7.0
Full Changelog: v7.6.0...v7.7.0
Sweatbox Builder v7.6.0
Full Changelog: v7.5.0...v7.6.0