What do you do when the badge gets too long. @shadcn

Gemini 3.1 Pro landed in Blender, and the first thing it does is watch the viewport instead of reading the scene file Every other integration works from the data. This one works from what the render actually shows, which is the only thing a client ever sees. > LOOK - the viewport sampled as an image, the same way a human judges a shot > READ - the scene graph pulled in alongside it, so geometry and appearance are compared > SPOT - anything that looks wrong on screen but reads as correct in the data flagged > FIX - the underlying nodes and transforms edited, never the image A scene can be technically perfect and still look broken. Wrong normals, bad scale, a material that reads as plastic under one light. None of that shows up in the file. The data says everything is fine, because by its own rules it is. Comparing the two is the whole trick. The gap between what the scene says and what the frame shows is where every real bug lives. Fixing at the node level keeps it clean. Nothing is painted over, so the next render inherits the actual correction. Most artists already work this way - look, judge, go back and fix. This just closes that loop without a person in it. The viewport pass, the comparison rules and a full fix log are laid out underneath.

Introducing IMG2M3 No AI just a devtool that fixes the part AI can't link👇 img2m3.vercel.app

For reasoning effort, use a picker (menu), not a slider. It's better for both UX and a11y. You see every option at once. One tap instead of drag and release. And when you ship Auto, it has no position on a slider.