Opus 5.5 recreates MengTo’s room in editable Three.js
MengTo used Opus 5.5 to recreate his room in Three.js from photos and videos for animated tutorials. The scene supports equipment, lighting and camera changes, while Three.js reduced laptop load.
TL;DR
- A real room became a virtual tutorial set: MengTo says he used Opus 5.5 to recreate it in Three.js.
- The set stays editable, with equipment, lighting and camera changes available.
- Laptop load drove the tool choice: MengTo says Blender made multitasking harder, so he deliberately used Three.js.
Three.js keeps objects, lights and cameras in a scene graph. MengTo also linked Kimi 3D Make, whose feature guide includes video and Live Photo exports.
Photos and videos as reference
MengTo supplied photos and videos of his actual room as reference. He asked Opus 5.5 to recreate the space for animated tutorials, a refreshingly practical brief for AI 3D.
Equipment, lighting and camera
MengTo calls the room a “playground,” with three kinds of changes available:
- Change the equipment.
- Adjust the lighting.
- Move the camera.
Those controls sit within Three.js's rendering setup: a renderer takes a scene and camera, then draws the camera's view onto a 2D canvas.
Three.js over Blender
MengTo deliberately chose Three.js because Blender took too long and pushed his laptop hard enough to interfere with multitasking.
The work also involved time at the object level. In another reply, he described the process running “in a loop across multiple hours for each object.”
Kimi 3D Make
In a separate post, MengTo argued that building in 3D should be part of every coding-agent harness and linked Kimi 3D Make.
Kimi's official guide separates three creation types:
- 3D Web: interactive websites and mini-games, with online previews and sharing.
- 3D Modeling: objects generated from text or reference material for viewing and further editing.
- 3D Printing: model files for inspection and print preparation in external software.
The browser tool requires a Kimi account. It accepts natural-language requests or reference images, with revisions handled through conversation; generation and edits consume Kimi's unified usage quota.
Kimi also draws a distinction between the outputs: a model displayed on a web page does not necessarily come with a standalone model file, and its printing mode does not connect to or control a printer.