The author generated a motorcycle demo once with the same short prompt for each model, then showed Gemini 4 Carbon and Opus 5.5 side by side. The video focuses on switching between perspective, cutaway, and exploded-parts views.
Suitable tasks: Exploring 3D demos that can switch views and show mechanical structures and disassembled parts.
Unsuitable tasks: Verifying real mechanical structures, part assembly relationships, code quality, or runtime performance; the post provides no evidence for these.
Applicable model versions: Gemini 4 Carbon; Opus 5.5 (video label). The specific build versions are not stated.
Applicable clients, agents, or APIs: Not stated. In a reply, the author said Carbon access was obtained through Arena, but did not say which client or execution environment was used to generate the demo.
Recommended reasoning level and parameters: Not stated.
The original post and demo video both show the following short prompt:
a café racer you can X-ray, cut in half, explode and lay out part by part.This is only the task description visible in the original post. It does not include any undisclosed system instructions, settings, or other inputs.
The author said the same prompt was submitted once to each model (“Same prompt, one shot each”). The video shows the results side by side, with the view options Product, X-ray, Cutaway, Exploded, and Laid out visible in the interface. When the display switches to the exploded view, the parts of both motorcycles are shown spread out. The post does not provide reproducible operating steps.
The X page identifies the author as Dromexa (@dromexa) and gives the publication date as October 29, 2026; the original post embeds a 0:29 video.
The post says the comparison is between Gemini 4 Carbon and Opus 5.5 and that the same prompt was run once on each. The video also labels them “GEMINI 4 CARBON” and “OPUS 5.5.”
The video presents the two generated results and their view controls side by side. Visible shots show the motorcycles’ exteriors, X-ray/cutaway views, and exploded parts. The author said Carbon’s motorcycle looked more like a real workshop build and considered Carbon the winner in 3D; this is the author’s subjective assessment.
Someone asked in the replies whether Carbon was accessed through Arena, and the author answered, “yes, via Arena”. This only describes the access source reported by the author and does not confirm that the generation interface or comparison workflow took place in Arena.
The original post and replies do not disclose the full system prompt, client or agent, model build versions, reasoning level, parameters, generation time, code, output files, or independent retest data.
This is an author demo of a single task, with one run per model. “Same prompt, one shot each” is the author’s statement and cannot establish which model is better at other 3D tasks.
The video shows interactive controls and visual results for disassembled parts, but does not verify the code behind the controls, geometric accuracy, whether the parts can be assembled, or runtime performance.
Unlike the robotic-eye example, this example shows switchable views of a mechanical object and a part-by-part disassembly demo; it is not just an animation around a single subject. Both examples come from individual posts, so they do not establish the scope of either model’s capabilities.
Collected on 2026-11-16. The original X post was opened through Tabbit, the English original was expanded, and the post text, author replies, video duration, prompt shown in the video, and model labels were checked. The video was played to inspect the side-by-side results and visible view controls. The video was not downloaded, no source code was obtained, and the model was not run for reproduction. Apart from the author’s reported source of Carbon access, the execution settings were not disclosed.
Gemini 4 Carbon