YUME

YUME

Interactive first-person world video from an image (and text on 1.5), driven by keyboard-style motion. Two in-tree variants, both runner-verified.

YUME generates explorable first-person world video. An image (and on YUME-1.5, text and optional video) goes in; a clip that follows keyboard-style motion comes out. It is not a prompt-only cinematic T2V model, not a 3D splat generator, and not a Cosmos world-foundation card.

Official paper teaser: An example of re-annotating the dataset. The original and new captions are used for T2V and I2V training, respectively. The Original caption describes detail scene context, while the New caption, generated by VLM,.
Official paper teaser: An example of re-annotating the dataset. The original and new captions are used for T2V and I2V training, respectively. The Original caption describes detail scene context, while the New caption, generated by VLM,.

WorldFoundry keeps two vendored in-tree adapters under Apache-2.0. Both runner paths are verified:

  • yume — official stdstu123/Yume-I2V-540P. Image-first. Sizes 544×960 or 960×544. Artifact yume.mp4.
  • yume-1p5 — official stdstu123/Yume-5B-720P. Prompt + image + video. Default size 704×1280 (also 1280×704). Artifact yume-1p5.mp4.

The paper / project write-up is Yume1.5 (project page, github.com/stdstu12/YUME). Title-page thumb stays beside the heading.

Build your run

Pipeline
YumePipelineworldfoundry.pipelines.yume.pipeline_yume
TaskInteractive Video interactive-video
Environmentworldfoundry-unified-cu128
DeviceCUDA 12.8
Runnerworldfoundry.pipeline
Loadingfrom_pretrained
Invocationnative_or_standard_invocation
worldfoundry-eval run \
  yume \
  --pipeline.task-profile interactive-video \
  --json

Variants

  • yume
    StatusRunner parity pending

    image/video-to-world-video

    Runtime profileyume

    Pipeline bindingyume

  • yume-1p5
    StatusRunner parity pending

    image/video/text-to-world-video

    Runtime profileyume-1p5

    Pipeline bindingyume-1p5

What it is for

Walk a still scene. Recorded inputs: prompt, image, video, plus navigation_actions and camera_actions. The pipeline requires at least one interaction — a WASD-style move or an arrow-key camera action. No interaction list means the run fails before sampling.

Use yume for the lighter 540P image-conditioned route. Use yume-1p5 when text guidance and 720P matter. Do not send this card a text prompt expecting a general T2V clip (that is ZeroScope / a DiT card). Do not expect a .ply world (that is WorldGen).

Score interactive first-person rollouts on WorldModelBench. Per-run visual QA stays outside the catalog.

Running in WorldFoundry

Both variants resolve into WORLDFOUNDRY_CKPT_DIR (HFD aliases or native Hugging Face snapshots) and run in worldfoundry-unified-cu128 (Python 3.11, CUDA 12.8). Weights must already be a complete local directory — the I2V line needs the DiT shards, UMT5, CLIP, and Wan2.1 VAE; 1.5 needs the 5B safetensors, UMT5, and Wan2.2 VAE. The runtime does not download them.