aboutsummaryrefslogtreecommitdiff
path: root/docs/tomes/05-render.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/tomes/05-render.md')
-rw-r--r--docs/tomes/05-render.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/tomes/05-render.md b/docs/tomes/05-render.md
index 3fc7c84..ca812ba 100644
--- a/docs/tomes/05-render.md
+++ b/docs/tomes/05-render.md
@@ -1318,6 +1318,16 @@ is a proven orientation-angle path. Field names, angle order and matrix
handedness remain unassigned, but a backend-neutral camera pose may now retain
the raw affine transform and the exact translation triple without guessing them.
+The render contract now represents that boundary directly. `RawCameraTransform`
+preserves each selector result as sixteen original `u32` words, so diagnostic
+data is not rounded or silently assigned a row/column convention. Its only
+typed accessor reinterprets the proven X/Y/Z words `3/7/11` as IEEE-754
+floats. `RawCameraPose` retains selector `0` and selector `2` together, and
+`CameraSnapshot::raw_pose` is optional. The present Vulkan renderer continues
+to use its existing view/projection matrices: raw pose capture is intentionally
+not converted into a view matrix until the original transform/projection
+convention has evidence.
+
A fresh no-input launch of the canonical `iron_3d.exe` did create a responsive
window titled `Parkan. Железная Стратегия`. A read-only probe then requested
`PROCESS_QUERY_INFORMATION | PROCESS_VM_READ` and attempted to read the known