Iteratively match a flying-car simulation to video
At a glance
A hobbyist used Claude and three.js to build and revise a simulation of a filmed Roadster stunt. This workflow is listed under Simulation, Creative Coding, Prototyping.
- Agents / tools
- Claude Opus 5.5, three.js, WebMCP, Claude for Chrome
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Give Claude Opus the video and ask it to create a three.js simulation that matches the footage. The author identified the five parked vehicles and supplied approximate dimensions for all six cars because the dark video made identification difficult. 2) Compare the initial simulation with the footage, ask Claude to correct the leftward path, then compare positions frame by frame and request corrections to the roll. 3) Check thruster behavior: the author asked for the six visible thrusters, four underneath and two near the front wheels, instead of the model's assumed twelve. 4) When the side thrusters still did not fire in flight, Claude added wind gusts and a 100 Hz feedback loop. The author then added WebMCP so the Claude Chrome plugin could adjust parameters and answer questions about the simulation.
How it went
After a multi-day process the author considered the simulation close enough to the footage and could vary parameters including weight, maximum thrust and height.
Worth knowing
Mass, drag coefficients, thruster positions and gas performance were estimates rather than Tesla data; the feedback model assumed perfect sensors. Some parameter combinations produced invalid flight paths.