Add illustrated workflow walkthroughs

This commit is contained in:
2026-10-14 12:22:29 +00:00
parent 862b94902e
commit eb9045b9a2
24 changed files with 242 additions and 0 deletions
Binary file not shown.

After

Width:  |  Height:  |  Size: 161 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 275 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 110 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 320 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 190 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 235 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 84 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 170 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 314 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 206 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 214 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 167 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 105 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 426 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 292 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 76 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 483 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 102 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 342 KiB

+66
View File
@@ -0,0 +1,66 @@
# Walkthrough: building a living district sheet
District sheets sit before establishment rendering. They register a close district bitmap to the whole-city map,
carry forward established pins, and fill unused label capacity with clearly marked proposals. Those background places
make the city feel inhabited without spending tier-1 effort on every doorway.
## 1. Keep both source scales
![Whole-city map reduced for registration](img/district-whole-city.jpg)
Start with the whole-city map and the untouched district bitmap. Do not re-export either to make them fit. Match
several distinctive roof patches, estimate one scale-and-translation transform, and inspect the residuals. In the
worked north sheet, 25 full-resolution patches gave scale 0.30233, translation (568.72, 191.08), and RMS error 0.06
sheet units.
![Whole-city pins projected through the registration](img/district-registration-pins.jpg)
Project the existing whole-city pins through that transform. A pin stays attached to its real map building. If it
falls under the template veil or outside the placeable window, omit it or create another district sheet—never slide it
to a convenient roof.
## 2. Define the district before adding places
![District windows and the proposed boundary street](img/district-windows-boundary.jpg)
A district boundary may be absent from the art. Trace it from street geometry and mark it **PROPOSED** until the GM
rules on it. The boundary decides which sheet owns border establishments and constrains where new places may be sited.
## 3. Populate the template
![Populated district sheet](img/district-sheet.jpg)
The sheet template supplies 22 label/subtitle slots, a legend, a parchment veil, and a placeable map window. The build
stage:
1. clones icon geometry from the template legend;
2. projects established pins from the whole-city map;
3. snaps each new proposal to an actual drawn roof, with water and neighbor clearances;
4. assigns labels to slots and routes leaders at 0, 45, or 90 degrees;
5. rejects line crossings, foreign-icon hits, legend crossings, and pins outside the placeable window;
6. exports a table carrying name, tagline, wealth tier, source status, and render tier.
In this example, the north sheet filled all 22 slots: seven established places, one previously unnamed marker, and
fourteen **PROPOSED** establishments. The proposals were not silently promoted by appearing on the map; the sheet and
its companion table kept the status explicit.
## 4. Spend detail by effort tier
Most padded places are city texture, not immediate play locations. Give them wealth tiers so architecture and goods
can be described consistently, but assign render effort separately:
- **T3:** one representative exterior when a place is likely to be noticed soon;
- **T4:** map pin, name, tagline, and a short fact only; no render until play promotes it;
- **T1/T2:** reserve for established or high-focus destinations that need multiple angles, interiors, or matrices.
This distinction is the economy of the stage: a district can feel full before the campaign pays to visualize every
shop. If play turns a proposed background pin into a destination, promote its effort tier and begin the normal
map → model → plate → frame chain.
## Template note
The source SVGs were inspected before publication. They had no SVG `<text>` nodes—the visible words were converted to
paths—and the district files linked private bitmap filenames while the whole-city file embedded hundreds of megabytes
of map data. Because path-outlined wording cannot be audited reliably by a text scan, those campaign-specific SVGs
are intentionally not redistributed here. Build from a fresh 1600 × 900 SVG with your own title, legend, veil,
22 label/subtitle groups, and linked district bitmap, then keep all live wording as `<text>` for future audits.
+48
View File
@@ -0,0 +1,48 @@
# Walkthrough: an upstairs shop room
Interiors use the same chain as a city exterior: locate the building, construct one measured room, place cameras,
render untextured plates, then re-surface without moving the set.
## 1. Map position and camera plan
![Map context and camera plan for the upstairs room](img/interior-map-camera.jpg)
Rúnaföngin is an 8.0 × 6.6 m two-story building. The shop occupies the upper floor. Its modeled interior is 6.8 ×
5.4 m, open to a steep roof: eaves 2.6 m above the floor and ridge about 5.5 m. Camera A stands just inside the upper
door at a 1.6 m eye height; camera B looks back from the northwest end. Both use an 86-degree horizontal field of view.
## 2. Build what must agree from both directions
The room model includes:
- 0.6 m walls, open rafters, ridge beam, purlins, and tie beams at x = 2.2 m and 4.6 m;
- a 3.1 m long, 1.0 m high counter beside the southwest wall;
- floor-to-roof shelving at 0.42 m vertical intervals;
- a center table, benches, stools, a small iron stove, and its flue;
- a northwest gable window looking onto a tree, plus a high southeast gable window;
- herb and feather bundles hanging from both tie beams.
Those are solids, not a list of hoped-for objects. Door, windows, counter, beams, and stove therefore remain on the
same walls in both views.
## 3. Render and inspect the plate
![Untextured room plate from camera A](img/interior-plate.jpg)
The plate carries the complete composition: roof volume, openings, furniture scale, sight lines, and hanging bundles.
Color classes identify materials and light sources. The plate gate checks exits, the counter against the 1.6 m eye
line, edge artifacts, and whether a supposed opening is actually in an exterior wall.
## 4. Re-surface the same tripod
![Finished people-free room frame](img/interior-frame.jpg)
The surface pass turns color-keyed blocks into dark timber, shelves, stoppered pots, closed books, metalwork, herbs,
and daylight. It does not get permission to redesign the room. The chosen frame's only recorded QC note was banding
on some book spines, with no readable lettering at inspection zoom.
![Room plate and final frame side by side](img/interior-side-by-side.jpg)
The comparison makes interior continuity easy to audit: the upper door, window, counter, central table, roof pitch,
and tie-beam lines stay registered. Once this people-free keeper exists, later occupied scenes can descend from it
without rebuilding the room.
+80
View File
@@ -0,0 +1,80 @@
# Walkthrough: Royal Castle battlements from measurements to pixels
This is the full method on a tier-1 landmark. The source map fixed the footprint, wall lines, towers, keep, hall wing,
and two gates. The model then made every missing construction choice explicit before the renderer saw anything.
## 1. Register the castle and choose a camera
![Map crop with the aerial camera and view frustum](img/royal-castle-map-camera.jpg)
The castle was traced from the district map into a meter-based local frame. Camera C sits 185 m south-southwest of the
castle center and 220 m above it, pitched down 50 degrees with a 58-degree horizontal field of view. The same camera
record drives the map projection, block plate, and final frame; there is no hand-matched perspective later.
## 2. Turn the drawing into construction facts
The map supplied the large masses. The model named the rest:
| element | model value |
|---|---:|
| curtain | 3.2 m thick; walk level 10.0 m |
| square corner towers | about 16 m to their fighting tops |
| keep | 21 m |
| hall wing | 13.5 m |
| original merlon rhythm | 1.3 m merlon + 1.1 m opening |
| enriched wall-walk merlons | 1.4 m wide, 0.9 m openings, 1.4 m high |
| stone walk + timber gallery | 2.3 m + 1.8 m = 4.1 m fighting platform |
| gallery structure | joists every 1.2 m; struts and rail posts every 2.4 m |
| clear lane inside the curtain | 4.5 m |
| outer gate opening | 4.4 m wide; 4.6 m spring line; 7.0 m deep |
| inner gate opening | 3.3 m wide; 2.8 m spring line |
| raised portcullis | bottom edge 5.25 m above the passage |
| gate hoarding | 1.6 m projection; floor at 15.8 m |
The numbered plan distinguishes the map-derived shell from the added program: wall access, bent gate passages, inner
cross-walls, yards, service buildings, and the 35 × 10 m garrison hall. The additions remain inside the map outline;
only the gate hoardings project beyond it.
![Labeled top-down construction plan](img/royal-castle-plan.jpg)
The wall section is the useful reality check. It shows that “a wall-walk” is not a prompt adjective: it is a 2.3 m
stone walk plus a 1.8 m timber deck, joists, ledger, edge beam, diagonal struts, stone corbels, breastwork, looped
merlons, and an inner rail.
![Measured wall-walk section and elevation](img/royal-castle-section.jpg)
## 3. Let the camera turn meters into plate pixels
![Untextured aerial block-model plate](img/royal-castle-plate.jpg)
The ray marcher projects every solid through the stored pinhole camera. At 2048 px wide and 58 degrees horizontal
field of view, the focal length is about 1,847 px (`1024 / tan(29 degrees)`). A projected span is therefore determined
by its meter width, depth, and camera transform—not by a prose estimate. Merlons repeat at their 2.3 m pitch; the
4.1 m walk has two separately modeled bands; the 10 m curtain, 16 m towers, and 21 m keep establish the vertical
hierarchy. The renderer receives those relationships as pixels.
Before any surface pass, the plate was checked against 38 map constants. The footprint gate found no added ground
area outside the source outline except the elevated hoardings, which project at most about 2 m beyond it.
## 4. Re-surface without redrawing
![Photoreal aerial frame](img/royal-castle-frame.jpg)
The edit model was told to treat the plate as the set and change surfaces only: granite ashlar, tarred timber, slate,
shingle, gravel, daylight. Camera C's keeper measured 1.005 scale, 0.05 degrees rotation, and a 3.1 × 0.1 px shift
against its plate. Target-region correlation was 0.63.
![Plate and final-frame comparison](img/royal-castle-side-by-side.jpg)
The side-by-side is the core test: walls, towers, courts, roof lines, and large openings should occupy the same image
regions before and after surface generation.
## 5. A model error stays a model error
The first model split the L-shaped hall wing into two prisms and accidentally generated twelve merlons on their
internal seam. The false wall was already visible in the plate, so prompting could not honestly fix it. The face list
was corrected, the plate was regenerated, and only 902 geometry pixels changed in aerial C. That is the payoff of a
single source of geometry: repair the solid, then re-run every dependent image.
**Takeaway:** the detail is not decorative bookkeeping. Exact dimensions create repeatable plate pixels, and those
pixels make cross-angle continuity measurable.
+48
View File
@@ -0,0 +1,48 @@
# Walkthrough: locking one shop sign across every angle
A sign is a small object with an outsized continuity cost. If it exists only in the prompt, every camera and weather
cell can invent a new one. Svein's Fine Gemstones solved that by making the sign part of the geometry and testing it
as its own landmark.
## 1. Four cameras, one modeled storefront
![Map footprint and the four camera frustums](img/sign-map-camera.jpg)
The map fixes a 14.7 × 12.5 m corner footprint and an east-west ridge. The view family has paired keepers for each
camera: **A/B** approach, **C/D** corner, **E/F** storefront, and **G/H** aerial. The plate model rebuilds the
recognizable storefront inside that footprint.
The sign is a 0.9 × 1.1 m blue heater shield with a narrow gilt rim. A faceted blue gem forms the pivot of gold
balance scales. It hangs flat on the stone pier beside the door, with no lettering. Modeling its size, face, bracket,
and attachment point gives every camera the same object to project.
## 2. Plate, surface, compare
![Face-on storefront plate](img/sign-plate.jpg)
Camera C in the production set is the face-on storefront view. The shield silhouette and its pier location exist in
the plate before any surface generation.
![Finished storefront frame](img/sign-frame.jpg)
Every day render also received a close crop of the established sign as a material-and-design reference. Geometry
came from the plate; color and emblem detail came from the crop.
![Plate and finished views side by side](img/sign-side-by-side.jpg)
## 3. Gate the sign as a landmark
A blue-shield locator cropped the expected sign region from every take. One aerial candidate returned only a bracket
and the wrong storefront, so it failed and was replaced. The eight day keepers then became the roots of the weather
and time matrix; derived cells were edits of those keepers, not fresh redraws.
![The established sign beside all eight day keepers](img/sign-lock-day.jpg)
![The sign crop across all 72 angle, time, and weather frames](img/sign-lock-matrix.jpg)
The final matrix contains four views × two keepers × nine conditions. Derived frames held to their day source within
0.5% scale, 0.1 degrees rotation, and 8 px translation. At aerial scale the sign is blurry, which is acceptable; its
blue shield, placement, and emblem family remain recognizable.
**Takeaway:** encode identity twice—coarse silhouette and placement in the model, fine design in a dedicated
reference—then crop and inspect the feature across the whole family.