3D engine that AI agents drive
Accept the size growth of the physics, drive, asset and shrinkwrap messages (issue #653)
Nguyen Xuan Anbbab9f444e30
diff --git a/changes/653-rest.md b/changes/653-rest.mdnew file mode 100644index 00000000..be0a092e--- /dev/null+++ b/changes/653-rest.md@@ -0,0 +1 @@+- The same readable errors now cover physics bodies, joints and ragdolls, vehicle drives (`motion.drive`, wheels, path, speed, lights), asset recipes and operations (root, overrides, animation, inspect, checkpoints), placed assets and the shrinkwrap edit: `motion.drive.wheels[1].node: got "Nope"; expected the name of a node in the asset, such as one scene_inspect lists.` The mesh-edit parameter checks that still say `Mesh edit 2 (...)` are not converted yet (#653)diff --git a/changes/653-rest.size.md b/changes/653-rest.size.mdnew file mode 100644index 00000000..cf831cdf--- /dev/null+++ b/changes/653-rest.size.md@@ -0,0 +1,3 @@+- entry:vehicle: 592 bytes gzip of message text in the vehicle kit (wheel, path, speed and light errors now name the field, the value and an example); nothing new runs unless a drive is rejected.+- scene:agent-scene+lazy: 1.5 KB gzip of message text in the physics, drive, asset, placement and shrinkwrap validators; nothing new runs unless a recipe is rejected, and an agent fixes the input in one retry.+- goal:agent-scene: 11 bytes gzip in the core bundle (message text only); the rest of the new text sits in lazy modules.diff --git a/changes/653.md b/changes/653.mdindex 6264f806..c442c999 100644--- a/changes/653.md+++ b/changes/653.md@@ -1,2 +1 @@- Validation errors for materials, nodes, the camera, lights, fog, bake, mesh edits and motion now read `materials[2].emissiveColor: got [-1,0,0]; expected three numbers of 0 or more, such as [1, 0.5, 0.2].`: the full field path, the value received (cut at 40 characters) and a range, a list of choices or an example. Schema errors from the MCP tools add the received value too (`recipe.materials.0.color.2: Too big: expected number to be <=1 (got 2)`). Mesh edit errors keep the position of the edit (`edits[1].segments`). Not every message in the engine is converted yet; the rest keep their older wording (#653)-- The same readable errors now cover physics bodies, joints and ragdolls, vehicle drives (`motion.drive`, wheels, path, speed, lights), asset recipes and operations (root, overrides, animation, inspect, checkpoints), placed assets and the shrinkwrap edit: `motion.drive.wheels[1].node: got "Nope"; expected the name of a node in the asset, such as one scene_inspect lists.` Mesh-edit parameter checks that still say `Mesh edit 2 (...)` are not converted yet (#653)diff --git a/changes/653.size.md b/changes/653.size.mdindex 29ee69c6..1b723f76 100644--- a/changes/653.size.md+++ b/changes/653.size.md@@ -1,6 +1,3 @@- scene:agent-scene: error text grows by about 0.9 KB gzip (field path, received value and an example in each converted message, plus the 30-line field-error module); an agent that reads "emissiveColor: got [-1,0,0]; expected three numbers of 0 or more, such as [1, 0.5, 0.2]" fixes the input in one retry instead of guessing.- goal:agent-scene: 888 bytes gzip of message text only, so that agent errors name the field, the value and an example; this is the issue's goal and nothing new runs unless a recipe is rejected.- scene:agent-scene+lazy: the same message text, 1.5 KB gzip with the lazy mesh, motion and bake modules; nothing new runs unless a recipe is rejected.-- entry:vehicle: 592 bytes gzip of message text in the vehicle kit (wheel, path, speed and light errors now name the field, the value and an example); nothing new runs unless a drive is rejected.-- scene:agent-scene+lazy: another 1.5 KB gzip of message text in the physics, drive, asset, placement and shrinkwrap validators; nothing new runs unless a recipe is rejected, and an agent fixes the input in one retry.-- goal:agent-scene: 11 bytes gzip in the core bundle, the rest of the text sits in lazy modules.