The author reports that most of the six interaction-focused 3D projects produced usable prototypes from a single prompt, but visual polish was inconsistent and some controls only looked functional, with little meaningful feedback. The author did not isolate Blender MCP's effect, so the report cannot establish what improvement MCP contributed.
Tasks this report can inform: One user's subjective experience with a game, a physics simulation, a mechanical model, a scene, a model inspector, and a 3D-printable model.
Tasks this report cannot generalize to: Estimating an overall success rate, fairly ranking this model against others, inferring Blender MCP's independent contribution, or confirming that a model is actually printable.
Model version covered: GPT-6.2 Astra (as labeled by the author; no more specific model identifier was provided).
Test environment or client: The author said Blender MCP was enabled. The client, MCP version, coding model/execution environment, and hardware were not specified. The fourth project was deployed to Vercel.
Reasoning level and parameters: Not specified.
The author said they ran six different 3D projects at the same time. Initial builds used mostly one-shot prompts, without iterative prompt revisions. Google Hydrogen generated the prompts separately. The author did not provide the prompt texts, scoring criteria, number of repetitions, or a control group. Running all six in parallel may have introduced shared-environment or resource effects; the post does not say how these were controlled.
| Project | What the author reported as usable | Problems reported by the author |
|---|---|---|
| Two-player 3D tank game | A playable turn-based game; adjustable angle and power; three weapons, scoring, and sound effects | Weak projectile hit effects; mediocre terrain deformation; only three weapons |
| Interactive soft-body slime physics simulation | Deformable slime; adjustable stiffness, damping, and surface tension; parameter changes affected bounce and motion; color changes | Imperfect deformation; the author felt the visuals fell short of Claude Opus 5.5 or Fable examples they had seen. This was a subjective comparison, not a like-for-like test. |
| Mechanical tourbillon watch | Rotation and zoom; crown-winding interaction; animation speed adjustable from 0.1x to 10x; expandable components | Rendering was not realistic enough, and the materials and mechanical details lacked polish |
| Cyberpunk cliff scene | Three scene layers; camera bookmarks by layer; day/night lighting, dynamic shadows, rain, and auto-rotation; deployed to Vercel | The author reported no obvious functional problems during testing. Unexpectedly, the project was deployed to Vercel instead of running locally. |
| Fictional futuristic weapon inspector | Rotation and zoom, component descriptions, half-receiver interior view, blueprint, exploded view, and attachment switching | The “Cycle Action” button had no obvious effect; some controls looked usable but gave no meaningful feedback |
| Christmas table decoration for 3D printing | A recognizable model split into three parts that could be inspected beforehand | The tree geometry could be improved; printability and assembly had not been physically tested; the author estimated about 21 hours to print |
Six tests, run in parallel; initial builds were mostly one-shot prompts; the author said they did not iterate on prompts.
Google Hydrogen generated the prompts separately. The prompt text was not published in the collected Reddit text.
The author's visible comments shared images of the slime, game, and the watch's internal structure. The post also linked a YouTube video, but this article does not treat it as verified test data.
No success rate, scorecard, measurement method, number of repeated trials, elapsed-time records, or other reproducible metrics were provided. The estimate of about 21 hours is print time, not model-generation time.
This is one author's field report on a set of different tasks, not a standardized benchmark. The main observation was that interaction and basic mechanics were generally more reliable than visual polish. The weapon inspector also showed that interface controls can look functional while providing insufficient feedback. With no control group, public prompts, or MCP ablation, the results cannot be attributed to Astra alone, nor can six tasks establish general performance. The printed model has not been physically validated.
The reproducible details are limited to the model name, Blender MCP being enabled, the six task types, parallel execution, and mostly one-shot prompts during the initial phase. Reproducing the tests would also require the original prompts, Hydrogen version, MCP/client configuration, runtime environment, actual time per task, and explicit acceptance criteria; the post did not provide these.
GPT-6.2 Astra