Gemini 4 roasts Google's 3D harness: blind coordinate writing and how to fix it

Ryoiki-Tokuiten · reddit · 2026-11-01

A Reddit user iterating a Three.js 3D scene with Gemini 4 Argon asked the model to explain itself, and got a strikingly candid self-analysis. Gemini admits its first-pass 3D code is bad because it writes coordinates blind, with two specific blind spots: visual occlusion in wide shots (it can't tell a hand became a rectangular block from 20m away), and the 2D-screenshot-to-3D-coordinate translation gap (it sees the clipping but can't compute the exact (x, y, z) offset). Its prescription: the harness must show it the rendered image every iteration via viewfile, and print exact 3D bounding boxes, joint world positions and [CLIPPING] flags alongside, so it fixes the exact rotation in one turn instead of guessing for five. It also notes the harness wasn't even rendering the actual pipeline, calling this the entire Bitter Lesson for 3D harnesses. Both a fun model-behavior observation and a directly actionable recipe for vision-feedback agent loops.

Original post →

More from coding & agent

coding & agent channel →