Integrate district-sheet stage into workflow
This commit is contained in:
@@ -5,8 +5,12 @@ pictures: the first view from the road, the gate, an aerial of the market block,
|
||||
midnight when it is packed, the same street in a blizzard. Every picture of a place agrees with every other picture
|
||||
of it, because they all descend from one 3D block model traced from your map.
|
||||
|
||||
Developed for a Norse-themed D&D campaign by Rick Falkvinge, with the agents that ran the render lanes. Shared so other
|
||||
tables can use it with their own maps, their own renderer accounts and their own agent setups.
|
||||
Developed for a Norse-themed D&D campaign with the agents that ran the render lanes. Shared so other tables can use it
|
||||
with their own maps, their own renderer accounts and their own agent setups.
|
||||
|
||||
**See it in pictures:** [measured castle battlements](docs/walkthrough-royal-castle.md) ·
|
||||
[an interior room](docs/walkthrough-interior-room.md) · [one sign across every angle](docs/walkthrough-sign-lock.md) ·
|
||||
[a populated district sheet](docs/walkthrough-district-map.md)
|
||||
|
||||
## What it does
|
||||
|
||||
@@ -23,6 +27,10 @@ tables can use it with their own maps, their own renderer accounts and their own
|
||||
7. **Sizes the whole effort by tier**: how likely is this place to come into focus at the table? That decides the
|
||||
deliverables, the budget, which agent model runs it, and what the GM is asked to look at.
|
||||
|
||||
Before step 1, an optional **district-map stage** registers a district bitmap to the whole-city map, projects existing
|
||||
pins, and fills unused template slots with explicitly PROPOSED T3/T4 establishments on real map buildings. It gives a
|
||||
large city texture before every background doorway earns a render.
|
||||
|
||||
Why it works: words cannot carry an aspect ratio, a distance or a height, and a map given as a reference moves the
|
||||
layout but not the shape. When the geometry arrives as pixels from the target camera, the renderer only has to paint
|
||||
surface, and a correction is one edit to the model followed by a re-render of every camera.
|
||||
@@ -101,6 +109,7 @@ review pile.
|
||||
```
|
||||
SKILL.md the procedure, for agents (and humans)
|
||||
references/ pipeline, gates, prompting, matrices, effort tiers, naming, failure modes
|
||||
docs/ illustrated map → model → plate → frame walkthroughs
|
||||
scripts/ the toolkit (see SKILL.md "Reference"); smoke_test.py proves it end to end
|
||||
scripts/adapters/ renderer adapter point
|
||||
examples/ config, cameras, scene, prompts to copy and edit
|
||||
|
||||
@@ -23,6 +23,14 @@ frame against the plate. A correction is one edit to the model and a re-render o
|
||||
|
||||
## Steps
|
||||
|
||||
0. **Build district sheets when the city needs them.** Register each district bitmap to the whole-city map from
|
||||
several roof patches; record the scale, translation and residuals; project established pins through that transform.
|
||||
Fill unused template slots only with clearly **PROPOSED** establishments sited on real unoccupied roofs, each with
|
||||
a name, tagline, wealth tier and effort tier. Never move a pin to escape the template veil. Most padded places are
|
||||
T3/T4 until play promotes them. Route leaders without crossings or legend hits; see
|
||||
`docs/walkthrough-district-map.md` and `references/pipeline.md` section 0.5.
|
||||
**Done when:** registration is measured, canon and proposals are visually distinct, every pin is map-sited, label
|
||||
routing passes, and the companion table carries both tier types.
|
||||
1. **Segment the map.** `segment_map.py MAP --mpp M --out seg.npz --look look.jpg`. Eyeball `look.jpg`.
|
||||
**Done when:** roofs, trees and water are right where you will put a camera; false trees removed.
|
||||
2. **Mass the town.** `massing.py seg.npz --config citykit.json --out town.npz`. Heights come from wealth zones
|
||||
@@ -86,5 +94,6 @@ frame against the plate. A correction is one edit to the model and a re-render o
|
||||
- `references/effort-tiers.md` — tiers, deliverables, budgets, model-cost tiering, delivery policy (on trial).
|
||||
- `references/naming.md` — file and folder names, the report shape.
|
||||
- `references/failure-modes.md` — symptom, cause, fix, one line each.
|
||||
- `docs/` — illustrated castle, interior, sign-lock, and district-sheet walkthroughs.
|
||||
- `scripts/` — `segment_map.py`, `massing.py`, `scene_solids.py`, `render_plate.py`, `build_jobs.py`,
|
||||
`render_batch.py` (+ `adapters/`), `gate.py`, `qc_sheet.py`, `matrix_jobs.py`, `cost.py`, `smoke_test.py`.
|
||||
|
||||
@@ -31,6 +31,25 @@ re-render of every camera. Across angles, every frame shows the same building by
|
||||
7. **What is canon and what you are about to PROPOSE.** Terrain is almost never on a map; walls and gates may not be
|
||||
drawn; heights are never drawn. Everything not on the map is a proposal and lives as a named constant.
|
||||
|
||||
## 0.5. District sheet (optional, before rendering establishments)
|
||||
|
||||
For a large city, register each district bitmap to the whole-city map before choosing render subjects. Template-match
|
||||
several distinctive roof patches, fit one scale-and-translation transform, record the residuals, and project the
|
||||
whole-city pins through it. Keep every pin on its real drawn building. If a pin falls outside the template's placeable
|
||||
window or under its veil, omit it or make another sheet; never move the pin to improve the layout.
|
||||
|
||||
Populate the district template with the established pins first. Then use empty slots for living-city background:
|
||||
proposed establishments with a name, one-line tagline, wealth tier, and an actual unoccupied roof. Mark every invented
|
||||
field **PROPOSED** in both the sheet and its companion table. Route leaders without crossings, foreign-icon hits, or
|
||||
legend overlap, and verify label-to-pin identity after any slot permutation.
|
||||
|
||||
Assign render effort separately from wealth. Most padded places are T3 or T4: T3 may get one exterior when it becomes
|
||||
relevant; T4 remains a pin and a short fact until play promotes it. Established or likely destinations may be T1/T2.
|
||||
See `docs/walkthrough-district-map.md` for the illustrated registration → pins → boundary → populated-sheet chain.
|
||||
|
||||
**Done when:** registration residuals are recorded; established and proposed rows are distinguishable; every pin is
|
||||
on a real map building; label routes pass; and each row has both wealth and effort tiers.
|
||||
|
||||
## 1. Segment (`segment_map.py`)
|
||||
|
||||
Roof, tree and water masks. Trees are the cauliflower glyphs (dense short dark strokes in compact blobs); roofs are
|
||||
|
||||
@@ -22,7 +22,7 @@ What the method needs from a renderer, in order of importance:
|
||||
2. **A 16:9 output at 2048x1152 or similar** so the plate-to-frame registration is pixel-comparable.
|
||||
3. **No seed and no strength dial is fine.** The method never relied on either: geometry is held by the plate and the
|
||||
prompt, variance is handled by rendering 2-4 takes and gating.
|
||||
4. **A rate-limit signal** (HTTP 429 with Retry-After, or any 5xx) so the batch runner can calibrate concurrency.
|
||||
4. **A rate-limit indicator** (HTTP 429 with Retry-After, or any 5xx) so the batch runner can calibrate concurrency.
|
||||
|
||||
Return 429/5xx for "try later" conditions and any other non-200 for a hard failure. A body containing
|
||||
`safety`, `moderation`, `content_policy` or `rejected` triggers the one allowed rephrase (`prompt_alt`).
|
||||
|
||||
Reference in New Issue
Block a user