SceneAE: Scene Generation and Reconstruction in Queryable 3D-Anchored Latent Space

cs.CV cs.AI Shuofeng Sun, Wenzhao Zheng, Yunpeng Zhang, Yi Wu, Linqing Zhao, Haibin Yan · Oct 14, 2026
Local to this browser
What it does
SceneAE proposes a sparse 3D-anchored latent representation for scene reconstruction and camera-controllable generation. Instead of viewpoint-aligned video latents, each latent couples an explicit 3D point with an implicit feature,...
Why it matters
Instead of viewpoint-aligned video latents, each latent couples an explicit 3D point with an implicit feature, enabling queryable rendering from arbitrary cameras. A two-stage diffusion model decouples geometry generation from content...
Main concern
The paper presents a compelling idea with solid empirical results, but some claims are overstated and comparisons are partially uneven. The core technical contributions — explicit 3D anchor positions and a geometry-content decoupled...
Community signal
0
0 up · 0 down
Sign in to vote with arrows
AI Review AI reviewed
Plain-language introduction

SceneAE proposes a sparse 3D-anchored latent representation for scene reconstruction and camera-controllable generation. Instead of viewpoint-aligned video latents, each latent couples an explicit 3D point with an implicit feature, enabling queryable rendering from arbitrary cameras. A two-stage diffusion model decouples geometry generation from content synthesis, improving camera control and cutting computational cost roughly in half compared with dense-grid baselines.

Critical review
Verdict
Bottom line

The paper presents a compelling idea with solid empirical results, but some claims are overstated and comparisons are partially uneven. The core technical contributions — explicit 3D anchor positions and a geometry-content decoupled diffusion transformer — are well-motivated and improve multi-view consistency and trajectory following. However, the reconstruction fidelity remains below dense video-VAE baselines, and the method’s reliance on static-scene assumptions limits applicability.

“Unlike conventional video-VAE latents that describe how a scene appears from particular viewpoints, our representation directly describes the scene itself, making it naturally applicable to both reconstruction and generation.”
SceneAE, Abstract · Abstract
“Compared with conventional video VAEs, our representation provides lower reconstruction sharpness.”
SceneAE, Appendix C.2 · Appendix C.2
What holds up

The strongest aspects are the design of the latent point cloud and the splat-based decoder, which together enable efficient queryable reconstruction from arbitrary viewpoints. The ablation in Table 9 shows that decoupling geometry and content yields clear gains, and the paper demonstrates favorable efficiency: with only $N=3000$ latents, GFLOPs and latency are roughly half those of SceneTok.

“The decoupled design performs best, showing that explicit geometric priors facilitate content synthesis.”
SceneAE, Section 4.4 · Section 4.4
“Compared with SceneTok at the same resolution, GFLOPs drop from 27,096 to 13,171, and batch latency decreases from 4,020 ms to 1,623 ms.”
SceneAE, Section 4.3 · Section 4.3
Main concerns

Key flaws include lower reconstruction fidelity compared to dense latents, which the authors acknowledge in Appendix C.2 but downplay in the main text. The evaluation of geometry generation uses different ground-truth sources for different methods — VGGT for Gen3R and DA3 for the authors’ method and GLD — making the comparison unfair and potentially inflating the reported Chamfer-distance gap. The method assumes static scenes, so the generation task is essentially static-scene extrapolation rather than true dynamic world modeling. Additionally, the two-stage training and inference pipelines increase complexity, yet the paper does not report end-to-end training time or sensitivity to the fixed latent budget.

“The evaluation GT for Gen3R is provided by VGGT (Wang et al., 2025), while the evaluation GT for ours and GLD is provided by DA3 (Lin et al., 2025). This avoids the influence of performance differences among geometry foundation models.”
SceneAE, Table 2 caption · Table 2 caption
“Our current representation assumes that scene content can be anchored to persistent locations in a shared 3D coordinate system. This assumption is effective for static scenes but becomes restrictive for moving or deformable objects.”
SceneAE, Appendix C.2 · Appendix C.2
Evidence and comparison

The evidence broadly supports the central claims about geometry consistency and camera controllability, but the comparison geometry is uneven. Metrics in Table 2 are computed against different depth estimators per method, preventing a fair ranking. The appearance metrics in Table 1 show competitive PSNR and SSIM, yet the gap over GLD is small. Novel-view synthesis beats SceneTok and LVSM but still trails dense methods that do not support novel-view rendering.

“We present SceneTok, a novel tokenizer for encoding view sets of scenes into a compressed and diffusable set of unstructured tokens.”
“SceneTok compresses the scene into compact unstructured 1D tokens and supports multi-view decoding, thereby alleviating the fixed-viewpoint limitation. However, its tokens lack explicit spatial localization, and the model must learn the scene region corresponding to each token through dense token-pixel interaction, which increases optimization difficulty as well as encoding and decoding costs.”
SceneAE, Section 1 · Section 1
Reproducibility

Training details are relatively thorough: DA3-Base features, $N=3000$ latents, $518 \times 376$ resolution, AdamW with learning rate $5 \times 10^{-5}$, batch size $40$, and $100$k iterations on 8 A800 GPUs. However, no code, data splits, or pretrained weights are released. The reliance on a frozen DA3 model and specific ray tokenization means reproduction requires exact feature-extraction pipelines that are not fully specified. The jitter, dual-path deformable attention, and two-stage designs introduce many hyperparameters that are only partly documented.

“The training optimizer hyperparameters follow GLD, using AdamW with a learning rate of 5e-5 and a batch size of 40. SceneLatent is trained for 100k iterations on 8 A800 GPUs.”
SceneAE, Section 4.1 · Section 4.1
“Since camera-controllable content generation relies on 3D RoPE, relatively accurate 3D positions are required. Therefore, we adopt a two-stage training paradigm: the Point DiT is trained first, and only then is the Content DiT trained, rather than training them jointly.”
SceneAE, Section 3.2 · Section 3.2
Abstract

Recent video world models have increasingly adopted 3D memory mechanisms to integrate historical observations into a lightweight and persistent scene representation. This naturally raises a complementary question: if 3D representations can serve as an effective mechanism for memorizing observed scenes, can they also be directly used as the latent space for reconstructing and generating scenes? Motivated by this idea, we represent a scene as a compact and unstructured 3D-anchored latent space (\textbf{SceneAE}). Each latent combines an explicit 3D position with an implicit content feature and is spatially grounded to describe its local scene region, forming a sparse latent point cloud. Unlike conventional video-VAE latents that describe how a scene appears from particular viewpoints, our representation directly describes the scene itself, making it naturally applicable to both reconstruction and generation. For reconstruction, once the scene has been generated, our persistent 3D representation can be projected and decoded into RGB-D observations by different target cameras, without the need to regenerate a video for each new camera trajectory. For generation, we leverage the geometry-content separation to first generate camera-controlled 3D geometry and then synthesize content conditioned on it, reducing camera-appearance entanglement and improving camera controllability. Experiments show that this 3D latent achieves superior generation quality, computational cost, and camera controllability.

Challenge the Review

Pick a starting point or write your own. Challenges run in the background, so you can keep reading while the AI investigates.

No challenges yet. Disagree with the review? Ask the AI to revisit a specific claim.