valentineus/fparkan
1
Fork 0
Code Issues Pull Requests 2 Actions Releases Activity

docs(terrain): trace generated shade profiles

Browse Source
This commit is contained in:
Valentin Popov
2026-07-18 18:12:23 +04:00
parent 6ab2f0bc22
commit cc7a1a0faa
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tomes/05-render.md
+12 -2
View File
@@ -1620,8 +1620,18 @@ mapped record is stored as `profile_record_base + 28 * record_index` with the
new bank byte; a mapping whose second index is `-1` stores only the profile new bank byte; a mapping whose second index is `-1` stores only the profile
ordinal, below `0x1000`, and is deliberately rejected by the lookup routine. ordinal, below `0x1000`, and is deliberately rejected by the lookup routine.
This explains the runtime sentinel without interpreting it as a missing WEAR This explains the runtime sentinel without interpreting it as a missing WEAR
row. The input map is not yet tied to a named on-disk stream, so this proves the row. The input map is not a direct `Shade.wea` decode: the sole call site is
cache builder's mechanics but not its complete asset-to-profile mapping. the terrain loader at `Terrain.dll` RVA `0x0a3f0`, after it has generated and
stitched 28-byte terrain records. That loader first appends pairs copied from
an intermediate primitive-key list with second value `-1`, then appends one
`(-1, generated_record_index)` pair for every generated record. Before calling
the cache builder it runs a three-edge matching pass over those records, using
their quantized positions and adjacency selectors. The cache profile therefore
describes loader-produced geometry and its generated correspondence map, not a
named on-disk `Shade.wea` section. The source of the intermediate primitive-key
list and the exact semantics of the 28-byte record's non-position fields remain
unassigned; this is sufficient to rule out an invented static WEAR parser, but
not to reproduce the profile generator yet.
On success the method returns the shared result view at cache offset `+24`, not On success the method returns the shared result view at cache offset `+24`, not
the stored-record pointer and not a WEAR row. Thus the dispatcher's observed the stored-record pointer and not a WEAR row. Thus the dispatcher's observed