Skip to content

Tags: mmp/vice

Tags

v0.14.6

Toggle v0.14.6's commit message
Release 0.14.6

v0.14.5

Toggle v0.14.5's commit message
Release 0.14.5

v0.14.4

Toggle v0.14.4's commit message
Release 0.14.4

v0.14.4-beta2

Toggle v0.14.4-beta2's commit message
eram: preserve 300-NM default when ARTCC config omits range

Previously the shared facility default fa.Range = 50 in
validateSTARSAdaptation clobbered ERAM's 300-NM vertical default, so
ARTCC configs without an explicit "range" (ZAU, ZFW, ZOB) opened ERAM
at stored Range=50, which the render path now halves to 25-NM
half-height. Drop the universal 50 fallback and apply a scope-specific
default at the consumer: STARS keeps 50, ERAM uses the value from
makeDefaultPreferences (300). Each scope still honors an explicit
facility/scenario/area/controller range when one is set.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

v0.14.3

Toggle v0.14.3's commit message
Release 0.14.3

v0.14.2

Toggle v0.14.2's commit message
Release 0.14.2

v0.14.1

Toggle v0.14.1's commit message
Update release notes for 0.14.1

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

v0.14.0

Toggle v0.14.0's commit message
cmd/vice: update whatsnew.go for release

v0.13.3

Toggle v0.13.3's commit message
server: bump RPC version

v0.13.2

Toggle v0.13.2's commit message
Docs and whats new for release