A mech game prototype, pushed by Gemini 4 Carbon
agent (cont.)
+0:17run_command{"CommandLine":"python3 -c '\nimport re\nwith open(\"~/context/reflect/sortie.html\") as f:\n text = f.read()\nclean = re.sub(r\"data:[^\\\"\\x27\\)]+\", \"DATA_URI_OMITTED\", text)\nfor i, line in enumerate(clean.splitlines(), 1):\n if i >= 170:\n print(f\"{i}: {line}\")\n'","WaitMsBeforeAsync":5000,"toolSummary":"Read rest of sortie.html text"}
input
{ "CommandLine": "python3 -c '\nimport re\nwith open(\"~/context/reflect/sortie.html\") as f:\n text = f.read()\nclean = re.sub(r\"data:[^\\\"\\x27\\)]+\", \"DATA_URI_OMITTED\", text)\nfor i, line in enumerate(clean.splitlines(), 1):\n if i >= 170:\n print(f\"{i}: {line}\")\n'", "WaitMsBeforeAsync": 5000, "toolSummary": "Read rest of sortie.html text" }result, 262 lines
Command exited with code 0. Command output: 170: <div class="row"><div class="lab">Easy work crowded out hard work</div><div><p>When you asked me to use up the limits, I built what code does well. One session took the tests from 70 to 427 with factions, contracts and salvage. The mech look stayed open the whole time.</p></div></div> 171: </div> 172: </div> 173: 174: <figure> 175: <img src="DATA_URI_OMITTED" alt="Left, the striker in space on 24 October, slim and heavily segmented with blue accents. Right, the common pattern at round 8 on a grey studio background, stout and mostly white with teal blocks." width="797" height="520" style="max-width:min(44rem,100%)"> 176: <figcaption>Left: the striker, 24 Oct, slim and segmented, kit look, in space. Right: common pattern round 8, 27 Oct, stout and plain, field look, on grey. I moved the shape and the viewing conditions at the same time, and you were judging both.</figcaption> 177: </figure> 178: 179: <div class="sub"> 180: <h3>Your feedback, in your words</h3> 181: <div class="four"> 182: <div><div class="tag">Responds to</div><ul> 183: <li>Distinct options: <span class="q">all four look distinct right now and I appreciate that</span></li> 184: <li>Character: <span class="q">moving in a unique direction</span></li> 185: <li>Motion: <span class="q">the thruster reel was sick</span></li> 186: <li>Playing it: <span class="q">the first test went well, actually, I liked it</span></li> 187: <li>Layers: <span class="q">more segmentation</span>, <span class="q">parts sticking out</span>, <span class="q">increase in the intricacy</span></li> 188: </ul></div> 189: <div><div class="tag">Rejects</div><ul> 190: <li><span class="q">I don't want toon robots</span></li> 191: <li><span class="q">I'm still looking at a plastic toy</span></li> 192: <li><span class="q">flat at the front</span></li> 193: <li><span class="q">armor block is out</span>, <span class="q">wedge looks weird</span></li> 194: <li><span class="q">cleaner but is blander</span></li> 195: </ul></div> 196: <div><div class="tag">Keeps asking for</div><ul> 197: <li>Feet, in four separate messages</li> 198: <li>Head and face, through the first rounds</li> 199: <li>Backs, three times</li> 200: <li>Fewer exposed parts, three times</li> 201: <li>Waist, knees, legs</li> 202: <li>The real brief: <span class="q">functional and distinctive, yet cohesive</span></li> 203: </ul></div> 204: <div><div class="tag">Hard to put into words</div><ul> 205: <li><span class="q">bland? unappealing? not sure how to explain it</span></li> 206: <li><span class="q">I can't pick from the head set</span></li> 207: <li><span class="q">I like all of the things you referenced</span></li> 208: <li><span class="q">I'm indecisive about it</span></li> 209: <li><span class="q">the same feeling as the thrust reel gives me</span></li> 210: </ul></div> 211: </div> 212: <div class="prose"> 213: <p><b>What I take from it.</b> You react precisely to what's off, down to the body part, and you rarely pick from a menu. So the useful question is "what's off?", and I should stop asking you to choose. Your words for failure are about material and presence (plastic, toy, bland). Those depend on surface, light and motion as much as outline, and I spent most of my effort on outline.</p> 214: </div> 215: </div> 216: 217: <div class="sub"> 218: <h3>Why the reel worked and the rounds didn't</h3> 219: <div class="scroll"><table class="compare"> 220: <thead><tr><th></th><th>Thruster reel</th><th>Common pattern rounds</th></tr></thead> 221: <tbody> 222: <tr><th>Medium</th><td>A shader. Code is the native tool.</td><td>Blender numbers. Code stands in for a hand.</td></tr> 223: <tr><th>Research</th><td>Games you know, before building</td><td>Proportions measured only after round 7</td></tr> 224: <tr><th>Shown as</th><td>Moving, in space, against the old version</td><td>Stills on grey</td></tr> 225: <tr><th>Scope</th><td>One effect</td><td>A whole body, rule set and three grades</td></tr> 226: <tr><th>You could answer</th><td>"How does it feel?"</td><td>"Which defects remain?"</td></tr> 227: </tbody> 228: </table></div> 229: <div class="figs"> 230: <figure><img src="DATA_URI_OMITTED" alt="A mech firing a long blue assault boost plume in space." width="720" height="450"><figcaption>The reel you called sick. That is the older striker. The new makers aren't in the game.</figcaption></figure> 231: <figure><img src="DATA_URI_OMITTED" alt="Five red and ivory knight mechs side by side: round 1 and directions A to D." width="1200" height="354"><figcaption>The knight board: round 1, then A to D. The new kit came first, and each column commits to one idea. It's the best mech result so far. All four still share limbs and stance, so they differ mostly above the waist.</figcaption></figure> 232: </div> 233: </div> 234: </section> 235: 236: <section class="part" id="research"> 237: <header><div class="tag">Part 2</div><h2>How mechs get made</h2></header> 238: <p class="note">How far to trust each point: <span class="c s">source</span> I read the page. <span class="c e">excerpt</span> I only saw a search excerpt, the site blocked me. <span class="c g">guess</span> my own reading. Japanese pages were read through machine translation.</p> 239: 240: <div class="rows"> 241: <div class="row"><h3>The design comes first</h3><div><ul> 242: <li>Yoji Shinkawa starts with <span class="q">many doodle-like, rough sketches</span>. <a href="https://blog.playstation.com/?p=207343">PlayStation Blog</a> <span class="c s">source</span></li> 243: <li>Kanetake Ebikawa, who designed the Exia and 00 Gundam, holds silhouette and character first and leaves small details for later. <a href="https://tamashiiweb.com/topics/detail/t_kokkaku_61.html?wovn=en">Tamashii Web</a> <span class="c s">source</span></li> 244: <li>Some think with their hands. Kunio Okawara presented with wooden models because it was <span class="q">quicker</span>. <a href="https://gundamunofficial.com/production/kuniookawara_walker.html">Translated interview</a> Titanfall's Ogre began as a kitbashed maquette, and <span class="q">physical restrictions guide the look of the art</span>. <a href="https://www.cgchannel.com/2014/04/qa-titanfall-lead-artist-joel-emslie/">CG Channel</a> <span class="c s">source</span></li> 245: <li>BattleTech: iPad sketch, VR blockout, SketchUp concept, then a contract 3D artist. <a href="https://forum.paradoxplaza.com/forum/threads/dev-diary-15-sharkys-machine.1292614/post-26072144">HBS diary</a> <span class="c e">excerpt</span></li> 246: <li>One solo Blender mech: about 12 concepts, one developed, blockout <span class="q">60% of the entire job</span>, 3 to 4 focused weeks. <a href="https://80.lv/articles/breakdown-futuristic-stalker-mech-made-with-blender">80 Level</a> <span class="c s">source</span></li> 247: <li>Code Geass's Lancelot siN: about a year and 15 takes, matching hand-drawn four-view sheets. Directors often didn't specify the final look, so the CG team found it by trial and error. <a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD 1</a>, <a href="https://cgworld.jp/feature/201903-codegeass3.html">3</a> <span class="c s">source</span></li> 248: </ul></div> 249: <div class="means"><b>For sortie</b>Modelling is translation of a design that already exists, and we have nothing to translate. Your difficulty naming the look is normal: professional directors have it too. Their answer is many cheap tries.</div></div> 250: 251: <div class="row"><h3>Silhouette and proportion</h3><div><ul> 252: <li>Proportion is a character choice. Ebikawa on one design: <span class="q">Hand is large, the foot is small, the body is long</span>. <a href="https://tamashiiweb.com/topics/detail/t_kokkaku_61.html?wovn=en">Tamashii Web</a> <span class="c s">source</span></li> 253: <li>Kimitoshi Yamane says Yoshikazu Yasuhiko's mecha <span class="q">win you over with their form and weight</span>. <a href="https://www.gundam-the-origin.net/en/special/interview08.html">The Origin</a> <span class="c s">source</span></li> 254: <li>Our own measures show three body plans. Line mech: crotch .53 to .57, knee .39 to .43. GN-X: crotch .63. Knightmare: crotch .50, knee .28, hands .40 to .50, hunched. docs/light-frames.md, docs/study-proportions.md <span class="c s">source</span></li> 255: </ul></div> 256: <div class="means"><b>For sortie</b>Aiming at the middle of a range gives an average machine <span class="c g">guess</span>. Pick one body plan per maker and push it.</div></div> 257: 258: <div class="row"><h3>Surface and detail density</h3><div><ul> 259: <li>Work in order: main forms, secondary forms, details. Details add function, story and scale. Going back late <span class="q">usually makes it a little bit worse</span>. <a href="https://80.lv/articles/hard-surface-modeling-tips-and-tricks">80 Level</a> <span class="c s">source</span></li> 260: <li>Yamane aims for <span class="q">an appropriate and satisfying level of density</span> and avoids <span class="q">a sort of nervous aesthetic</span>. <a href="https://www.gundam-the-origin.net/en/special/interview08.html">The Origin</a> <span class="c s">source</span></li> 261: <li>It depends on style. GQuuuuuuX's team kept adding detail and digital markings. <a href="https://www.animenewsnetwork.com/interview/2025-06-20/cgi-veteran-hiroyasu-kobayashi-breaks-down-how-he-mech-ed-the-magic-happen-in-mobile-suit-gundam-/.224743">ANN</a> The Geass team found more detail wasn't always right. <a href="https://cgworld.jp/feature/201903-codegeass3.html">CGWORLD</a> <span class="c s">source</span></li> 262: <li>Game standard for clean plates: real bevels plus weighted normals, often with no bake. One Polycount poster says it removes about 90 percent of the unwanted gradients on flat faces. <a href="https://polycount.com/discussion/comment/2577181">Polycount</a> <span class="c e">excerpt</span>, <a href="https://docs.blender.org/manual/en/5.1/modeling/modifiers/normals/weighted_normal.html">Blender manual</a> <span class="c s">source</span></li> 263: <li>Katoki's Ver.Ka kits stand apart largely through decals and warning labels. <a href="https://www.gunpla101.com/version-ka-101">Hobby guide</a> <span class="c e">excerpt</span></li> 264: </ul></div> 265: <div class="means"><b>For sortie</b>The kit uses weighted normals nowhere. Maker plates have seams off (<code>kit/makers/shell.py:107</code>) because the rule said detail comes from decals, and the makers have no decals, only a service band and stencil blocks. Bare plates are my top suspect for "plastic" and "bland" <span class="c g">guess</span>. This is the cheapest thing to test.</div></div> 266: 267: <div class="row"><h3>Joints and armour</h3><div><ul> 268: <li>Harness moves on overlapping lames with leather straps and sliding rivets, and mail covers the gaps. <a href="https://www.medievalcollectibles.com/glossary/terminology/armor-terminology/">Glossary</a>, Met catalogue notes <span class="c e">excerpt</span></li> 269: <li>One armourer notes that many visible rivets connect to nothing. <a href="https://www.ageofarmour.com/education/gorget.php">Age of Armour</a> <span class="c e">excerpt</span></li> 270: <li>The Geass rig was kept simple on purpose, and the hand rig was the hardest, since a robot hand can't close like a fist. <a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD</a> <span class="c s">source</span></li> 271: <li>Designs change once things move. Shinkawa revised details after seeing in-game movement, and Titanfall's designs were changed for the animators. <a href="https://blog.playstation.com/?p=207343">PlayStation Blog</a>, <a href="https://www.cgchannel.com/2014/04/qa-titanfall-lead-artist-joel-emslie/">CG Channel</a> <span class="c s">source</span></li> 272: <li>Gunpla kits let plates slide and rotate with the joint so a pose still looks closed. I found no good source today. <span class="c g">guess</span></li> 273: </ul></div> 274: <div class="means"><b>For sortie</b>I can't find a range-of-motion sheet in any round. Add reach, crouch and boost poses before any detail. That would catch the shoulder bar problem early, and a mechanism only has to look believable.</div></div> 275: 276: <div class="row"><h3>Scale</h3><div><ul> 277: <li>Pacific Rim: <span class="q">to communicate huge scale, you want to move things slowly</span>, with <span class="q">little hits, and hard stops with mechanical recoil</span> in the small parts. <a href="https://artofvfx.com/?p=4715">Art of VFX</a> <span class="c s">source</span></li> 278: <li>An action figure beside the maquette made the Ogre read as 20 feet tall. <a href="https://www.cgchannel.com/2014/04/qa-titanfall-lead-artist-joel-emslie/">CG Channel</a> <span class="c s">source</span></li> 279: <li>The Origin sized ships with human models: <span class="q">If the window is this big, then how many meters high is the bridge?</span> <a href="https://www.gundam-the-origin.net/en/special/interview09.html">The Origin</a> <span class="c s">source</span></li> 280: </ul></div> 281: <div class="means"><b>For sortie</b>We already have pilots, a hangar and a catapult. Put a pilot in every hero shot, add hatches and rungs at human size, and let small parts snap while big masses drift.</div></div> 282: 283: <div class="row"><h3>Anime and real time</h3><div><ul> 284: <li>Lancelot siN: flat fills, line weight painted in large textures, limbs stretched to fit each layout. Some other cuts had about 10 staff retouching frames in Photoshop. <a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD 1</a>, <a href="https://cgworld.jp/feature/201903-codegeass3.html">3</a> <span class="c s">source</span></li> 285: <li>A game can't cheat per shot, so the model must hold from every angle. Our chase camera mostly sees the back. <span class="c g">guess</span></li> 286: </ul></div> 287: <div class="means"><b>For sortie</b>Anime references flatter a front three-quarter drawing. Judge from the chase camera first. That may be why backs keep coming up.</div></div> 288: </div> 289: 290: <div class="sub"> 291: <h3>Your four influences</h3> 292: <div class="scroll"><table class="compare"> 293: <thead><tr><th></th><th>What I could source</th><th>My reading <span class="c g">guess</span></th></tr></thead> 294: <tbody> 295: <tr><th>Gundam 00</th><td>Designs by Takayuki Yanase, Ebikawa and others (<a href="https://mechabay.com/gundam-00">Mechabay</a>). Our measure: waist a tenth of height, legs near 60 percent, limbs of three or four overlapping plates over a dark inner frame. No designer interview found on why.</td><td>Long straight lines, sharp wedges and thin plates. The frame does show here, as a dark slim core. Ours reads as grey scaffolding.</td></tr> 296: <tr><th>Code Geass</th><td>On the Re;surrection film: Akira Yasuda's original designs, Eiji Nakata's main frames, Kenji Teraoka's cockpits (<a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD</a>). Our measure in docs/light-frames.md.</td><td>The character is in the stance: a hunch, long arms, skating on wheels. Our sheets stand upright, which removes it.</td></tr> 297: <tr><th>Front Mission</th><td>Modular: body, two arms, legs (<a href="https://www.mobygames.com/game/13788/front-mission/?s=date">MobyGames</a>). Shinkawa drew one new wanzer for Left Alive. No credits for the classic wanzers found.</td><td>Military vehicles first. Mismatched parts must still look right, so it's the best model for your parts system.</td></tr> 298: <tr><th>Lancer</th><td>A baseline maker plus four big makers (<a href="https://lancer.wiki.gg/wiki/The_Big_Four">wiki</a>). No source on its art rules.</td><td>Useful for maker structure, as docs/lore.md already says. It teaches little about 3D form.</td></tr> 299: </tbody> 300: </table></div> 301: </div> 302: 303: <div class="two"> 304: <div class="sub"> 305: <h3>Where code-built falls down</h3> 306: <ul> 307: <li><b>Differences you can't see.</b> Kate Compton's "ten thousand bowls of oatmeal": unique on paper, the same to the eye. <a href="https://gamedeveloper.com/design/practical-procedural-generation-for-everyone-">Game Developer</a> <span class="c s">source</span> Our heavies carry up to 73 plates, and Codex still says medium and heavy look alike at 2 km on two of the four lines.</li> 308: <li><b>Seeing.</b> Vision models struggle with Blender tasks that are <span class="q">relatively easy for human Blender users</span>. <a href="https://arxiv.org/abs/2504.01786v1">BlenderGym</a> <span class="c e">excerpt</span> A similar system's stated limit is missing subtle spatial artifacts. <a href="https://api.emergentmind.com/papers/2508.08228">LL3M</a> <span class="c e">excerpt</span></li> 309: <li><b>The vocabulary shows through.</b> Two-view shells look like slabs, lofts look like tubes. Each kit has a look. <span class="c g">guess, from our rounds</span></li> 310: <li><b>No hand.</b> An artist pushes a form until it's right. I change a number and wait minutes.</li> 311: <li><b>Thin geometry breaks.</b> Coplanar slivers on the light shins, a pinhole on the knee wings.</li> 312: </ul> 313: </div> 314: <div class="sub"> 315: <h3>Where it wins, so keep it</h3> 316: <ul> 317: <li>The joint contract, mount pads, material roles and livery swaps.</li> 318: <li>Rebuilding every model after one frame change, with byte-identical proof.</li> 319: <li>Effects and shaders, as the reel showed.</li> 320: <li>Variation you then curate. Compton kept the Spore planet seeds that looked good and threw out the rest: <span class="q">You don't need to 'do it right', just do what works.</span> <a href="https://gamedeveloper.com/design/practical-procedural-generation-for-everyone-">Game Developer</a> <span class="c s">source</span></li> 321: </ul> 322: </div> 323: </div> 324: </section> 325: 326: <section class="part" id="tools"> 327: <header><div class="tag">Part 3</div><h2>Tools</h2></header> 328: <div class="prose"><p><b>You need to buy nothing.</b> The first four rows need no install and are what I'd use. The well-known Blender hard-surface add-ons I could check are built for a person with a mouse, so they barely help a scripted pipeline.</p></div> 329: <div class="scroll"><table class="tools"> 330: <thead><tr><th>Cost</th><th>Tool</th><th>What it does</th><th>Fit here</th><th>Licence, signs of life</th><th>Verdict</th></tr></thead> 331: <tbody> 332: <tr class="band"><td colspan="6">Free, already here</td></tr> 333: <tr><td class="cost">$0</td><th><a href="https://docs.blender.org/manual/en/5.1/modeling/modifiers/normals/weighted_normal.html">Weighted Normal modifier</a> with Bevel</th><td>Keeps flat faces flat and puts the highlight on the bevel</td><td>Scriptable headless. Unused in the kit today.</td><td>GPL, in Blender. Manual current at 5.x.</td><td class="v-try">Try first</td></tr> 334: <tr><td class="cost">$0</td><th><code>lib.subd</code> with creases</th><td>Domes and swelling plates with crisp edges</td><td>Ours, already built. Your approved heads came from this line of work.</td><td>In the repo</td><td class="v-try">Default for hero plates</td></tr> 335: <tr><td class="cost">$0</td><th><a href="https://docs.blender.org/manual/en/latest/modeling/geometry_nodes/volume/index.html">SDF grid nodes</a></th><td>Mesh to SDF, boolean, offset and fillet, then back to mesh: forms that blend into each other</td><td>Listed for 5.2 LTS, we run 5.2.3. Graph built from Python. Thin plates may need fine grids <span class="c g">guess</span>.</td><td>GPL, in Blender. I read the node list only.</td><td class="v-try">One-day test on a shoulder</td></tr> 336: <tr><td class="cost">$0</td><th>SVG silhouette sheets</th><td>Dozens of rough outlines in minutes</td><td>No install. The kit already takes 2D outlines.</td><td>Ours to write</td><td class="v-try">Use for the sketch step</td></tr> 337: <tr class="band"><td colspan="6">Free, to install</td></tr> 338: <tr><td class="cost">$0</td><th><a href="https://github.com/gumyr/build123d">build123d</a></th><td>Python CAD with true fillets and chamfers</td><td>Scriptable, but outside Blender. The page lists STL and STEP export. Complex fillets may fail <span class="c g">guess</span>.</td><td>Apache 2.0. 3.6k stars, 3,454 commits.</td><td>Only if bevels fall short</td></tr> 339: <tr><td class="cost">$0</td><th><a href="https://github.com/ahujasid/blender-mcp">BlenderMCP</a></th><td>Lets an agent drive a live Blender and see viewport shots</td><td>Could shorten the loop. Adds a live session, and telemetry to switch off.</td><td>MIT. About 12k stars per one listing.</td><td class="v-no">Skip for now</td></tr> 340: <tr><td class="cost">$0</td><th><a href="https://extensions.blender.org/add-ons/hardflow/">Hardflow</a></th><td>Draw-to-cut booleans, snapping, decals, kitbash</td><td>Mouse-driven. No scripting described.</td><td>GPLv3+. 1.22.0, Oct 2026 note, 7,504 downloads.</td><td class="v-no">Only if you want to model by hand</td></tr> 341: <tr><td class="cost">$0</td><th><a href="https://www.renderjuice.com/blender/extensions/bool-tool">Bool Tool</a></th><td>Boolean shortcuts</td><td>The kit already calls booleans.</td><td>GPL. About 1M downloads.</td><td class="v-no">Skip</td></tr> 342: <tr><td class="cost">$0</td><th><a href="https://github.com/hlorus/CAD_Sketcher">CAD Sketcher</a></th><td>Constraint-based 2D sketches</td><td>Interactive. Calls itself experimental.</td><td>GPL-3.0. Needs Blender 5.0+.</td><td class="v-no">Skip</td></tr> 343: <tr><td class="cost">$0</td><th><a href="https://github.com/microsoft/TRELLIS.2">TRELLIS.2</a></th><td>One image to a textured 3D mesh</td><td>Needs an NVIDIA GPU with 24 GB, and C1 has a Radeon. A fused mesh won't ride our joints <span class="c g">guess</span>.</td><td>MIT.</td><td class="v-no">Can't run here</td></tr> 344: <tr><td class="cost">$0 if it runs</td><th>Local image model on C1</th><td>Rough concept sheets for you to react to, private, nothing ships</td><td>Untested on C1, and the GPU is shared. I didn't research models today.</td><td>Depends on the model</td><td>Your call, question 5 below</td></tr> 345: <tr class="band"><td colspan="6">Paid, none recommended</td></tr> 346: <tr><td class="cost">$38</td><th><a href="https://superhivemarket.com/products/hard-ops--boxcutter-ultimate-bundle">Hard Ops / Boxcutter</a></th><td>The standard hard-surface toolset</td><td>Menus, pies and clicks. No scripting mentioned.</td><td>GPL. Blender 3.5 to 5.2.</td><td class="v-no">Only for a human modeller</td></tr> 347: <tr><td class="cost">$44.99</td><th><a href="https://superhivemarket.com/products/meshmachine">MESHmachine</a></th><td>Chamfer and fillet tools, normal detail plugs</td><td>Page doesn't say how it's driven.</td><td>GPL. Blender 4.2 to 5.2.</td><td class="v-no">No</td></tr> 348: <tr><td class="cost">From $54.99</td><th><a href="https://superhivemarket.com/products/decalmachine">DECALmachine</a></th><td>Mesh decals in Blender</td><td>The game already places decals at runtime.</td><td>GPL. Blender 4.3 to 5.1.</td><td class="v-no">No</td></tr> 349: <tr><td class="cost">$20 to about $70</td><th><a href="https://blendermarket.com/products/fluent/ratings?page=5">Fluent</a></th><td>Interactive boolean modelling</td><td>Same problem as Hard Ops <span class="c g">guess</span>. Listings conflict on price.</td><td>Not checked</td><td class="v-no">No</td></tr> 350: <tr><td class="cost">$29, or $69 commercial</td><th><a href="https://superhivemarket.com/products/robot-designer">Robot Designer</a></th><td>Geometry Nodes robot generator, 800+ sliders, 25 presets</td><td>Someone else's look, with a real oatmeal risk.</td><td>Terms mix GPL with resale limits. Published about 7 months ago, Blender 4.5 to 5.2.</td><td class="v-no">No</td></tr> 351: <tr><td class="cost">Not priced</td><th>A concept artist</th><td>One real four-view sheet to model against</td><td>It's the step every source has and we lack.</td><td></td><td>Only if the free week fails, and only on your go</td></tr> 352: </tbody> 353: </table></div> 354: </section> 355: 356: <section class="part" id="forward"> 357: <header><div class="tag">Part 4</div><h2>When you start this again</h2></header> 358: 359: <div class="two"> 360: <div class="sub"> 361: <h3>What changes</h3> 362: <ul> 363: <li><b>Design and building become separate steps.</b> Rough and many first, then model one.</li> 364: <li><b>One hero at a time, judged moving.</b> Clips are the review. Stills are for diagnosis.</li> 365: <li><b>You veto, you don't choose.</b> I bring variety and ask "what's off?"</li> 366: <li><b>Surface gets equal time with outline.</b> Weighted normals, sculpted plates, designed seams, real decals, one settled look.</li> 367: <li><b>Rules come last.</b> <code>docs/visual-language.md</code> goes back to draft until something lands.</li> 368: <li><b>The critic changes job.</b> I ask Codex "what's the one idea here, and what feels cheap?" It never decides done. Your friends see clips too, since they gave useful reads early on.</li> 369: </ul> 370: </div> 371: <div class="sub"> 372: <h3>What I'd ask you, one at a time</h3> 373: <ol> 374: <li>Think of a moment in any game or show when a mech made you feel "that's it". What was it doing?</li> 375: <li>In your ideal first hour of sortie, where's your mech on screen when it matters most?</li> 376: <li>You've asked about the inner frame three times. Do you want to see it at all, and where?</li> 377: <li>Is Gundam 00 still the target for the plain line mech, or did the knight board move that?</li> 378: <li>Are rough private AI sketches fine for this, and do you already have an image tool you like?</li> 379: </ol> 380: <p class="note">No boards or menus during this. I'd play your answers back in your words and keep one short settled / open note. The clean-or-worn question gets answered by the reel, so I wouldn't ask it.</p> 381: </div> 382: </div> 383: 384: <div class="sub"> 385: <h3>The first week</h3> 386: <div class="scroll"><table class="week"> 387: <thead><tr><th>Day</th><th>What happens</th><th>Your part</th><th>Done when</th></tr></thead> 388: <tbody> 389: <tr><th>1. Interview</th><td>The questions above. No building.</td><td>About 30 minutes</td><td>A short settled / open note</td></tr> 390: <tr><th>2. Reel</th><td>No modelling. A 10-second clip of each existing mech (striker, pattern, all four knight lines): turn, boost, stop, plus one shot next to a pilot. Same clip in clean and worn looks. Makers need a small hook-up to the thruster bench.</td><td>Watch, say what's off, send it to friends if you like</td><td>The look is settled, and we know which mech already has some pull</td></tr> 391: <tr><th>3. Sketches</th><td>30 or so rough silhouettes in SVG, pushed hard, none averaged from references. Rough AI sheets too if you said yes.</td><td>Cross out what's dead</td><td>Three survivors, no scoring</td></tr> 392: <tr><th>4. Surface test</th><td>One chest and shoulder from a survivor, built with weighted normals, sculpted plates, the SDF fillet, drawn seams and decals. Shown at the chase camera and close up, moving.</td><td>Say which looks expensive and which looks plastic</td><td>One method chosen, the rest dropped</td></tr> 393: <tr><th>5. Hero</th><td>One mech at one grade, with a reach, crouch and boost check before detail. Shown only as a reel.</td><td>React as you did to the thrusters</td><td>You say "that's done" about some of it, or name what's off</td></tr> 394: </tbody> 395: </table></div> 396: <p class="note">You've since chosen to start over with one mech from scratch, so the plan at the top replaces this week. The test for the week was one part of one mech reaching the thruster reel's feeling. Grades, other makers and rules wait until then. The open shared shoulder bar question waits on your answer to question 3.</p> 397: </div> 398: 399: <div class="two"> 400: <div class="sub"> 401: <h3>What I'd stop doing</h3> 402: <ul> 403: <li>Numbered polish rounds on one model</li> 404: <li>Building twelve models before one is loved</li> 405: <li>Turning one comment into a rule for every maker</li> 406: <li>Putting ratios and plate counts in your reports</li> 407: <li>Grey sheets of small tiles as the verdict</li> 408: <li>Asking you to pick, or carrying a rolling list of naming decisions in every report</li> 409: <li>Filling spare usage with systems while the look is open</li> 410: <li>Long terminal reports: one page, clip first, one question at the end</li> 411: </ul> 412: </div> 413: <div class="sub"> 414: <h3>Risks I can't remove</h3> 415: <ul> 416: <li><b>Code-built may cap out.</b> My guess is that it holds at the chase camera and falls short in hangar close-ups. If the week's hero doesn't land, I'll say so plainly. The next step would cost money: one commissioned four-view sheet, not priced, on your go only.</li> 417: <li><b>Sketches can promise more than the kit can build.</b> So day 4 comes before day 5, and only proven methods go on the hero.</li> 418: <li><b>I can't watch video.</b> I judge frames. You and your friends are the only judges of motion.</li> 419: </ul> 420: </div> 421: </div> 422: 423: <p class="note"><b>What I couldn't read.</b> Paradox forum (HBS diaries), Polycount, the Met and Age of Armour blocked direct fetches, so those are search excerpts. Kate Compton's original zine returned 403, so I used Game Developer's summary. CGWORLD and Tamashii Web were machine translated. I found no designer's own account of Gundam 00's shape choices, no source on Armored Core 6's or Lancer's art rules, and nothing usable on Gunpla inner frames. Prices are from listing pages today and can change.</p> 424: </section> 425: 426: </div> 427: </body> 428: </html>
read_file{"EndLine":375,"Path":"~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/.system_generated/steps/9/output.txt","StartLine":70}
input
{ "EndLine": 375, "Path": "~/.gemini/antigravity-cli/brain/cea9ec26-a0ce-4401-a5d2-36df51bb07b3/.system_generated/steps/9/output.txt", "StartLine": 70 }result, 196 lines
Showing lines 70-264 of 264 70: 234: </section> 71: 235: 72: 236: <section class="part" id="research"> 73: 237: <header><div class="tag">Part 2</div><h2>How mechs get made</h2></header> 74: 238: <p class="note">How far to trust each point: <span class="c s">source</span> I read the page. <span class="c e">excerpt</span> I only saw a search excerpt, the site blocked me. <span class="c g">guess</span> my own reading. Japanese pages were read through machine translation.</p> 75: 239: 76: 240: <div class="rows"> 77: 241: <div class="row"><h3>The design comes first</h3><div><ul> 78: 242: <li>Yoji Shinkawa starts with <span class="q">many doodle-like, rough sketches</span>. <a href="https://blog.playstation.com/?p=207343">PlayStation Blog</a> <span class="c s">source</span></li> 79: 243: <li>Kanetake Ebikawa, who designed the Exia and 00 Gundam, holds silhouette and character first and leaves small details for later. <a href="https://tamashiiweb.com/topics/detail/t_kokkaku_61.html?wovn=en">Tamashii Web</a> <span class="c s">source</span></li> 80: 244: <li>Some think with their hands. Kunio Okawara presented with wooden models because it was <span class="q">quicker</span>. <a href="https://gundamunofficial.com/production/kuniookawara_walker.html">Translated interview</a> Titanfall's Ogre began as a kitbashed maquette, and <span class="q">physical restrictions guide the look of the art</span>. <a href="https://www.cgchannel.com/2014/04/qa-titanfall-lead-artist-joel-emslie/">CG Channel</a> <span class="c s">source</span></li> 81: 245: <li>BattleTech: iPad sketch, VR blockout, SketchUp concept, then a contract 3D artist. <a href="https://forum.paradoxplaza.com/forum/threads/dev-diary-15-sharkys-machine.1292614/post-26072144">HBS diary</a> <span class="c e">excerpt</span></li> 82: 246: <li>One solo Blender mech: about 12 concepts, one developed, blockout <span class="q">60% of the entire job</span>, 3 to 4 focused weeks. <a href="https://80.lv/articles/breakdown-futuristic-stalker-mech-made-with-blender">80 Level</a> <span class="c s">source</span></li> 83: 247: <li>Code Geass's Lancelot siN: about a year and 15 takes, matching hand-drawn four-view sheets. Directors often didn't specify the final look, so the CG team found it by trial and error. <a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD 1</a>, <a href="https://cgworld.jp/feature/201903-codegeass3.html">3</a> <span class="c s">source</span></li> 84: 248: </ul></div> 85: 249: <div class="means"><b>For sortie</b>Modelling is translation of a design that already exists, and we have nothing to translate. Your difficulty naming the look is normal: professional directors have it too. Their answer is many cheap tries.</div></div> 86: 250: 87: 251: <div class="row"><h3>Silhouette and proportion</h3><div><ul> 88: 252: <li>Proportion is a character choice. Ebikawa on one design: <span class="q">Hand is large, the foot is small, the body is long</span>. <a href="https://tamashiiweb.com/topics/detail/t_kokkaku_61.html?wovn=en">Tamashii Web</a> <span class="c s">source</span></li> 89: 253: <li>Kimitoshi Yamane says Yoshikazu Yasuhiko's mecha <span class="q">win you over with their form and weight</span>. <a href="https://www.gundam-the-origin.net/en/special/interview08.html">The Origin</a> <span class="c s">source</span></li> 90: 254: <li>Our own measures show three body plans. Line mech: crotch .53 to .57, knee .39 to .43. GN-X: crotch .63. Knightmare: crotch .50, knee .28, hands .40 to .50, hunched. docs/light-frames.md, docs/study-proportions.md <span class="c s">source</span></li> 91: 255: </ul></div> 92: 256: <div class="means"><b>For sortie</b>Aiming at the middle of a range gives an average machine <span class="c g">guess</span>. Pick one body plan per maker and push it.</div></div> 93: 257: 94: 258: <div class="row"><h3>Surface and detail density</h3><div><ul> 95: 259: <li>Work in order: main forms, secondary forms, details. Details add function, story and scale. Going back late <span class="q">usually makes it a little bit worse</span>. <a href="https://80.lv/articles/hard-surface-modeling-tips-and-tricks">80 Level</a> <span class="c s">source</span></li> 96: 260: <li>Yamane aims for <span class="q">an appropriate and satisfying level of density</span> and avoids <span class="q">a sort of nervous aesthetic</span>. <a href="https://www.gundam-the-origin.net/en/special/interview08.html">The Origin</a> <span class="c s">source</span></li> 97: 261: <li>It depends on style. GQuuuuuuX's team kept adding detail and digital markings. <a href="https://www.animenewsnetwork.com/interview/2025-06-20/cgi-veteran-hiroyasu-kobayashi-breaks-down-how-he-mech-ed-the-magic-happen-in-mobile-suit-gundam-/.224743">ANN</a> The Geass team found more detail wasn't always right. <a href="https://cgworld.jp/feature/201903-codegeass3.html">CGWORLD</a> <span class="c s">source</span></li> 98: 262: <li>Game standard for clean plates: real bevels plus weighted normals, often with no bake. One Polycount poster says it removes about 90 percent of the unwanted gradients on flat faces. <a href="https://polycount.com/discussion/comment/2577181">Polycount</a> <span class="c e">excerpt</span>, <a href="https://docs.blender.org/manual/en/5.1/modeling/modifiers/normals/weighted_normal.html">Blender manual</a> <span class="c s">source</span></li> 99: 263: <li>Katoki's Ver.Ka kits stand apart largely through decals and warning labels. <a href="https://www.gunpla101.com/version-ka-101">Hobby guide</a> <span class="c e">excerpt</span></li> 100: 264: </ul></div> 101: 265: <div class="means"><b>For sortie</b>The kit uses weighted normals nowhere. Maker plates have seams off (<code>kit/makers/shell.py:107</code>) because the rule said detail comes from decals, and the makers have no decals, only a service band and stencil blocks. Bare plates are my top suspect for "plastic" and "bland" <span class="c g">guess</span>. This is the cheapest thing to test.</div></div> 102: 266: 103: 267: <div class="row"><h3>Joints and armour</h3><div><ul> 104: 268: <li>Harness moves on overlapping lames with leather straps and sliding rivets, and mail covers the gaps. <a href="https://www.medievalcollectibles.com/glossary/terminology/armor-terminology/">Glossary</a>, Met catalogue notes <span class="c e">excerpt</span></li> 105: 269: <li>One armourer notes that many visible rivets connect to nothing. <a href="https://www.ageofarmour.com/education/gorget.php">Age of Armour</a> <span class="c e">excerpt</span></li> 106: 270: <li>The Geass rig was kept simple on purpose, and the hand rig was the hardest, since a robot hand can't close like a fist. <a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD</a> <span class="c s">source</span></li> 107: 271: <li>Designs change once things move. Shinkawa revised details after seeing in-game movement, and Titanfall's designs were changed for the animators. <a href="https://blog.playstation.com/?p=207343">PlayStation Blog</a>, <a href="https://www.cgchannel.com/2014/04/qa-titanfall-lead-artist-joel-emslie/">CG Channel</a> <span class="c s">source</span></li> 108: 272: <li>Gunpla kits let plates slide and rotate with the joint so a pose still looks closed. I found no good source today. <span class="c g">guess</span></li> 109: 273: </ul></div> 110: 274: <div class="means"><b>For sortie</b>I can't find a range-of-motion sheet in any round. Add reach, crouch and boost poses before any detail. That would catch the shoulder bar problem early, and a mechanism only has to look believable.</div></div> 111: 275: 112: 276: <div class="row"><h3>Scale</h3><div><ul> 113: 277: <li>Pacific Rim: <span class="q">to communicate huge scale, you want to move things slowly</span>, with <span class="q">little hits, and hard stops with mechanical recoil</span> in the small parts. <a href="https://artofvfx.com/?p=4715">Art of VFX</a> <span class="c s">source</span></li> 114: 278: <li>An action figure beside the maquette made the Ogre read as 20 feet tall. <a href="https://www.cgchannel.com/2014/04/qa-titanfall-lead-artist-joel-emslie/">CG Channel</a> <span class="c s">source</span></li> 115: 279: <li>The Origin sized ships with human models: <span class="q">If the window is this big, then how many meters high is the bridge?</span> <a href="https://www.gundam-the-origin.net/en/special/interview09.html">The Origin</a> <span class="c s">source</span></li> 116: 280: </ul></div> 117: 281: <div class="means"><b>For sortie</b>We already have pilots, a hangar and a catapult. Put a pilot in every hero shot, add hatches and rungs at human size, and let small parts snap while big masses drift.</div></div> 118: 282: 119: 283: <div class="row"><h3>Anime and real time</h3><div><ul> 120: 284: <li>Lancelot siN: flat fills, line weight painted in large textures, limbs stretched to fit each layout. Some other cuts had about 10 staff retouching frames in Photoshop. <a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD 1</a>, <a href="https://cgworld.jp/feature/201903-codegeass3.html">3</a> <span class="c s">source</span></li> 121: 285: <li>A game can't cheat per shot, so the model must hold from every angle. Our chase camera mostly sees the back. <span class="c g">guess</span></li> 122: 286: </ul></div> 123: 287: <div class="means"><b>For sortie</b>Anime references flatter a front three-quarter drawing. Judge from the chase camera first. That may be why backs keep coming up.</div></div> 124: 288: </div> 125: 289: 126: 290: <div class="sub"> 127: 291: <h3>Your four influences</h3> 128: 292: <div class="scroll"><table class="compare"> 129: 293: <thead><tr><th></th><th>What I could source</th><th>My reading <span class="c g">guess</span></th></tr></thead> 130: 294: <tbody> 131: 295: <tr><th>Gundam 00</th><td>Designs by Takayuki Yanase, Ebikawa and others (<a href="https://mechabay.com/gundam-00">Mechabay</a>). Our measure: waist a tenth of height, legs near 60 percent, limbs of three or four overlapping plates over a dark inner frame. No designer interview found on why.</td><td>Long straight lines, sharp wedges and thin plates. The frame does show here, as a dark slim core. Ours reads as grey scaffolding.</td></tr> 132: 296: <tr><th>Code Geass</th><td>On the Re;surrection film: Akira Yasuda's original designs, Eiji Nakata's main frames, Kenji Teraoka's cockpits (<a href="https://cgworld.jp/feature/201903-codegeass1.html">CGWORLD</a>). Our measure in docs/light-frames.md.</td><td>The character is in the stance: a hunch, long arms, skating on wheels. Our sheets stand upright, which removes it.</td></tr> 133: 297: <tr><th>Front Mission</th><td>Modular: body, two arms, legs (<a href="https://www.mobygames.com/game/13788/front-mission/?s=date">MobyGames</a>). Shinkawa drew one new wanzer for Left Alive. No credits for the classic wanzers found.</td><td>Military vehicles first. Mismatched parts must still look right, so it's the best model for your parts system.</td></tr> 134: 298: <tr><th>Lancer</th><td>A baseline maker plus four big makers (<a href="https://lancer.wiki.gg/wiki/The_Big_Four">wiki</a>). No source on its art rules.</td><td>Useful for maker structure, as docs/lore.md already says. It teaches little about 3D form.</td></tr> 135: 299: </tbody> 136: 300: </table></div> 137: 301: </div> 138: 302: 139: 303: <div class="two"> 140: 304: <div class="sub"> 141: 305: <h3>Where code-built falls down</h3> 142: 306: <ul> 143: 307: <li><b>Differences you can't see.</b> Kate Compton's "ten thousand bowls of oatmeal": unique on paper, the same to the eye. <a href="https://gamedeveloper.com/design/practical-procedural-generation-for-everyone-">Game Developer</a> <span class="c s">source</span> Our heavies carry up to 73 plates, and Codex still says medium and heavy look alike at 2 km on two of the four lines.</li> 144: 308: <li><b>Seeing.</b> Vision models struggle with Blender tasks that are <span class="q">relatively easy for human Blender users</span>. <a href="https://arxiv.org/abs/2504.01786v1">BlenderGym</a> <span class="c e">excerpt</span> A similar system's stated limit is missing subtle spatial artifacts. <a href="https://api.emergentmind.com/papers/2508.08228">LL3M</a> <span class="c e">excerpt</span></li> 145: 309: <li><b>The vocabulary shows through.</b> Two-view shells look like slabs, lofts look like tubes. Each kit has a look. <span class="c g">guess, from our rounds</span></li> 146: 310: <li><b>No hand.</b> An artist pushes a form until it's right. I change a number and wait minutes.</li> 147: 311: <li><b>Thin geometry breaks.</b> Coplanar slivers on the light shins, a pinhole on the knee wings.</li> 148: 312: </ul> 149: 313: </div> 150: 314: <div class="sub"> 151: 315: <h3>Where it wins, so keep it</h3> 152: 316: <ul> 153: 317: <li>The joint contract, mount pads, material roles and livery swaps.</li> 154: 318: <li>Rebuilding every model after one frame change, with byte-identical proof.</li> 155: 319: <li>Effects and shaders, as the reel showed.</li> 156: 320: <li>Variation you then curate. Compton kept the Spore planet seeds that looked good and threw out the rest: <span class="q">You don't need to 'do it right', just do what works.</span> <a href="https://gamedeveloper.com/design/practical-procedural-generation-for-everyone-">Game Developer</a> <span class="c s">source</span></li> 157: 321: </ul> 158: 322: </div> 159: 323: </div> 160: 324: </section> 161: 325: 162: 326: <section class="part" id="tools"> 163: 327: <header><div class="tag">Part 3</div><h2>Tools</h2></header> 164: 328: <div class="prose"><p><b>You need to buy nothing.</b> The first four rows need no install and are what I'd use. The well-known Blender hard-surface add-ons I could check are built for a person with a mouse, so they barely help a scripted pipeline.</p></div> 165: 329: <div class="scroll"><table class="tools"> 166: 330: <thead><tr><th>Cost</th><th>Tool</th><th>What it does</th><th>Fit here</th><th>Licence, signs of life</th><th>Verdict</th></tr></thead> 167: 331: <tbody> 168: 332: <tr class="band"><td colspan="6">Free, already here</td></tr> 169: 333: <tr><td class="cost">$0</td><th><a href="https://docs.blender.org/manual/en/5.1/modeling/modifiers/normals/weighted_normal.html">Weighted Normal modifier</a> with Bevel</th><td>Keeps flat faces flat and puts the highlight on the bevel</td><td>Scriptable headless. Unused in the kit today.</td><td>GPL, in Blender. Manual current at 5.x.</td><td class="v-try">Try first</td></tr> 170: 334: <tr><td class="cost">$0</td><th><code>lib.subd</code> with creases</th><td>Domes and swelling plates with crisp edges</td><td>Ours, already built. Your approved heads came from this line of work.</td><td>In the repo</td><td class="v-try">Default for hero plates</td></tr> 171: 335: <tr><td class="cost">$0</td><th><a href="https://docs.blender.org/manual/en/latest/modeling/geometry_nodes/volume/index.html">SDF grid nodes</a></th><td>Mesh to SDF, boolean, offset and fillet, then back to mesh: forms that blend into each other</td><td>Listed for 5.2 LTS, we run 5.2.3. Graph built from Python. Thin plates may need fine grids <span class="c g">guess</span>.</td><td>GPL, in Blender. I read the node list only.</td><td class="v-try">One-day test on a shoulder</td></tr> 172: 336: <tr><td class="cost">$0</td><th>SVG silhouette sheets</th><td>Dozens of rough outlines in minutes</td><td>No install. The kit already takes 2D outlines.</td><td>Ours to write</td><td class="v-try">Use for the sketch step</td></tr> 173: 337: <tr class="band"><td colspan="6">Free, to install</td></tr> 174: 338: <tr><td class="cost">$0</td><th><a href="https://github.com/gumyr/build123d">build123d</a></th><td>Python CAD with true fillets and chamfers</td><td>Scriptable, but outside Blender. The page lists STL and STEP export. Complex fillets may fail <span class="c g">guess</span>.</td><td>Apache 2.0. 3.6k stars, 3,454 commits.</td><td>Only if bevels fall short</td></tr> 175: 339: <tr><td class="cost">$0</td><th><a href="https://github.com/ahujasid/blender-mcp">BlenderMCP</a></th><td>Lets an agent drive a live Blender and see viewport shots</td><td>Could shorten the loop. Adds a live session, and telemetry to switch off.</td><td>MIT. About 12k stars per one listing.</td><td class="v-no">Skip for now</td></tr> 176: 340: <tr><td class="cost">$0</td><th><a href="https://extensions.blender.org/add-ons/hardflow/">Hardflow</a></th><td>Draw-to-cut booleans, snapping, decals, kitbash</td><td>Mouse-driven. No scripting described.</td><td>GPLv3+. 1.22.0, Oct 2026 note, 7,504 downloads.</td><td class="v-no">Only if you want to model by hand</td></tr> 177: 341: <tr><td class="cost">$0</td><th><a href="https://www.renderjuice.com/blender/extensions/bool-tool">Bool Tool</a></th><td>Boolean shortcuts</td><td>The kit already calls booleans.</td><td>GPL. About 1M downloads.</td><td class="v-no">Skip</td></tr> 178: 342: <tr><td class="cost">$0</td><th><a href="https://github.com/hlorus/CAD_Sketcher">CAD Sketcher</a></th><td>Constraint-based 2D sketches</td><td>Interactive. Calls itself experimental.</td><td>GPL-3.0. Needs Blender 5.0+.</td><td class="v-no">Skip</td></tr> 179: 343: <tr><td class="cost">$0</td><th><a href="https://github.com/microsoft/TRELLIS.2">TRELLIS.2</a></th><td>One image to a textured 3D mesh</td><td>Needs an NVIDIA GPU with 24 GB, and C1 has a Radeon. A fused mesh won't ride our joints <span class="c g">guess</span>.</td><td>MIT.</td><td class="v-no">Can't run here</td></tr> 180: 344: <tr><td class="cost">$0 if it runs</td><th>Local image model on C1</th><td>Rough concept sheets for you to react to, private, nothing ships</td><td>Untested on C1, and the GPU is shared. I didn't research models today.</td><td>Depends on the model</td><td>Your call, question 5 below</td></tr> 181: 345: <tr class="band"><td colspan="6">Paid, none recommended</td></tr> 182: 346: <tr><td class="cost">$38</td><th><a href="https://superhivemarket.com/products/hard-ops--boxcutter-ultimate-bundle">Hard Ops / Boxcutter</a></th><td>The standard hard-surface toolset</td><td>Menus, pies and clicks. No scripting mentioned.</td><td>GPL. Blender 3.5 to 5.2.</td><td class="v-no">Only for a human modeller</td></tr> 183: 347: <tr><td class="cost">$44.99</td><th><a href="https://superhivemarket.com/products/meshmachine">MESHmachine</a></th><td>Chamfer and fillet tools, normal detail plugs</td><td>Page doesn't say how it's driven.</td><td>GPL. Blender 4.2 to 5.2.</td><td class="v-no">No</td></tr> 184: 348: <tr><td class="cost">From $54.99</td><th><a href="https://superhivemarket.com/products/decalmachine">DECALmachine</a></th><td>Mesh decals in Blender</td><td>The game already places decals at runtime.</td><td>GPL. Blender 4.3 to 5.1.</td><td class="v-no">No</td></tr> 185: 349: <tr><td class="cost">$20 to about $70</td><th><a href="https://blendermarket.com/products/fluent/ratings?page=5">Fluent</a></th><td>Interactive boolean modelling</td><td>Same problem as Hard Ops <span class="c g">guess</span>. Listings conflict on price.</td><td>Not checked</td><td class="v-no">No</td></tr> 186: 350: <tr><td class="cost">$29, or $69 commercial</td><th><a href="https://superhivemarket.com/products/robot-designer">Robot Designer</a></th><td>Geometry Nodes robot generator, 800+ sliders, 25 presets</td><td>Someone else's look, with a real oatmeal risk.</td><td>Terms mix GPL with resale limits. Published about 7 months ago, Blender 4.5 to 5.2.</td><td class="v-no">No</td></tr> 187: 351: <tr><td class="cost">Not priced</td><th>A concept artist</th><td>One real four-view sheet to model against</td><td>It's the step every source has and we lack.</td><td></td><td>Only if the free week fails, and only on your go</td></tr> 188: 352: </tbody> 189: 353: </table></div> 190: 354: </section> 191: 355: 192: 356: <section class="part" id="forward"> 193: 357: <header><div class="tag">Part 4</div><h2>When you start this again</h2></header> 194: 358: 195: 359: <div class="two"> 196: 360: <div class="sub"> 197: 361: <h3>What changes</h3> 198: 362: <ul> 199: 363: <li><b>Design and building become separate steps.</b> Rough and many first, then model one.</li> 200: 364: <li><b>One hero at a time, judged moving.</b> Clips are the review. Stills are for diagnosis.</li> 201: 365: <li><b>You veto, you don't choose.</b> I bring variety and ask "what's off?"</li> 202: 366: <li><b>Surface gets equal time with outline.</b> Weighted normals, sculpted plates, designed seams, real decals, one settled look.</li> 203: 367: <li><b>Rules come last.</b> <code>docs/visual-language.md</code> goes back to draft until something lands.</li> 204: 368: <li><b>The critic changes job.</b> I ask Codex "what's the one idea here, and what feels cheap?" It never decides done. Your friends see clips too, since they gave useful reads early on.</li> 205: 369: </ul> 206: 370: </div> 207: 371: <div class="sub"> 208: 372: <h3>What I'd ask you, one at a time</h3> 209: 373: <ol> 210: 374: <li>Think of a moment in any game or show when a mech made you feel "that's it". What was it doing?</li> 211: 375: <li>In your ideal first hour of sortie, where's your mech on screen when it matters most?</li> 212: 376: <li>You've asked about the inner frame three times. Do you want to see it at all, and where?</li> 213: 377: <li>Is Gundam 00 still the target for the plain line mech, or did the knight board move that?</li> 214: 378: <li>Are rough private AI sketches fine for this, and do you already have an image tool you like?</li> 215: 379: </ol> 216: 380: <p class="note">No boards or menus during this. I'd play your answers back in your words and keep one short settled / open note. The clean-or-worn question gets answered by the reel, so I wouldn't ask it.</p> 217: 381: </div> 218: 382: </div> 219: 383: 220: 384: <div class="sub"> 221: 385: <h3>The first week</h3> 222: 386: <div class="scroll"><table class="week"> 223: 387: <thead><tr><th>Day</th><th>What happens</th><th>Your part</th><th>Done when</th></tr></thead> 224: 388: <tbody> 225: 389: <tr><th>1. Interview</th><td>The questions above. No building.</td><td>About 30 minutes</td><td>A short settled / open note</td></tr> 226: 390: <tr><th>2. Reel</th><td>No modelling. A 10-second clip of each existing mech (striker, pattern, all four knight lines): turn, boost, stop, plus one shot next to a pilot. Same clip in clean and worn looks. Makers need a small hook-up to the thruster bench.</td><td>Watch, say what's off, send it to friends if you like</td><td>The look is settled, and we know which mech already has some pull</td></tr> 227: 391: <tr><th>3. Sketches</th><td>30 or so rough silhouettes in SVG, pushed hard, none averaged from references. Rough AI sheets too if you said yes.</td><td>Cross out what's dead</td><td>Three survivors, no scoring</td></tr> 228: 392: <tr><th>4. Surface test</th><td>One chest and shoulder from a survivor, built with weighted normals, sculpted plates, the SDF fillet, drawn seams and decals. Shown at the chase camera and close up, moving.</td><td>Say which looks expensive and which looks plastic</td><td>One method chosen, the rest dropped</td></tr> 229: 393: <tr><th>5. Hero</th><td>One mech at one grade, with a reach, crouch and boost check before detail. Shown only as a reel.</td><td>React as you did to the thrusters</td><td>You say "that's done" about some of it, or name what's off</td></tr> 230: 394: </tbody> 231: 395: </table></div> 232: 396: <p class="note">You've since chosen to start over with one mech from scratch, so the plan at the top replaces this week. The test for the week was one part of one mech reaching the thruster reel's feeling. Grades, other makers and rules wait until then. The open shared shoulder bar question waits on your answer to question 3.</p> 233: 397: </div> 234: 398: 235: 399: <div class="two"> 236: 400: <div class="sub"> 237: 401: <h3>What I'd stop doing</h3> 238: 402: <ul> 239: 403: <li>Numbered polish rounds on one model</li> 240: 404: <li>Building twelve models before one is loved</li> 241: 405: <li>Turning one comment into a rule for every maker</li> 242: 406: <li>Putting ratios and plate counts in your reports</li> 243: 407: <li>Grey sheets of small tiles as the verdict</li> 244: 408: <li>Asking you to pick, or carrying a rolling list of naming decisions in every report</li> 245: 409: <li>Filling spare usage with systems while the look is open</li> 246: 410: <li>Long terminal reports: one page, clip first, one question at the end</li> 247: 411: </ul> 248: 412: </div> 249: 413: <div class="sub"> 250: 414: <h3>Risks I can't remove</h3> 251: 415: <ul> 252: 416: <li><b>Code-built may cap out.</b> My guess is that it holds at the chase camera and falls short in hangar close-ups. If the week's hero doesn't land, I'll say so plainly. The next step would cost money: one commissioned four-view sheet, not priced, on your go only.</li> 253: 417: <li><b>Sketches can promise more than the kit can build.</b> So day 4 comes before day 5, and only proven methods go on the hero.</li> 254: 418: <li><b>I can't watch video.</b> I judge frames. You and your friends are the only judges of motion.</li> 255: 419: </ul> 256: 420: </div> 257: 421: </div> 258: 422: 259: 423: <p class="note"><b>What I couldn't read.</b> Paradox forum (HBS diaries), Polycount, the Met and Age of Armour blocked direct fetches, so those are search excerpts. Kate Compton's original zine returned 403, so I used Game Developer's summary. CGWORLD and Tamashii Web were machine translated. I found no designer's own account of Gundam 00's shape choices, no source on Armored Core 6's or Lancer's art rules, and nothing usable on Gunpla inner frames. Prices are from listing pages today and can change.</p> 260: 424: </section> 261: 425: 262: 426: </div> 263: 427: </body> 264: 428: </html>