Airliner, inside out
A twin-engine airliner taken apart in six views: skin, X-ray, cross-section, exploded parts, engines and systems, through every phase from taxi to parked.
Made in Claude Code (Claude subscription) with claude-opus-5.5. The agent wrote code, looked at the preview and fixed it over several iterations. This is not a single-shot result: comparisons on this site show models in one attempt.
Starting prompt
Build "Airliner, inside out": an interactive technical animation that takes a modern twin-engine narrow-body airliner apart in front of the viewer. It shows how the aircraft is built and how it works, not just its outside. Single self-contained HTML file; Three.js and its addons from a CDN via an import map are fine; build everything procedurally, no external textures or models. The aircraft (about 38 m long, 34 m span, low swept wing, two high-bypass turbofans under the wing, conventional tail): - A livery skin with cabin windows, doors and cockpit windows. Under it a real structure: fuselage frames, stringers, floor beams, cabin floor and cargo floor. A cabin with rows of seats, overhead bins and galleys. A lower cargo hold with containers. - Wings with a front and rear spar, ribs and fuel tanks inside, and separate moving slats, flaps, ailerons and spoilers. Winglets. A tail with a moving rudder and elevators. - Engines with a nacelle (inlet, fan cowls, core cowl, nozzle and plug) and a real core inside: a twisted-blade fan with spinner, low- and high-pressure compressor stages, an annular combustor, high- and low-pressure turbine stages, and two concentric shafts. The low-pressure spool (fan, booster, LP turbine) and the high-pressure spool turn at different speeds. - Nose and main landing gear with wheels that retract into the fuselage. An automatic cinematic tour of six chapters, about 75 seconds, then it loops. Each chapter has its own camera work, a title and one line of explanation. 1. Product: the aircraft on a soft studio floor, slow camera move. 2. X-ray: the skin turns to glass and reveals the frames, stringers, floor beams, wing spars, ribs and fuel tanks. 3. Section: a cutting plane travels along the fuselage from nose to tail. The camera follows the cut face: cabin, seats, bins, floor beams and cargo hold in cross-section. 4. Exploded: the aircraft separates into its major assemblies. These are nose, fuselage barrels, tail cone, wings with their slats and flaps, tail surfaces, engines split along their axis into cowls, fan, compressors, combustor and turbines, and landing gear. The cabin interior lifts out. Every assembly is labelled, then it all reassembles smoothly. 5. Engine: a close-up cutaway of one turbofan running. The spools spin up from idle to take-off power and back. Air flows through it as particles coloured by temperature: cool bypass air around the core, heating through the compressor, white-hot in the combustor, cooling through the turbines and out of the nozzle. 6. Systems: a flight in sequence: taxi with a flight-control check, take-off with slats and flaps set, gear up, cruise, landing with full flaps and gear down, spoilers deploying at touchdown, then parked. Interface (a clean, light product-page style): - Mode tabs to jump to any chapter. - Flight-phase buttons: taxi, take-off, cruise, landing, parked. - Sliders for explode amount, section position and engine throttle. - A readout of N1, N2, EGT and thrust from the engine model. - A labels toggle and two or three colour themes for the livery. - A play/pause control with chapter progress. - Drag to orbit and scroll to zoom. The camera returns to the cinematic path a few seconds after the last input. Using a tab, phase button or slider pauses the tour until play is pressed. - Everything starts automatically and is visibly moving from the first frame. The layout works on a phone. Rendering: soft studio lighting with shadows, physically based materials, ACES tone mapping. Bloom only on the combustor glow and hot gas. The frame must stay clean and readable, never washed out by glare or haze. Engineering rules (the page must work on the first load, with no fixes): - Use Three.js r170 and only methods that exist on each of its classes. Give every custom ShaderMaterial `fog: false`, and declare every uniform, constant and varying its shaders use. - Declare each identifier once. Inside one calculation, never reuse a shared scratch vector for two values that are both still needed; use local vectors. - Guard every animated value against NaN. - Answer with the complete file exactly once, in a single ```html code block: no drafts, partial snippets or notes. Keep planning brief and write the code. Aim for roughly 800 to 1,200 lines, compact and well structured. No black, untextured or placeholder objects anywhere.