text stringclasses 1
value |
|---|
probe2 |
Magpie Dataset Lite
Paper: Magpie: Real-Time World Renderer for Interactive Games
Project Page: https://zhanxy.xyz/Magpie-website
Magpie Dataset Lite is a publicly released subset of the Magpie interactive game rendering dataset (arXiv:2608.27168). Magpie is a real-time generative world-rendering system that separates gameplay execution in a game engine from visual synthesis in a render server. This lite release provides 561 gameplay trajectories with a combined render.mp4 duration of 105 hours, covering 20 scenes.
Each sample includes time-synchronized high-fidelity render and white-box video streams, together with structured interaction metadata recorded during capture.
Dataset Summary
| Item | Value |
|---|---|
| Paper | arXiv:2608.27168 |
| Project page | Magpie Website |
| Relation to full Magpie dataset | Partial release (lite subset) |
| Number of trajectories | 561 |
Total duration (render.mp4) |
105 hours |
| Number of scenes | 20 |
| Video streams per sample | 2 (render.mp4, white_box.mp4) |
| Metadata per sample | 1 JSON file |
| Capture setting | Unreal Engine, human-operated gameplay |
| Original per-stream resolution | 1920 Γ 1080 |
| Original frame rate | 60 FPS |
What Is Magpie?
Magpie learns to convert engine-produced white-box observations into photorealistic or stylized renderings while gameplay rules and state remain in the game engine. During data collection, operators play controllable Unreal Engine scenes naturallyβexploring, interacting, changing viewpoint, idling, and transitioning between behaviorsβrather than executing isolated scripted actions.
Each trajectory therefore provides paired supervision for structure-to-appearance video generation:
render.mp4: high-fidelity target streamwhite_box.mp4: synchronized white-box stream preserving layout, geometry, occlusion, and principal motion while omitting final textures, materials, and complex lighting
For more details, see the Magpie project page and the paper: Magpie: Real-Time World Renderer for Interactive Games.
Directory Structure
Each trajectory is stored under sceneXX/playerYY/:
magpie_lite_dataset/
βββ scene00/
β βββ echo/
β β βββ render.mp4
β β βββ white_box.mp4
β β βββ scene00_echo.json
β βββ player1/
β β βββ render.mp4
β β βββ white_box.mp4
β β βββ scene00_player1.json
β βββ ...
βββ scene03/
βββ scene04/
β βββ player9_part1/
β βββ player9_part2/
β βββ ...
βββ scene28/
Naming conventions
- Scene folders use numeric IDs only, e.g.
scene00,scene16,scene28. - Player folders identify the operator/session, e.g.
echo,kellan,player1,player15. - Some source captures contain multiple nested takes for the same logical player. Those are exported as separate trajectories with suffixes such as
player9_part1andplayer9_part2. - Metadata files are named
{scene}_{player}.json, e.g.scene00_echo.json.
File Descriptions
render.mp4
High-fidelity gameplay video. It provides the visual target stream used for training and evaluation of generative rendering.
white_box.mp4
Synchronized white-box gameplay video from the same timestamp and viewpoint as render.mp4. It preserves scene layout, collision-relevant structure, principal silhouettes, and visible state changes while removing final appearance details.
Both videos in a sample are frame-aligned and should be consumed as a pair.
{scene}_{player}.json
Structured interaction metadata copied from the original capture session. It is time-aligned with the paired videos and typically contains:
key_events: keyboard input events with timestamps and pressed/released statesue_events: Unreal Engine camera / viewpoint records with timestamps, including fields such as location, rotation, and field of view
These fields preserve the provenance of visual changes and support filtering, analysis, and future conditioning experiments. In the current Magpie training pipeline described in the paper, camera pose is used for visual-history retrieval, while operator input and event records are retained as synchronized metadata rather than direct training targets.
Scenes Included in Lite
This release includes the following 20 scenes:
scene00, scene03, scene04, scene06, scene08, scene09, scene11, scene12, scene13, scene14, scene16, scene17, scene19, scene20, scene21, scene24, scene25, scene26, scene27, scene28
Approximate duration by scene (render.mp4)
| Scene | Duration |
|---|---|
| scene00 | 10:12:18 |
| scene03 | 4:59:01 |
| scene04 | 12:38:41 |
| scene06 | 6:36:53 |
| scene08 | 5:07:10 |
| scene09 | 2:11:44 |
| scene11 | 5:44:45 |
| scene12 | 5:37:31 |
| scene13 | 4:50:18 |
| scene14 | 3:35:42 |
| scene16 | 3:58:13 |
| scene17 | 5:23:38 |
| scene19 | 1:42:07 |
| scene20 | 2:10:13 |
| scene21 | 3:50:49 |
| scene24 | 3:15:35 |
| scene25 | 4:05:23 |
| scene26 | 9:38:41 |
| scene27 | 4:55:55 |
| scene28 | 4:26:03 |
| Total | 105:00:38 |
Intended Uses
This dataset is intended for research on:
- white-box-conditioned video generation
- game / interactive world rendering
- structure-to-appearance synthesis
- long-horizon human gameplay video modeling
- multimodal analysis of synchronized render + control metadata
Usage Example
from pathlib import Path
import json
root = Path("magpie_lite_dataset")
sample = root / "scene00" / "echo"
render = sample / "render.mp4"
white_box = sample / "white_box.mp4"
meta = sample / "scene00_echo.json"
with meta.open("r", encoding="utf-8") as f:
events = json.load(f)
print(render.exists(), white_box.exists())
print("key events:", len(events.get("key_events", [])))
print("camera events:", len(events.get("ue_events", [])))
Citation
If you use this dataset, please cite the Magpie paper:
@article{zhan2026magpie,
title={Magpie: Real-Time World Renderer for Interactive Games},
author={Zhan, Xiaoyu and Wang, Xinyu and Zhang, Xiaohong and Zhu, Huanjie and Sun, Tengjiao and Fang, Pengcheng and Yu, Jiaxing and Guo, Yanwen and Fu, Dongjie},
journal={arXiv preprint arXiv:2608.27168},
year={2026},
url={https://arxiv.org/abs/2608.27168}
}
License
This dataset is released under the Apache License 2.0.
- Downloads last month
- -