Skip to content
Kingy AI

Kingy / Make This

← All outcomes

Build an interactive V8 cutaway

An editable 3D engine exhibit with synchronized pistons, valves and a guided tour.

18-second capture of the original interactive exhibit.
Selected model attempts
Not recorded
Selected model charges
Not recorded
Human editing
Not recorded

kingy tested

Open the actual result ↗

Reproduce the outcome

  1. Download and extract the source package.
  2. Open a terminal in project and run npm run preview. This serves the included built app locally.
  3. Open http://127.0.0.1:4317 and inspect the actual model.
  4. To adapt, make a separate copy, edit project/app/page.tsx INITIAL state using the exported change below, then install dependencies and rebuild only when you choose.
  5. For a rebuilt copy, run npm test and inspect selected-cylinder labels, pause/scrub behavior and phone layout.
Original input and exact settings
  • Original directed production brief
  • Original procedural geometry; no external asset upload required
selectedCylinder
1
angle
35
speed
0.5
view
section
Original prompt
Build an original interactive web exhibit called “Inside the Machine.” The opening view should make the viewer want to rotate the engine and understand it. Use a restrained warm-white interface, graphite metal, copper details, and one red accent. Give the engine most of the screen. Keep technical controls secondary until requested.

Choose and document one consistent V8 configuration. Establish cylinder numbering, firing order, crank geometry, cam relationship, and the four-stroke cycle using primary technical references before implementation. Use the same definitions throughout the geometry, animation, labels, and diagrams. If a mechanically credible V8 is blocked, report the specific problem before substituting another mechanism.

Model recognizable crankshaft, connecting rods, pistons, cylinder banks, and the valve/cam mechanism required by your explanation. Derive connected part positions from a shared crank angle and explicit geometry. Add a section view that reveals the working parts, an assembled view, and an exploded inspection view. Use a fixed, reproducible timeline that can be scrubbed, paused, and stepped without changing the mechanical relationships.

Controls: orbit/zoom, reset camera, pause/play, scrub a full four-stroke cycle, change playback speed, select a cylinder, and switch inspection views. A selected cylinder should show its current stroke and a simple linked diagram. Separate any illustrative pressure coloring from measured or simulated thermodynamics. Label the mechanical simplifications in an accessible information panel.

Create a short guided sequence: assembled engine, cutaway, slow-motion cylinder cycle, exploded inspection, return to the complete engine. Every transition should help the viewer follow the same object. Preserve an easy manual-control mode. Recompose the controls for a phone; do not shrink a desktop dashboard until the text is unreadable.

Use the installed website-building workflow and suitable available local tools. Record libraries and versions. Keep geometry and animation editable. Build and inspect the actual app. Check linked motion at several crank angles, the period of the cycle, control behavior, and desktop/phone layouts. Make one targeted correction if a material defect remains.

Deliver a runnable web project, source and dependencies, a 15–20-second demonstration capture, two actual screenshots, a README, the mechanics references and assumptions, and a change example. Include a geometry export if the chosen workflow supports it reliably; distinguish that geometry from the interactive app.

Work inside this task's new local project. Make routine design choices yourself. Use available dependencies and original/procedural assets. Identify missing installations or permissions precisely. Do not publish, buy services, or operate physical hardware. Record the first delivered result and all human follow-ups.

Attribution and rights: Original Kingy procedural implementation; retain attribution and bundled third-party MIT/ISC notices. Inspiration was credited; no source assets were copied.

Sources & limits

Inside the Machine: actual interactive exhibit

Record checked 2026-09-06.

This is one retained directed build, not a model comparison or guaranteed one-prompt reproduction.

Illustrative mechanics omit combustion, thermal behavior, fluids and engineering tolerances.

Phone verification used a Chrome viewport, not physical phone hardware.

Generation/tool session cost and active human time were not recorded; no new generation was performed for this recipe.

Help improve this tool

Did this help you finish?

About Make This. Your feedback goes to Kingy’s private review queue.

Your experience with Make This
What happened?