Tags: mmp/vice
Tags
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>
PreviousNext