Released July 31, 2026 · independent Unreal production guide
Use MiniMax H3 for game-video reference, then turn the approved mechanic and visual brief into a native Unreal 5 project with SEELE AI.
MiniMax H3 is a multimodal video-generation model, not an Unreal Engine plug-in or coding model. It can turn text, images, video, and audio references into 4–15 second video at up to 2K with native stereo sound. Use those clips to test visual direction, motion, shot structure, interface mood, or a pitch. Then convert the approved player loop into a native Unreal 5 project in SEELE AI, preview it in the browser, and continue with project, packaging, and target-device checks.
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 game from an approved multimodal-video concept. Build one compact coastal observatory, one traversal route, one power-restoration interaction, one weather transition, clear controls, success, failure recovery, immediate restart, browser preview, and a downloadable project. Use original unbranded assets and do not treat the reference clip as gameplay proof.
Use this Unreal promptCreate a native Unreal 5 vertical slice with one player controller, one primary mechanic, one objective chain, visible feedback, completion, failure, and restart. Keep the environment compact and original, verify the full loop in browser preview, and prepare the project for local inspection before any marketing capture.
Use this Unreal promptCreate an Unreal 5 playable scene with a third-person exploration camera, one short interaction route, two deliberate cinematic transitions that return control cleanly, no locked input after a shot, clear objective feedback, failure recovery, and a browser-previewable build.
Use this Unreal promptGenerate a small native Unreal 5 game from a rights-cleared brief containing visual, motion, and audio references. Preserve only the approved player loop and mood, use original production-safe assets, expose assumptions, and include browser preview, restart testing, packaging checks, and local project download.
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.
MiniMax announced H3 on July 31, 2026 as a general-purpose multimodal video model. The official API model name is MiniMax-H3, with text-to-video, image-to-video, first/last-frame, reference generation, and video-editing workflows.
Official documentation lists 2K output, integer durations from 4 to 15 seconds, common or adaptive aspect ratios, and 24 fps. H3 can use text, image, video, and audio material as unified context and can generate native stereo audio.
MiniMax highlights instruction following, text and brand rendering, V2V motion transfer, editing, UI/UX, and gaming. These are useful preproduction and marketing signals, but none proves an engine-ready asset, Blueprint graph, C++ module, playable level, or packaged build.
SEELE AI is the handoff when the goal changes from a rendered clip to a playable artifact. Provide the mechanic, camera, world, objective, controls, success, failure, restart, and visual references; then generate and inspect the native Unreal 5 project.
Decide whether the H3 experiment should answer a question about camera language, world mood, character motion, interface feedback, trailer structure, or audio rhythm. Keep one question per clip so reviewers can distinguish an attractive result from a useful production decision.
Use only material your team can process: a concise text brief, original frames, approved motion reference, permitted audio, and exact exclusions. Record model name, settings, duration, resolution, prompt, source files, and any regeneration steps.
Mark what the clip establishes and what remains unknown. A video can communicate timing and appearance; it cannot prove collision, input, state ownership, replication, performance, accessibility, save behavior, or platform packaging.
Write the player verb, camera, environment, objective chain, input, feedback, success, failure, restart, target session length, and the visual rules approved from the clip. Remove cinematic details that do not affect the playable slice.
Open SEELE’s Unreal creator, submit the bounded brief, generate the native Unreal 5 project, play the browser preview through success and failure, then inspect the downloaded project or package on the actual target workflow.
Do not call H3 an Unreal plug-in, editor agent, Blueprint generator, C++ assistant, or runtime system.
Do not present a generated clip as gameplay, a SEELE product screenshot, or proof that a mechanic exists.
Do not copy visual errors, impossible camera moves, unstable text, or temporal artifacts into the game brief.
Do not submit confidential assets, unreleased characters, voices, music, or player data without approved processing terms.
| Dimension | What good looks like | Evidence to keep |
|---|---|---|
| Visual decision | The clip resolves one named art, motion, shot, UI, or audio question | Decision note plus approved and rejected frames |
| Playable translation | The brief names player input, state changes, objective, feedback, failure, and restart | SEELE prompt and acceptance checklist |
| Native proof | The generated project behaves correctly beyond a passive camera pass | Browser-preview run and local project checks |
| Release boundary | Video rights and game-release requirements remain separately owned | Provenance, licenses, build record, and approvals |
A shot list may map to Cine Camera Actors and Level Sequences, but gameplay cameras, input, streaming, transitions, and player agency still need explicit ownership.
Use an H3 frame or clip to communicate direction. Rebuild or acquire production assets through a rights-cleared pipeline and verify materials, scale, rigs, LODs, collision, and performance.
Native stereo sound can communicate mood and timing, but Unreal audio cues, attenuation, concurrency, subtitles, localization, mixing, and runtime triggers remain separate work.
Keep the H3 prompt and media receipt beside the SEELE creation brief, project revision, test results, and package manifest so later reviewers know which artifact proved which claim.
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.
Convert a MiniMax H3 game concept into a scoped mechanic, generate a native Unreal 5 project in SEELE, and validate the playable loop.
Open this workflowUse MiniMax H3 for cinematic previs, then rebuild approved shots in Unreal Sequencer with controllable scenes, cameras, timing, and evidence.
Open this workflowExplore game UI motion with MiniMax H3, then rebuild approved states in Unreal UMG with functional input, accessibility, localization, and tests.
Open this workflowThe cited MiniMax release and API documentation do not establish an official Epic or Unreal integration. H3 produces video from multimodal inputs. Treat the result as reference material, then implement and verify the selected mechanic, scene, UI, animation, or cinematic in the actual Unreal project. Confirm the current provider documentation before you lock a production decision.
No official source cited here says H3 generates a native Unreal project. H3 generates and edits video. SEELE AI provides the direct creation handoff described on this page: generate a native Unreal 5 project from a bounded brief, inspect a browser preview, then download or continue packaging. Treat the tested Unreal build, not the reference clip, as acceptance evidence.
Copy only approved decisions: player verb, camera style, environment, objective, interaction beats, feedback, failure, completion, restart, and visual constraints. Do not copy impossible motion, accidental text, temporal artifacts, copyrighted characters, or details that cannot be owned and tested in a playable system. Keep prompts, outputs, project versions, and review notes in the same decision log.
No. H3’s 2K specification describes the generated video output. Unreal render resolution, frame rate, scalability, upscaling, texture budgets, platform profiles, and performance targets must be configured and measured in the real project on representative hardware. Recheck rights, runtime behavior, performance, and packaging before any external release.
That depends on the rights in every input, the output terms, identity and voice consent, music ownership, and your distribution requirements. Even when the audio is usable, Unreal implementation still needs cue structure, mixing, attenuation, subtitles, localization, runtime triggers, and platform validation. Use the browser preview to reject weak interaction before deeper production work.
Create one three-to-five-minute vertical slice with one camera, one primary interaction, one objective chain, clear success and failure, immediate restart, and the minimum environment needed to reproduce the approved visual idea. Generate it, play every state in the browser preview, then inspect the native project. 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.