Side-by-side superyacht render comparison in Three.js and Blender
Side-by-side superyacht render comparison in Three.js and Blender is a 52.2-second Claude Opus motion design reference by @maxt3chno, built around Three.js, Blender. [Note: the creator shared a partial prompt. Copy this 3D motion prompt, keep the creator's frame counts and palette, and adapt the subject for your own launch film.
@maxt3chnoView post
Prompt
[Note: the creator shared a partial prompt. Wording below is theirs.]
GOAL:
TASK: model a superyacht from scratch in Blender via MCP and produce renders that match the references (shape, materials, lighting)
You are an experienced 3D artist (hard-surface, product visualisation) and a technical artist who writes bpy.
MOTION:
Using the blender MCP server, build a dark-navy superyacht from scratch in Blender from four reference images, and render it from the same four angles. The goal: with your render placed next to the reference, a person should not immediately tell which is which. Lighting and materials matter most. Geometry must be clean and well proportioned, but when time and attention are limited, materials, lighting and framing win.
0. Project and rules
Working folder: E:\Claude\SEA\yacht_blender_model\. Scene file: yacht.blend. Scripts: scripts\*.py. Renders: renders\. Report: PROGRESS.md. Everything you create stays inside this folder.
This is a standalone project. Do not read, modify or link anything in E:\Claude\SEA\Yacht or any other folder. No integration with other projects, no exports to other formats unless asked.
Download nothing (no HDRIs, models or textures). Everything is procedural: geometry from bpy/bmesh, materials from nodes, lighting from the scene.
Inspect Blender first: https://t.co/fdimPQSGng.version, what is open, whether there are unsaved changes. If the open file contains someone's content, delete nothing and ask the user. If the scene is empty or the default one, start a new file and save it as yacht.blend straight away.
Blender version. Principled BSDF input names, the sky model and the view transforms differ between 3.x, 4.x and 5.x. Do not guess: check the version and, when unsure, search the server's bundled documentation (search_api_docs, get_python_api_docs, data/api/).
How to work through MCP:Each part of the yacht is a separate file scripts\NN_name.py with a build() function. Scripts are idempotent: they delete their own objects by name and rebuild them. With execute_blender_code, run the file from disk rather than pasting hundreds of lines into the call. The whole model must be rebuildable with one command (scripts\build_all.py).
One call builds one part. Return structured data from the script (vertex counts, bounding boxes), not print output.
Units: metres, 1 BU = 1 m. All objects at scale 1,1,1 (apply transforms).
Save yacht.blend after every stage, plus a copy yacht_stageN.blend.
A long render can hit the MCP call timeout. Keep previews small (1000 × 558, 32–64 samples, denoised). If final frames time out, render them in the background from a terminal: "<https://t.co/fdimPQSGng.binary_path>" -b yacht.blend -P scripts\render_final.py.
Look at your own results. After every stage, render a preview to a file and open the PNG yourself (with the file-reading tool), next to the reference. A viewport screenshot is only good for a quick shape check. Judge colour and lighting only from Cycles renders.
1. References (open all four first)
E:\Claude\SEA\yac
Author original
TASK: model a superyacht from scratch in Blender via MCP and produce renders that match the references (shape, materials, lighting)
You are an experienced 3D artist (hard-surface, product visualisation) and a technical artist who writes bpy. Using the blender MCP server, build a dark-navy superyacht from scratch in Blender from four reference images, and render it from the same four angles. The goal: with your render placed next to the reference, a person should not immediately tell which is which. Lighting and materials matter most. Geometry must be clean and well proportioned, but when time and attention are limited, materials, lighting and framing win.
0. Project and rules
Working folder: E:\Claude\SEA\yacht_blender_model\. Scene file: yacht.blend. Scripts: scripts\*.py. Renders: renders\. Report: PROGRESS.md. Everything you create stays inside this folder.
This is a standalone project. Do not read, modify or link anything in E:\Claude\SEA\Yacht or any other folder. No integration with other projects, no exports to other formats unless asked.
Download nothing (no HDRIs, models or textures). Everything is procedural: geometry from bpy/bmesh, materials from nodes, lighting from the scene.
Inspect Blender first: https://t.co/fdimPQSGng.version, what is open, whether there are unsaved changes. If the open file contains someone's content, delete nothing and ask the user. If the scene is empty or the default one, start a new file and save it as yacht.blend straight away.
Blender version. Principled BSDF input names, the sky model and the view transforms differ between 3.x, 4.x and 5.x. Do not guess: check the version and, when unsure, search the server's bundled documentation (search_api_docs, get_python_api_docs, data/api/).
How to work through MCP:Each part of the yacht is a separate file scripts\NN_name.py with a build() function. Scripts are idempotent: they delete their own objects by name and rebuild them. With execute_blender_code, run the file from disk rather than pasting hundreds of lines into the call. The whole model must be rebuildable with one command (scripts\build_all.py).
One call builds one part. Return structured data from the script (vertex counts, bounding boxes), not print output.
Units: metres, 1 BU = 1 m. All objects at scale 1,1,1 (apply transforms).
Save yacht.blend after every stage, plus a copy yacht_stageN.blend.
A long render can hit the MCP call timeout. Keep previews small (1000 × 558, 32–64 samples, denoised). If final frames time out, render them in the background from a terminal: "<https://t.co/fdimPQSGng.binary_path>" -b yacht.blend -P scripts\render_final.py.
Look at your own results. After every stage, render a preview to a file and open the PNG yourself (with the file-reading tool), next to the reference. A viewport screenshot is only good for a quick shape check. Judge colour and lighting only from Cycles renders.
1. References (open all four first)
E:\Claude\SEA\yac
Questions
What is this 3d scenes prompt for?
It is a Claude Opus motion design brief for “Side-by-side superyacht render comparison in Three.js and Blender”. Paste it into Claude and keep the timings already written in the prompt.
Where is the original film?
The creator is @maxt3chno. Use View post to open the X video this prompt belongs to.