@rig-c/parts 2.43.0 → 2.45.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/cli.ts +141 -36
- package/docs/AUTHORING.md +541 -70
- package/docs/DEPTH.md +44 -3
- package/docs/MIGRATION.md +2 -0
- package/docs/STABILITY.md +357 -39
- package/package.json +1 -1
- package/src/boundarydepth.ts +113 -0
- package/src/check.ts +296 -78
- package/src/cloth.ts +14 -3
- package/src/config.ts +78 -11
- package/src/configwrite.ts +3 -3
- package/src/diffdrafts.ts +593 -0
- package/src/editedparts.ts +11 -2
- package/src/externalreceipt.ts +130 -0
- package/src/maskvalues.ts +21 -0
- package/src/outputpaths.ts +40 -0
- package/src/parts.ts +14 -5
- package/src/plate.ts +2 -6
- package/src/propose.ts +165 -8
- package/src/receiptproducer.ts +41 -0
- package/src/remesh-api.ts +33 -0
- package/src/remesh.ts +197 -19
- package/src/remeshdelta.ts +143 -30
- package/src/rig.ts +95 -21
- package/src/runstamp.ts +16 -0
- package/src/scene.ts +440 -54
- package/src/sceneclips.ts +198 -0
- package/src/turn.ts +24 -3
- package/tools/edited-part-cli.ts +12 -3
package/docs/DEPTH.md
CHANGED
|
@@ -54,6 +54,27 @@ anchor; its own median is not subtracted again. Thus two touching parts retain
|
|
|
54
54
|
their declared depth difference when they turn. Head and body groups have
|
|
55
55
|
separate anchors, and this applies to generated grids and authored meshes alike.
|
|
56
56
|
|
|
57
|
+
For an abutting body surface such as a sleeve, author the boundary depths in
|
|
58
|
+
that same group space. At yaw angle `a`, the horizontal travel is
|
|
59
|
+
`-(pivot + z - zRef) * sin(a)`, so the jump across a touching pair is
|
|
60
|
+
`abs(zA - zB) * abs(sin(a))`: the common pivot and reference cancel.
|
|
61
|
+
Matching medians does not match boundary depths when the relief differs.
|
|
62
|
+
Conversely, replacing each surface's own median with the shared anchor adds
|
|
63
|
+
`-(ownMedian - zRef) * sin(a)` uniformly to that surface; it can enlarge one
|
|
64
|
+
seam while reducing another. This is placement, not a sleeve-specific scale.
|
|
65
|
+
Where continuity is intended, declare `turn.body.boundaryDepths` so a named
|
|
66
|
+
band takes the original neighbour sheet's sampled boundary depth. Samples use
|
|
67
|
+
the nearest shared boundary; depths at distinct equidistant projection candidates
|
|
68
|
+
are combined by their arithmetic mean. The head equivalent is
|
|
69
|
+
`turn.boundaryDepths`. The band may be the target itself or a
|
|
70
|
+
contained existing part made with `assemble.patches`; the declaration and a
|
|
71
|
+
concrete patch example are in
|
|
72
|
+
[Declared boundary depths](AUTHORING.md#declared-boundary-depths-1342).
|
|
73
|
+
The band uses a hard switch, so inspect stretch at its inner edge as well as
|
|
74
|
+
the shared seam at both turn extremes. No calibration is retuned. Choosing a different shared reference leaves the seam jump unchanged.
|
|
75
|
+
Neither a per-sleeve pivot nor a guessed correction is inferred. A seam reading
|
|
76
|
+
measures depth discontinuity, not composite visibility.
|
|
77
|
+
|
|
57
78
|
See-through, the layer decomposition this package reads, also writes a per-layer
|
|
58
79
|
depth sheet, and a config can register those directly (`config.depth`,
|
|
59
80
|
[Per-layer depth sheets](AUTHORING.md#per-layer-depth-sheets-773)). In
|
|
@@ -131,7 +152,27 @@ which one you ran. Model licences are the model's own and are not this
|
|
|
131
152
|
package's to restate — the site's [licensing page](https://rig-c.org/docs/licensing/)
|
|
132
153
|
says where each kind of term sits.
|
|
133
154
|
|
|
134
|
-
### 3.
|
|
155
|
+
### 3. Bind every map to its prepared input
|
|
156
|
+
|
|
157
|
+
After the model writes each numeric map, bind those exact bytes to the input
|
|
158
|
+
image you supplied:
|
|
159
|
+
|
|
160
|
+
```sh
|
|
161
|
+
rig-parts depth-bind --map face.json --input inference/face.png --part face
|
|
162
|
+
rig-parts depth-bind --map hair_front.json --input inference/hair_front.png --part hair_front
|
|
163
|
+
rig-parts depth-bind --map hair_back.json --input inference/hair_back.png --part hair_back
|
|
164
|
+
```
|
|
165
|
+
|
|
166
|
+
This writes a sibling `<map>.binding.json` receipt containing the part name
|
|
167
|
+
and the map and input SHA256 hashes. It records the files you name at invocation;
|
|
168
|
+
it does not prove the model inferred one from the other. Use each recipe map
|
|
169
|
+
path and its matching prepared image, retain the receipts with the maps, then
|
|
170
|
+
apply them. Existing receipts are never overwritten. If a map changes, retain
|
|
171
|
+
the old map and receipt and bind the new map at a new path; update the recipe
|
|
172
|
+
and prepare again so its manifest binds that recipe. `depth-apply` refuses
|
|
173
|
+
missing, stale or mismatched bindings before emission.
|
|
174
|
+
|
|
175
|
+
### 4. Apply the maps as depth sheets
|
|
135
176
|
|
|
136
177
|
```sh
|
|
137
178
|
rig-parts depth-apply --parts work/rig --manifest inference/manifest.json --config depth.json --rig-config config.json --out mapped
|
|
@@ -158,7 +199,7 @@ in `work/rig` or your original config is touched. Any mismatch — a recipe edit
|
|
|
158
199
|
after prepare, a part that moved, a map of the wrong size, a part your
|
|
159
200
|
`turn.roles` does not name — is refused by name before a byte is written.
|
|
160
201
|
|
|
161
|
-
###
|
|
202
|
+
### 5. Rig, and look
|
|
162
203
|
|
|
163
204
|
```sh
|
|
164
205
|
rig-parts rig --parts mapped --config mapped/config.json --out compiled
|
|
@@ -178,7 +219,7 @@ from here as they do for any rig.
|
|
|
178
219
|
**Try it today.** The `look` example in
|
|
179
220
|
[rig-c/examples](https://github.com/rig-c/examples/tree/main/look) is a complete
|
|
180
221
|
depth-driven head and body turn you can rebuild, with no model and no GPU. It
|
|
181
|
-
takes the See-through sheets route, so steps 1 to
|
|
222
|
+
takes the See-through sheets route, so steps 1 to 4 are already done for you:
|
|
182
223
|
|
|
183
224
|
```sh
|
|
184
225
|
rig-parts assemble --source painting.png --full layers/full --head layers/head --config config.json --out assembled
|
package/docs/MIGRATION.md
CHANGED
|
@@ -9,6 +9,8 @@ from the pull request that measured it.
|
|
|
9
9
|
|
|
10
10
|
## In one paragraph
|
|
11
11
|
|
|
12
|
+
Issue #1362: consumers of check/build/compose diagnostic folders must use the [diagnostic path mapping](STABILITY.md#diagnostic-path-segments) and retained `frames.json` directories; safe ASCII names, including uppercase requirement names, keep their paths; ASCII-case alias siblings now refuse by name; unsafe part names also change seam-picture filenames and the corresponding `check.json` `picture` references; prefixed animation names and `extremes.json` animation fields are unchanged.
|
|
13
|
+
|
|
12
14
|
Install `@rig-c/parts` (the package's name after 1.5.3; *After 1.5.3* below). A
|
|
13
15
|
config that built on 0.16.0 loads and builds unchanged: every config change since is
|
|
14
16
|
a new, opt-in field inside a new mesh mode. The bytes a config without that mode
|