Interactive experiences · Practical guide
Choose a visual engine for an interactive experience
Choose a tool by what it must receive, produce, and sustain during the event. A polished demo alone does not explain project delivery, operation, or recovery.
Compare by data, delivery, and operation
Start by defining inputs and outputs: what data arrive, what picture must be produced, where it ends, and who operates it. If approved clips meet the goal, a 3D engine may add work without improving participation. If a character or scene must change every frame, the engine becomes part of the design.
| Tool | Documented starting point | Decision question |
|---|---|---|
| TouchDesigner | TOPs for image/compositing; CHOPs for numeric data. | Which operators, outputs, build, and license does the chain need? |
| Unreal | 3D scene, Live Link data, and Media Framework. | Who prepares character, logic, packaging, and operation? |
| Notch | Real-time creation/delivery depending on edition. | Is delivery video, media-server block, or executable, under which license? |
| Unity | Video integrated into an application using Video Player. | What development, plugins, platform, and support does the application need? |
Authoring and playback/deployment features are not interchangeable. Notch separates plans and delivery rights; Derivative distinguishes licensing by use. Confirm the exact version and current terms for each candidate before contracting. The proposal should identify the required licenses and who will develop, operate, and maintain the project.
Proposed comparison: the same character/graphic, identical fictional input, same resolution/destination, and an input-loss test. Record operation, recovery, resources, portability, maintenance, and editable deliverables. Choose using those results and the responsible team. After selection, configure using the matching version guide and keep the approved project.
Questions to plan the configuration
Does every experience need a 3D engine?
It depends on the response. Approved messages selected by an action may work as clips. A scene or character changing every frame requires evaluating logic, rendering, and interfaces.
What should be delivered beyond a demo?
Identified project/assets, versions, dependencies, applicable licenses, and operation/recovery instructions. Compare who can maintain the deliverable, not just its appearance.
Sources and scope
- Derivative — TOP — GPU image/compositing operators; confirm build, resources, and license for each project.
- Epic — Media Framework Overview, Unreal Engine 5.8 — Sources, textures, and audio inside the engine; plugins and compatibility depend on the selected route.
- Notch — plans and playback, 2026.2 — Editions and authoring, export, and playback rights by version.
- Unity 6.6 / 6000.6 — Video and cutscenes — Video integration in an application with Video Player; does not confirm all input devices.
- Derivative — Licensing — Licensing by use and features of the selected configuration.