Previsualization intent · H3 reference to Unreal Sequencer
Use MiniMax H3 for cinematic previs, then rebuild approved shots in Unreal Sequencer with controllable scenes, cameras, timing, and evidence.
MiniMax H3 can generate short multimodal video references for composition, movement, audio rhythm, and transitions. Use the clip as previsualization: extract shot duration, lens intent, camera path, subject blocking, environment state, light change, audio beat, and cut point. Rebuild those decisions with Cine Camera Actors, Level Sequences, production assets, and deterministic timing in the Unreal project. When interactivity is part of the scene, use SEELE to generate the playable context before refining the cinematic layer.
Choose the prompt closest to the user job, review the prefilled scope, and generate the native project. Each prompt converts a video-model intent into input, state, objective, failure, restart, and an inspectable SEELE handoff.
Create a native Unreal 5 third-person exploration slice in an original underground observatory. The player restores one console, triggers a twelve-second machinery reveal, regains control, crosses the opened bridge, reaches completion, can fail, and can restart. Include browser preview and a downloadable project for Sequencer refinement.
Use this Unreal promptGenerate an Unreal 5 scene with one playable corridor, one interaction, a short in-engine camera transition to reveal a distant structure, a skip path, reliable control restoration, objective feedback, completion, failure recovery, immediate restart, and native project output.
Use this Unreal promptBuild a compact Unreal 5 arena where the player crosses a trigger, a short boss entrance sequence plays, control returns, one enemy attack can be dodged, victory and defeat both work, restart is clean, and the sequence can be skipped without duplicating state.
Use this Unreal promptCreate a native Unreal 5 weather-station slice with one lever interaction, a timed storm transition, lighting and audio feedback, a new traversal route, completion, failure recovery, restart, browser preview, and project download for camera and sequence polish.
Use this Unreal promptAn inspectable Unreal project rather than a rendered clip, prompt answer, or unsupported provider-integration claim.
A fast playable check for camera, controls, objective clarity, feedback, success, failure, and restart before local continuation.
A workflow for performance review and package preparation before external distribution or platform submission.
A local handoff for source, Blueprints, assets, plugins, rights, build settings, target-device checks, and continued production.
First/last-frame control, multimodal references, video editing, V2V motion transfer, native audio, and 4–15 second clips support rapid exploration of a bounded cinematic beat.
A reviewer can approve framing, pace, subject direction, light progression, transition, color intent, and audio emphasis without claiming that production assets or final animation already exist.
Sequencer must own cameras, tracks, timing, bindings, animation, events, effects, audio, render settings, and the transition back to gameplay. Asset quality and performance remain native project concerns.
If a cinematic belongs inside a game, first create the small playable world and interaction path in SEELE. Then refine the shot against the actual level, scale, character, input state, and performance budget.
Choose one decision: camera reveal, character entrance, environment transition, action beat, UI-to-world transition, or audio cue. Specify duration, aspect ratio, continuity anchors, and what would make the result unusable.
Create a rights-cleared H3 reference, then mark frames for camera start and end, lens feeling, subject path, action timing, light changes, audio events, transitions, and intentional discontinuities. Reject accidental temporal artifacts.
When the shot interrupts or returns to play, define the player state before and after it. Use SEELE to generate the native Unreal slice with the relevant environment, mechanic, objective, and recovery behavior.
Use production cameras, transforms, rails or rigs, animation, event tracks, effects, audio, and render settings. Keep gameplay-owned state outside fragile cinematic bindings and verify skip, interruption, replay, save, and streaming behavior.
Render a native review version and compare composition and timing with the previs, not pixel identity. Record accepted deviations, performance, assets, rights, project revision, and the final source of every frame and sound.
Copying a generated camera path literally can create impossible speed, collision, parallax, or player discomfort.
A beautiful shot can leave input locked, duplicate events, break saves, or return the player to an invalid state.
Temporal artifacts may be mistaken for intentional animation or effects requirements.
Previs audio and voices can introduce rights, consent, localization, and mixing problems.
| Dimension | What good looks like | Evidence to keep |
|---|---|---|
| Shot clarity | One cinematic decision is visible without depending on accidental artifacts | Annotated frame and timing sheet |
| Gameplay continuity | Control, state, events, and camera recover correctly before and after the shot | Native transition tests |
| Real-time fit | The shot works with actual scale, assets, streaming, and frame budget | Project capture and performance record |
| Source integrity | Every reference and production element has a known owner and role | Media and project provenance map |
“Fast and tense” becomes duration, focal behavior, path speed, acceleration, shake limits, cut timing, exposure, color, and audio beats that a Sequencer owner can reproduce.
Let the shot request or observe gameplay-owned state through explicit events. Avoid burying persistent rules in temporary cinematic bindings that fail on skip or replay.
Validate natural completion, skip, interruption, death, pause, map streaming, replay, save/load, and returning control at low frame rate. The happy-path render is only one case.
The native version should preserve the approved story and timing while respecting real assets, rig limits, collision, camera comfort, and performance. Pixel matching a generated reference is not the production goal.
Snapshot date: August 4, 2026. MiniMax’s July 31, 2026 release and current API documentation identify the API model as MiniMax-H3 and support H3’s video modes, duration, resolution, frame rate, multimodal references, audio, and dated pricing. They do not establish an Epic-supported Unreal integration or native game output. Epic documentation and the tested project remain authoritative for engine behavior.
First-party release positioning, H3 technologies, multimodal context, video and audio claims, editing, motion transfer, and target industries.
Open official announcementModel name, supported generation modes, 4–15 second duration, resolution, frame rate, aspect ratios, and reference inputs.
Re-check current output and reference-material pricing before spending. Use Epic documentation and the actual project for engine, asset, animation, UI, cinematic, build, and package decisions.
Use MiniMax H3 V2V motion transfer as character reference, then validate rigs, animation graphs, root motion, collision, and gameplay in Unreal.
Open this workflowBudget MiniMax H3 video experiments for an Unreal game, account for references and retries, and spend only after a playable slice proves the idea.
Open this workflowUse MiniMax H3 for game-video reference, then turn the approved mechanic and visual brief into a native Unreal 5 project with SEELE AI.
Open this workflowNo. H3 can create a useful short previsualization, but Sequencer controls the actual Unreal cameras, tracks, bindings, animation, events, effects, audio, render settings, and gameplay transition. Rebuild approved decisions in the project and verify them against the native scene and state. Confirm the current provider documentation before you lock a production decision.
Record shot duration, aspect ratio, start and end composition, lens intent, camera path, subject blocking, action beats, environment state, light changes, audio events, transition points, and continuity anchors. Also mark artifacts or impossible motion that must not enter the Unreal specification. Treat the tested Unreal build, not the reference clip, as acceptance evidence.
Use SEELE when the shot needs a playable context that does not yet exist. Generate the native Unreal 5 scene and mechanic, validate the browser-preview loop, then refine cameras and timing against that real level instead of designing the cinematic around a disconnected video. Keep prompts, outputs, project versions, and review notes in the same decision log.
A licensed clip can be used as a media plate or reference where appropriate, but that does not create editable geometry, cameras, rigs, animation tracks, gameplay state, or real-time lighting. Confirm codec, audio, color, rights, performance, and platform behavior for any runtime media use. Recheck rights, runtime behavior, performance, and packaging before any external release.
Test the player state before the shot, input lock and restoration, camera handoff, event uniqueness, skip, replay, pause, failure, save/load, streaming, and low-frame-rate behavior. Completion should return the player to one explicit valid state without duplicating rewards or objectives. Use the browser preview to reject weak interaction before deeper production work.
No. Preserve the approved composition, action, timing, and emotional purpose while accepting differences required by real assets, scale, rigging, collision, camera comfort, lighting, and performance. Document intentional changes so reviewers know why the production version is safer or more playable. Record the source clip separately from the native project and package evidence.
Use H3 to answer the video question. Use SEELE to generate the playable system: native Unreal project, browser preview, optimization and packaging path, and a downloadable handoff. Keep concept media and native evidence clearly separated.