Most AI video models give you one clip and stop. Hy-Nomas, released by Tencent Hunyuan on October 21, 2026, works more like a video game engine. You describe a world in text, and the model renders it as 720p video at 24 fps. Then you keep steering it, turn by turn, with new text instructions and camera moves from your keyboard and mouse. Each new segment remembers what came before, so you can walk down a street, turn around and still find the same buildings behind you. Two days after the release, a community port called ComfyUI-HyNomas brought it to ComfyUI, with an interactive explorer node you can drive with WASD. This guide explains what Hy-Nomas is, which files to download, how to set up the ComfyUI nodes, how to write world prompts and camera paths, and what to expect on a 16 GB GPU.
- What it is: an open interactive world model from Tencent Hunyuan. It generates video one segment at a time at 1280×720 and 24 fps, in 8 denoising steps, and you steer each segment with text, camera moves or both.
- License: the model code and weights are Apache 2.0, but the PixelUMM decoder (the VAE) is under NVIDIA’s non-commercial license, so treat outputs from the full pipeline as non-commercial.
- In ComfyUI: install ComfyUI-HyNomas by Nynxz and download the 9 GB INT8 DiT, the 15.8 GB PixelUMM VAE and the Qwen2.5-VL-7B text encoder.
- Controls: the Nomas Explore node gives you a live viewer with WASD, arrow keys and mouse look. Scripted workflows use Nomas Camera Path lines like
w 2orlook 30 0 1. - Speed: one user reports about 21 seconds per 3-second turn on an RTX 5090. A 16 GB card needs offloading and the short-history window mode.
What Is Hy-Nomas?
Hy-Nomas (“Towards Free-Form Interactive World Generation”) is what researchers call a world model: a video generator that you can interact with while it runs. Instead of writing one prompt and waiting for a finished clip, you build the video in turns:
- You describe the opening: the perspective (first person, third person follow or observer), the style (real world, CG, video game, animation or anime), the main subject and the scene.
- Hy-Nomas renders the first segment.
- You decide what happens next. You can type a change (“it starts to snow”, “the dragon lands on the tower”), move the camera with the keyboard and mouse, or do both at once.
- Hy-Nomas renders the next segment, continuing from the last one, and so on.
Tencent released everything: the weights, inference code, training code, data annotation code, a benchmark called Hy-Nomas-Bench with 280 test cases, and an online demo at hy-nomas.hy.tencent.com. One of their gallery examples is a 60-second video built from five 12-second text turns, which gives you an idea of how far a single world can go.
If you have only used clip generators like MiniMax H3 or Wan, the closest thing you may have tried is chaining clips with an extender. Hy-Nomas builds that chaining into the model itself, and adds real camera control on top. If you want a comparison with the clip-based models, see my best local AI video models roundup.
How It Works: Segments and Memory
Hy-Nomas is autoregressive across segments. Each turn you take becomes one video segment. Inside a segment, the model looks at all frames in both directions, the way a normal video diffusion model does. Between segments, it uses a key/value cache: a compressed memory of the earlier segments that the new segment can attend to. That cache is what lets the world stay consistent when you come back to a place you already saw.
Camera control works through camera matrices. When you press W or drag the mouse, your moves are recorded at 24 fps and turned into a camera trajectory for the next turn. The model only receives the direction and relative speed of the movement, because translations are normalised per turn. Rotation is scaled up by 2.5x by default, so mouse looks have a visible effect. Text and camera guidance are both set to 1.0 in the distilled model.
The output frames are not decoded by a normal VAE. Hy-Nomas uses a fine-tuned version of NVIDIA’s PixelUMM decoder, which turns small 4x16x16 blocks of latents into pixels in a single step, working over 10-frame windows with 5 frames of overlap. That decoder is why the VAE file is so large (15.8 GB), and it is also where the licence catch comes from (see below).
Specs at a Glance
| Item | Hy-Nomas |
|---|---|
| Developer | Tencent Hunyuan |
| Released | October 21, 2026 |
| Type | Interactive world model (text + camera control, multi-turn) |
| Output | 1280×720 (trained at 1280×704 in the ComfyUI port), 24 fps |
| Denoising steps | 8 (distilled) |
| Backbone | 54 double-stream MMDiT blocks, hidden size 2,048, 16 heads |
| Text encoder | Qwen2.5-VL-7B-Instruct |
| Latent space | DCAE-V, 32x spatial and 4x temporal compression, 32 channels |
| Decoder | Fine-tuned NVIDIA PixelUMM, single-step |
| Extra adapters | Cinematic LoRA (visual quality), Robotics LoRA (dual-arm robot footage) |
| Official hardware | 8 GPUs (standard) or one RTX 4090 with offloading |
| Licence | Apache 2.0 for Hy-Nomas; NVIDIA non-commercial for the PixelUMM decoder |
Tencent has not published a total parameter count yet. The technical report is marked “coming soon”.
License: What You Can and Cannot Do
This part matters if you make videos for clients or monetised channels. The Hy-Nomas model code and DiT weights are released under Apache 2.0, which allows commercial use. However, the ComfyUI port’s README points out that the PixelUMM decoder weights are a fine-tune of NVIDIA PixelUMM under the NVIDIA One-Way Noncommercial License, and marks them as non-commercial only. Since every frame you see passes through that decoder, the safe reading is that videos from the standard pipeline are for personal, research and experimental use. If you plan to use Hy-Nomas output commercially, read both licences yourself first.
Install ComfyUI-HyNomas
Hy-Nomas has no native ComfyUI support yet and there is no Comfy-Org repack. The working option is the community pack by Nynxz, which the author describes as “pure ComfyUI and torch” with no extra requirements.
- Update ComfyUI to a current build.
- Install the pack:
cd ComfyUI/custom_nodes git clone https://github.com/Nynxz/ComfyUI-HyNomas - Restart ComfyUI. The two example workflows appear under Templates, Custom Nodes, and are also in the pack’s
example_workflowsfolder:nomas_explore.json: the interactive explorernomas_world.json: a scripted world with an opening turn, a camera turn and a text turn, decoded to video
Model Files and Folders
The ComfyUI port uses converted weights from nynxz/Hy-Nomas, not the original Tencent files. The pack refuses Tencent’s own distilled_int8 format with a message, so do not try to load that one.
| File | Size | Folder | Notes |
|---|---|---|---|
nomas_dit_distilled_int8_convrot.safetensors |
9.0 GB | ComfyUI/models/diffusion_models |
Recommended. INT8 ConvRot DiT. |
nomas_dit_distilled_bf16.safetensors |
17.1 GB | ComfyUI/models/diffusion_models |
Alternative. Use it if you want to merge LoRAs. |
nomas_pixelumm_vae_bf16.safetensors |
15.8 GB | ComfyUI/models/vae |
PixelUMM decoder plus DCAE-V encoder. Required. |
qwen_2.5_vl_7b.safetensors or qwen_2.5_vl_7b_fp8_scaled.safetensors |
see repo | ComfyUI/models/text_encoders |
From Comfy-Org/Qwen-Image_ComfyUI. Same file as Qwen-Image uses. |
If you already run Qwen-Image, you have the text encoder. The fp8 scaled version is the better pick on 16 GB cards. In total, plan for about 35 GB of disk space with the INT8 DiT.
The Nodes Explained
The pack uses ComfyUI’s stock loaders and adds its own world nodes:
| Node | What it does |
|---|---|
| Load Diffusion Model | Loads the Hy-Nomas DiT. |
| Load CLIP | Loads Qwen2.5-VL-7B. Set the type to qwen_image. |
| Load VAE | Loads the PixelUMM decoder. |
| Nomas World Prompt | Builds the opening turn from a perspective, a style, one subject (written <|Subject1|> in the text), a scene description, an optional action and a length. |
| Nomas Prompt (JSON) | Takes a full multi-segment prompt with timestamps, in Tencent’s JSON format. |
| Nomas Camera Path | A text box of camera moves, one per line. Also sets the length of the turn. |
| Nomas World | Generates the opening turn(s). Outputs a LATENT and a WORLD. |
| Nomas World Continue | Adds one more turn to a WORLD, from a text change, an action, a camera path or a mix. |
| Nomas Explore | The interactive node: live preview, timeline and a small camera-path view, with Text turn, Undo, New world and Save video buttons. |
| VAE Decode | Stock node that turns the latents into frames in scripted workflows. |
Using Nomas Explore (WASD Mode)
This is the fun way to use Hy-Nomas. Load nomas_explore.json, check that the three loaders point at your files, and queue it once to build the opening turn. Then:
- Click inside the viewer so it captures your keyboard.
- Move with W, A, S and D, turn with the arrow keys, or drag the mouse to look around. Your moves are recorded at 24 fps and queued for the next turn.
- Press Text turn to type a change in words instead of (or together with) a camera move.
- Each new turn renders only its new frames, plus 5 overlap latents that are cross-faded into the previous turn so the join is smooth.
- Use Undo to throw away a turn you do not like, and New world to start over.
- When you are happy, press Save video. It writes an MP4 to
ComfyUI/output/video.
It is not real time. Each turn takes seconds to render, so think of it as “move, wait, watch” rather than playing a game. Short moves of 1 to 3 seconds per turn give you the most control.
Scripted Worlds With Camera Paths
If you want a repeatable result, use nomas_world.json instead. Here the camera moves are written as text in the Nomas Camera Path node, one move per line, in the format <keys> <seconds>:
w 2
w+left 1.5
wait 1
look 30 0 1
s 1
w 2: walk forward for 2 secondsw+left 1.5: walk forward while turning left for 1.5 secondswait 1: hold still for 1 secondlook 30 0 1: a mouse drag of 30 horizontally and 0 vertically over 1 seconds 1: step back for 1 second
The total of the seconds sets the length of that turn, so this example makes a 6.5 second segment. Chain several Nomas World Continue nodes to build a longer world: for example, a camera turn that walks into a market, then a text turn that says “a street performer starts juggling fire”, then another camera turn that circles him. Decode the final latent with VAE Decode and save it with your usual video node.
Writing Good World Prompts
The Nomas World Prompt node splits the opening into fields, which helps a lot. Some tips:
- Pick the perspective on purpose. First person works best for walking and exploring. Third person follow is better when the subject matters, such as a character or vehicle. Observer suits scenes you watch from a distance.
- Describe one subject clearly. The node supports one subject, referred to as
<|Subject1|>. Give it a short, concrete description (“a red-haired girl in a yellow raincoat”) and keep using the tag in later turns. - Make the scene explorable. “A narrow medieval street with market stalls on both sides and a cathedral at the far end” gives the camera somewhere to go. “A beautiful place” does not.
- Change one thing per text turn. Hy-Nomas was trained on turns with a description of the change, so “the sky turns orange as the sun sets” works better than rewriting the whole scene.
- Match the style to the training data. The official gallery covers real world, CG, video game, animation and anime styles. Stay within those for the best results.
Here is an example opening in plain words:
Perspective: third-person follow
Style: video game
Subject: <|Subject1|> is a small explorer robot with a round body, one blue eye and two thin legs
Scene: a mossy forest of giant mushrooms, with glowing spores floating in the air and a stone archway ahead
Action: <|Subject1|> walks slowly towards the archway
Then follow it with a camera turn (w 3) and a text turn such as “<|Subject1|> passes under the archway and a hidden valley with a waterfall appears”.
Note that every world starts from text. The port has no image-to-world input, so you cannot start from a photo yet.
Running It on 16 GB VRAM
Tencent’s reference setup uses eight GPUs, and their single-GPU configuration targets a 24 GB RTX 4090 with heavy offloading: the DiT and cache in INT8, the decoder in FP8, and each model moved to the GPU only for its stage. Neither Tencent nor the port author has published a VRAM figure. The ComfyUI port uses ComfyUI’s normal memory management, so offloading works as it does for other big models. On a 16 GB card like my RTX 5080, these settings give you the best chance:
- Use the INT8 DiT (9 GB), not the 17.1 GB bf16 file.
- Use the fp8 scaled text encoder.
- Keep window mode on. It is the default and keeps 18 past latent frames on the GPU (always including the first and the newest). Full mode keeps every frame and costs about 0.2 GB of VRAM per latent frame, which adds up fast.
- Use short turns. The history budget does not limit the memory used by the current segment, so a 12-second turn needs far more VRAM than a 3-second one.
- Have plenty of system RAM. Offloaded models sit in RAM. The port stores the INT8 cache in memory-mapped files in ComfyUI’s temp folder, so long worlds lean on the page cache, so I would plan for 64 GB of RAM with this pipeline.
- Use a fast SSD for both the model files and ComfyUI’s temp folder.
For reference, one user reported about 21 seconds per 3-second turn on an RTX 5090 with the INT8 DiT at 1280×704, plus about 4 seconds of decoding per 10-latent window. Expect a 16 GB card to be noticeably slower because of the offloading. For general ComfyUI memory fixes, my 16 GB out of memory guide covers launch flags and settings that also apply here.
The Official Tencent Repo (Linux, Multi-GPU)
If you have a Linux box with several GPUs, you can run the original code from Tencent-Hunyuan/Hy-Nomas. Tencent recommends their Docker image hynomasoss/hynomasoss:cu130, which bundles PyTorch, FlashAttention and MagiAttention. A manual install needs Python 3.12+, uv, the CUDA 13.0 toolkit and a C++ compiler:
git clone https://github.com/Tencent-Hunyuan/Hy-Nomas.git
cd Hy-Nomas
docker pull hynomasoss/hynomasoss:cu130
# or: uv sync --extra all && source .venv/bin/activate
The official pipeline reads its turns from a JSON prompt file with fields like segments, visual_description_long, description_change and contained_actions, and camera moves from trajectory files with camera-to-world matrices. The web demo also needs Tencent’s separate prompt enhancement service (Nomas-PE). For most people on Windows with one GPU, the ComfyUI port is the easier route.
The official release also includes two LoRAs: a Cinematic LoRA for better visual quality and a Robotics LoRA trained on dual-arm robot footage. LoRAs need the floating point (bf16 or fp32) DiT, because the INT8 loader cannot apply a separate LoRA at inference time.
Limitations
- Not real time. Each turn takes seconds to tens of seconds, even on top cards.
- Text only start. No image-to-world input in the ComfyUI port yet.
- Big downloads. About 35 GB for the smallest working set.
- Non-commercial decoder. The PixelUMM licence limits commercial use of the output.
- Young port. ComfyUI-HyNomas is a few days old and unofficial, and the speed figures so far come from single users. Expect updates and the occasional breaking change.
- Memory grows with the world. Long sessions need lots of system RAM and disk cache.
FAQ
What is Hy-Nomas?
Hy-Nomas is Tencent Hunyuan’s open interactive world model. It generates 720p, 24 fps video one segment at a time, and you control each segment with text instructions and camera moves.
Does Hy-Nomas work in ComfyUI?
Yes, through the community pack ComfyUI-HyNomas by Nynxz. It is not built into ComfyUI and there is no official Comfy-Org repack yet.
How much VRAM does Hy-Nomas need?
Tencent’s single-GPU setup targets a 24 GB RTX 4090 with offloading. No official VRAM number is published. In ComfyUI, the 9 GB INT8 DiT with offloading, window mode and short turns is the way to try it on 16 GB.
Can I use Hy-Nomas videos commercially?
The Hy-Nomas model is Apache 2.0, but the PixelUMM decoder weights are under NVIDIA’s non-commercial licence. Treat the output as non-commercial unless you have checked both licences for your use.
Can I start a world from my own image?
Not in the ComfyUI port. Every world starts from a text description.
How long can a Hy-Nomas world be?
There is no fixed limit, since you keep adding turns. Tencent’s gallery includes a 60-second video made from five 12-second turns. In practice, RAM and disk cache set the limit.
Final Thoughts
Hy-Nomas is the first open world model that feels usable on a home PC. Walking through a world you described in one sentence, and steering it with WASD, is very different from waiting for a single clip. It is slow, the downloads are huge and the decoder licence rules out commercial work for now, but the ComfyUI port makes it easy to try. Start with nomas_explore.json, keep your turns short, and use window mode on a 16 GB card.
More local AI video guides on Freakyjolly:
- Best Local AI Video Models in 2026
- MiniMax H3 Extender: Turn 1 Reference Image Into Multiple Connected Clips
- Best MiniMax H3 Text-to-Video Workflow for ComfyUI
- MiniMax H3 Out of Memory in ComfyUI: 16 GB GPU Fixes