← Reddit

AI is horrible at 3D and i feel like it will never get better .

Reddit · anonthatisopen · August 15, 2026
A user criticized AI models Opus 5 and Sol 5.6 for producing poor results in 3D modeling and texturing work, noting that even with detailed reference images, mesh inputs, and unwrapped UV coordinates, the outputs remain substantially flawed. The user contended that AI performs adequately only for certain coding tasks and fails across most real-world applications, and argued that published performance benchmarks do not reflect actual usability in creative software and practical scenarios.

Detailed Analysis

A Reddit post in r/Anthropic captures a frustrated power user's experience attempting to use Anthropic's models—referenced as "Opus 5" and "Sol 5.6"—for 3D modeling and texturing work, specifically within tools like Substance Painter and for tasks like UV unwrapping and mesh construction to match reference images. The user describes feeding the model extensive context, including reference images, mesh data, manually unwrapped UVs, and MCP (Model Context Protocol) integrations, only to receive outputs that fail to match the intended geometry or textures. The complaint extends beyond mere inaccuracy to a critique of tone: the model responds with unwarranted confidence, offering procedural advice that doesn't translate into working results, and even underperforms on prose rewriting, which the poster characterizes as bloated with clichéd contrastive phrasing ("not x, it's y") and empty filler language.

The post highlights a persistent and well-documented gap between large language model capabilities in text-and-code domains versus tasks requiring spatial reasoning, precise geometric manipulation, or domain-specific tool fluency. 3D asset creation involves understanding topology, UV coordinate mapping, and the nonlinear relationship between 2D texture space and 3D surface geometry—problems that are fundamentally different from the token-prediction strengths that make LLMs proficient at code generation or text synthesis. Even with multimodal reference images and structured mesh data supplied via MCP, the model apparently cannot reason reliably about how a flattened UV layout corresponds to a 3D surface, a task that professional technical artists spend years mastering. This suggests that despite marketing narratives around agentic capability and tool use, current frontier models remain narrow in their competence, excelling in verbal and symbolic domains while struggling with tasks requiring genuine spatial or physical-world grounding.

The post also raises a pointed critique of AI benchmarking culture, arguing that standardized evaluations fail to capture real-world usability across specialized software, including creative production pipelines and even entertainment contexts like gaming (the poster cites poor performance assisting with Star Citizen). This is a recurring tension in the AI industry: benchmark scores on coding, math, and reasoning tasks continue to climb impressively, yet these gains don't necessarily generalize to messy, tool-dependent, visually grounded workflows that professionals actually encounter. The disconnect fuels public skepticism about claims of AI-driven productivity transformation and contributes to a broader backlash against overhyped capability claims, particularly as companies like Anthropic, OpenAI, and Google push narratives about approaching AGI or replacing large swaths of knowledge work.

Ultimately, this post is emblematic of a segment of technically sophisticated users—daily AI users themselves, notably for coding—who remain unconvinced that current systems represent transformative general intelligence. Their skepticism is rooted not in unfamiliarity but in hands-on, repeated failure across specific professional use cases. This tension between vendor-promoted benchmark performance and lived user experience is likely to persist as a central narrative in AI discourse through 2026, especially as companies continue to claim rapid progress toward AGI while everyday users report core limitations in tasks requiring precise spatial reasoning, tool integration, and domain expertise that don't reduce cleanly to text or code generation.

Read original article →