lumbridge-public/tera

Archived

Fork 0

Commit Graph

Author	SHA1	Message	Date
karti	6fde2f0c97	feat: one California by default, and a box ship you can see Two complaints, and the measured cause of each turned out to be a number already written down in this repo rather than anything that needed inventing. "I see three different maps." `reconcile.ts` has existed for a round with the four rules that make three packs draw one California, behind a flag whose whole purpose was that the owner could choose from a photograph — and `DEFAULT_RULES` was empty, so nobody ever saw the reconciled board without typing a query string. The photographs are now taken, at HEAD, at a matched 17:10 and a matched pose against the live API, and two of the four rules are on: - `exaggeration`. Relief in frame is 7.24% on California, 6.92% on the Southland and 4.51% on the Bay: two boards were already on one number and one was not. The rule moves SF and only SF, 3.60 -> 5.78, and leaves the two boards every marketing still was tuned on untouched to the digit. Unreconciled, the Bay draws Tamalpais, the Berkeley hills and Mount Diablo as low smeared mounds; at 5.78 they stand up, and the chapter's own caption — "the Diablo range closing the east" — is true of the picture for the first time. - `projection`. Each pack squashed longitude by the cosine of its own centre, so California and the Southland disagreed about Riverside by 3,435 m and about their shared corner by 4,025 m: 3% of the frame at a 109 km stand-off, and a visible sideways slide in any transition showing both. One canvas cannot hold two answers for one place. `ground` stays off: its palette mix pushes the Southland's flats yellow-olive inland, because that pack's `flats` is off the one-parameter family in a direction no mix can reach. Its own comment calls it the riskiest of the four and the photograph agrees. `roads` stays off for the reason argued in the file — it rewrites a column nothing reads on the one board where the complaint shows. "I don't see boats on our ports." True, and by construction. `Crane`'s own doc note already had the cause: at SoCal's 3.4x a 130 m gantry stands 1.13 units while a 400 m ship is 1.02 units long. Exaggeration multiplies heights and a length takes 1x, so a hull is the one object on this coast that the board flattens while stretching everything around it — and eleven of fifteen hulls in a working harbour are alongside a berth, where a moored hull has no wake by design and so had nothing to be seen by. `FREEBOARD_RATIO` had already named the fix: a laden ULCV "stands about thirty metres out of the water before you count the container stack, and the stack is what makes the silhouette". The stack was never drawn. `containerHull` draws it — three bays with the forward one a tier down, eight tiers of high-cube at 0.52 of keel-to-deck depth — which buys height and nothing else. No length, no beam: a new test holds the container solid inside the merchant hull's bounding box in x and z, so a hull still cannot overhang the berth it lies in, and `vesselScale.test.ts` is green to the digit. It arrived through the seam `HULL_SHAPES` said it would — one entry, one case in `hullGeometry`, one arm in `hullShape` — which is the only evidence that seam was real rather than merely claimed. The band is a modulation map, and the first pass of it was not. Painted at `PORT_PALETTE`'s real box values under a container ship's own 0x93aac4 tint, the stack photographed near black — darker than the hull under it. `deckAtlas`'s own header had predicted that exact failure two paragraphs above where I was editing. So hue comes from the tint like every other part of every other hull, and the band carries relative value and structure: at the 25 px a stack draws at, individual box hues average to one tone and what survives is the shadow between two boxes. Adding a fourth band also had to move the other three, since they occupied 0.02..0.98 with nothing to append to, so band edges are now computed from one layout rather than typed as six literals — and the four hardcoded `v` values in the bow triangles read from it too. Three tests were pinned rather than changed: they measure packs as authored or synthetic one-hill fixtures, and each had an implicit dependency on the flag being off. Following `roadWidth.test.ts`, which already did this. Verified: 1,690 tests pass. All ten performance-budget cells pass with no cap raised — bay-area desktop 2,306,424 triangles of 2,600,000 (the taller board keeping more through the height guard), socal +284 triangles and +1 draw call for the container mesh, of 1,700,000 and 320. Frame time is not claimed either way; this box's GPU never leaves 500 MHz of 2,725. ⚠ This changes the default, so lumbridgecorp.com's 21 stills and 4 films are now pictures of a board the product no longer draws. `npm run refresh` is the whole of that work and it is not optional. `?reconcile=0` asks for the old board. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-23 23:32:51 -07:00
karti	f81d5218d4	feat: SFO, LAX, both bridges, a road that reads as a road, and aeroplanes that move The aeroplanes were stuck because the wire could not describe motion. `WireAircraft` carried position, altitude and heading and nothing else, so the client could only interpolate between the last two observations: every aircraft replayed a segment it had already flown, arrived at the newest known point, and sat still until the next poll landed five to fifteen seconds later. The feed had the missing numbers the whole time and the server threw them away. Sampled live from `api.adsb.lol/v2/point` while writing this — `gs` ground speed, `track`, `baro_rate`, plus `r` registration and `t` type designator. They are on the wire now in SI, aircraft dead-reckon along their own track and correct toward the truth when a fix lands, and the click card an anonymous visitor gets says "B739 · N68834". That last part is the enrichment FR24 was wanted for, obtained from an ODbL feed we may actually republish. SFO and LAX exist. A new `engine/airports.ts` composes an airport from runways, taxiways, aprons and terminal masses, with markings drawn on a canvas rather than modelled; the pattern of the runways is what the eye recognises from altitude, long before any building does. SFO is the two crossing pairs on the bay fill; LAX is the four parallels either side of the terminal horseshoe, plus the Southland fields under the traffic that actually flies there. The Golden Gate and the Bay Bridge are those bridges. One kit in `engine/bridges.ts`, because a suspension bridge is a repeated tower, a catenary main cable, a series of hangers and a deck — so both are configurations rather than two private implementations. The Bay Bridge carries the real 2013 topology: two suspension towers west of Yerba Buena, one east, then the piered causeway. The freeway stopped being a wireframe overlay and became a road, with shoulders, a median, and lane markings as texture. And the board got faster while all of that landed. California went from 728,744 triangles and 562 draw calls to 391,169 and 371 — headroom from 2.8% to 47.8%. The Bay Area board is 506,550 triangles lighter than before this work. Two things paid for it: - `transmission: 0.08` on the aircraft cockpit glass. three.js runs a full transmission backdrop pass whenever any rendered material has transmission above zero, re-drawing the entire opaque scene into a second target every frame — so the city was rendering terrain, every block and every freeway piece TWICE. Measured by patching only that number in a copy of the built bundle: 703,267 tris / 562 draws with it, 398,608 / 371 without. The material was already `transparent: true, opacity: 0.86`, so it was buying nothing. - Flatness-adaptive terrain LOD, which collapses runs of lattice cells wherever the height and colour agree with the quad replacing them. The coastline is provably untouched — a patch collapses only when every point is on land and agrees about `park` — and a test asserts the drawn footprint matches the cell-by-cell area to 1e-6. `createTerrain` got faster: the vertices it stops emitting cost more than the flatness scan costs to run. The budget now watches the boards this was built on. There was no `bay-area` or `socal` cell — so SFO, LAX and both bridges all landed in frames nothing measured, which is how a cap you do not have looks from the inside. Both are in the matrix now with caps set from measurement, and the rationale lives in the harness because JSON cannot hold a comment. Two known defects ship with this, both recorded in TODO.md rather than hidden: - `bay-area.desktop` drops about one frame in twenty (p50 16.7, p95 33.3). It is desktop-only and not fill rate — mobile runs the same 2.26 M triangles at a comparable pixel count and holds 16.7 flat — which points at the 2048 shadow map desktop uses against handheld's 1024. Measured at the commit before this work with the same harness: identical p95 33.3. Pre-existing, and invisible until the cell existed. - The aeroplane glyph is still about 1.5x the Golden Gate's main span at chapter zoom, down from 2.5x. `GLYPH_MAX_SCALE` is 52 because the raw scale at the far end of the California orbit is 51.0 at a 60-degree field of view, and 26 — tried first — put the glyph at 0.0123 of the frame against the 0.012 where the wings stop resolving. The real fix is to clamp against the camera's focus distance rather than the aircraft's, which is a signature change. Tests 1020 -> 1137. Typecheck, build, eight budget cells, no-binaries, provenance, zero-config boot, dependency licences, arena source hashes and the UI smoke across two viewports and two access tiers all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-22 05:06:12 -07:00

Author

SHA1

Message

Date

karti

6fde2f0c97

feat: one California by default, and a box ship you can see

Two complaints, and the measured cause of each turned out to be a number
already written down in this repo rather than anything that needed inventing.

**"I see three different maps."** `reconcile.ts` has existed for a round with
the four rules that make three packs draw one California, behind a flag whose
whole purpose was that the owner could choose from a photograph — and
`DEFAULT_RULES` was empty, so nobody ever saw the reconciled board without
typing a query string. The photographs are now taken, at HEAD, at a matched
17:10 and a matched pose against the live API, and two of the four rules are on:

- `exaggeration`. Relief in frame is 7.24% on California, 6.92% on the Southland
  and **4.51%** on the Bay: two boards were already on one number and one was
  not. The rule moves SF and only SF, 3.60 -> 5.78, and leaves the two boards
  every marketing still was tuned on untouched to the digit. Unreconciled, the
  Bay draws Tamalpais, the Berkeley hills and Mount Diablo as low smeared
  mounds; at 5.78 they stand up, and the chapter's own caption — "the Diablo
  range closing the east" — is true of the picture for the first time.
- `projection`. Each pack squashed longitude by the cosine of its *own* centre,
  so California and the Southland disagreed about Riverside by 3,435 m and about
  their shared corner by 4,025 m: 3% of the frame at a 109 km stand-off, and a
  visible sideways slide in any transition showing both. One canvas cannot hold
  two answers for one place.

`ground` stays off: its palette mix pushes the Southland's flats yellow-olive
inland, because that pack's `flats` is off the one-parameter family in a
direction no mix can reach. Its own comment calls it the riskiest of the four
and the photograph agrees. `roads` stays off for the reason argued in the file —
it rewrites a column nothing reads on the one board where the complaint shows.

**"I don't see boats on our ports."** True, and by construction. `Crane`'s own
doc note already had the cause: at SoCal's 3.4x a 130 m gantry stands 1.13 units
while a 400 m ship is 1.02 units *long*. Exaggeration multiplies heights and a
length takes 1x, so a hull is the one object on this coast that the board
flattens while stretching everything around it — and eleven of fifteen hulls in
a working harbour are alongside a berth, where a moored hull has no wake by
design and so had nothing to be seen by.

`FREEBOARD_RATIO` had already named the fix: a laden ULCV "stands about thirty
metres out of the water **before you count the container stack, and the stack is
what makes the silhouette**". The stack was never drawn. `containerHull` draws
it — three bays with the forward one a tier down, eight tiers of high-cube at
0.52 of keel-to-deck depth — which buys height and nothing else. No length, no
beam: a new test holds the container solid inside the merchant hull's bounding
box in x and z, so a hull still cannot overhang the berth it lies in, and
`vesselScale.test.ts` is green to the digit.

It arrived through the seam `HULL_SHAPES` said it would — one entry, one case in
`hullGeometry`, one arm in `hullShape` — which is the only evidence that seam
was real rather than merely claimed.

**The band is a modulation map, and the first pass of it was not.** Painted at
`PORT_PALETTE`'s real box values under a container ship's own 0x93aac4 tint, the
stack photographed near black — darker than the hull under it. `deckAtlas`'s own
header had predicted that exact failure two paragraphs above where I was
editing. So hue comes from the tint like every other part of every other hull,
and the band carries relative value and *structure*: at the 25 px a stack draws
at, individual box hues average to one tone and what survives is the shadow
between two boxes. Adding a fourth band also had to move the other three, since
they occupied 0.02..0.98 with nothing to append to, so band edges are now
computed from one layout rather than typed as six literals — and the four
hardcoded `v` values in the bow triangles read from it too.

Three tests were pinned rather than changed: they measure packs as authored or
synthetic one-hill fixtures, and each had an implicit dependency on the flag
being off. Following `roadWidth.test.ts`, which already did this.

Verified: 1,690 tests pass. All ten performance-budget cells pass with no cap
raised — bay-area desktop 2,306,424 triangles of 2,600,000 (the taller board
keeping more through the height guard), socal +284 triangles and +1 draw call
for the container mesh, of 1,700,000 and 320. Frame time is not claimed either
way; this box's GPU never leaves 500 MHz of 2,725.

⚠ This changes the default, so lumbridgecorp.com's 21 stills and 4 films are now
pictures of a board the product no longer draws. `npm run refresh` is the whole
of that work and it is not optional. `?reconcile=0` asks for the old board.

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

2026-08-23 23:32:51 -07:00

karti

f81d5218d4

feat: SFO, LAX, both bridges, a road that reads as a road, and aeroplanes that move

**The aeroplanes were stuck because the wire could not describe motion.**
`WireAircraft` carried position, altitude and heading and nothing else, so the
client could only interpolate between the last two observations: every aircraft
replayed a segment it had already flown, arrived at the newest known point, and
sat still until the next poll landed five to fifteen seconds later. The feed had
the missing numbers the whole time and the server threw them away. Sampled live
from `api.adsb.lol/v2/point` while writing this — `gs` ground speed, `track`,
`baro_rate`, plus `r` registration and `t` type designator. They are on the wire
now in SI, aircraft dead-reckon along their own track and correct toward the
truth when a fix lands, and the click card an anonymous visitor gets says
"B739 · N68834". That last part is the enrichment FR24 was wanted for, obtained
from an ODbL feed we may actually republish.

**SFO and LAX exist.** A new `engine/airports.ts` composes an airport from
runways, taxiways, aprons and terminal masses, with markings drawn on a canvas
rather than modelled; the pattern of the runways is what the eye recognises from
altitude, long before any building does. SFO is the two crossing pairs on the bay
fill; LAX is the four parallels either side of the terminal horseshoe, plus the
Southland fields under the traffic that actually flies there.

**The Golden Gate and the Bay Bridge are those bridges.** One kit in
`engine/bridges.ts`, because a suspension bridge is a repeated tower, a catenary
main cable, a series of hangers and a deck — so both are configurations rather
than two private implementations. The Bay Bridge carries the real 2013 topology:
two suspension towers west of Yerba Buena, one east, then the piered causeway.
The freeway stopped being a wireframe overlay and became a road, with shoulders,
a median, and lane markings as texture.

**And the board got faster while all of that landed.** California went from
728,744 triangles and 562 draw calls to 391,169 and 371 — headroom from 2.8% to
47.8%. The Bay Area board is 506,550 triangles lighter than before this work.
Two things paid for it:

- `transmission: 0.08` on the aircraft cockpit glass. three.js runs a full
  transmission backdrop pass whenever any rendered material has transmission
  above zero, re-drawing the entire opaque scene into a second target every
  frame — so the city was rendering terrain, every block and every freeway piece
  TWICE. Measured by patching only that number in a copy of the built bundle:
  703,267 tris / 562 draws with it, 398,608 / 371 without. The material was
  already `transparent: true, opacity: 0.86`, so it was buying nothing.
- Flatness-adaptive terrain LOD, which collapses runs of lattice cells wherever
  the height and colour agree with the quad replacing them. The coastline is
  provably untouched — a patch collapses only when every point is on land and
  agrees about `park` — and a test asserts the drawn footprint matches the
  cell-by-cell area to 1e-6. `createTerrain` got *faster*: the vertices it stops
  emitting cost more than the flatness scan costs to run.

**The budget now watches the boards this was built on.** There was no `bay-area`
or `socal` cell — so SFO, LAX and both bridges all landed in frames nothing
measured, which is how a cap you do not have looks from the inside. Both are in
the matrix now with caps set from measurement, and the rationale lives in the
harness because JSON cannot hold a comment.

Two known defects ship with this, both recorded in TODO.md rather than hidden:

- `bay-area.desktop` drops about one frame in twenty (p50 16.7, p95 33.3). It is
  desktop-only and not fill rate — mobile runs the same 2.26 M triangles at a
  comparable pixel count and holds 16.7 flat — which points at the 2048 shadow
  map desktop uses against handheld's 1024. Measured at the commit before this
  work with the same harness: identical p95 33.3. Pre-existing, and invisible
  until the cell existed.
- The aeroplane glyph is still about 1.5x the Golden Gate's main span at chapter
  zoom, down from 2.5x. `GLYPH_MAX_SCALE` is 52 because the raw scale at the far
  end of the California orbit is 51.0 at a 60-degree field of view, and 26 —
  tried first — put the glyph at 0.0123 of the frame against the 0.012 where the
  wings stop resolving. The real fix is to clamp against the camera's focus
  distance rather than the aircraft's, which is a signature change.

Tests 1020 -> 1137. Typecheck, build, eight budget cells, no-binaries,
provenance, zero-config boot, dependency licences, arena source hashes and the
UI smoke across two viewports and two access tiers all pass.

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

2026-08-22 05:06:12 -07:00

2 Commits