RelationVGGT: Visual Geometry Transformers for 3D Spatial Relation Segmentation

cs.CV cs.AI Minsu Kim, Jaesung Choe, Jiwoo Lee, Yu-Chiang Frank Wang, Seon Joo Kim · Oct 1, 2026
Local to this browser
What it does
RelationVGGT tackles 3D spatial relation segmentation: given multi-view images, a reference subject mask, and a text relation (e. g.
Why it matters
The core idea is to replace expensive volumetric relation search with per-pixel relation prediction by fusing semantic DINOv2 features with geometry-aware Pi3 tokens through a subject-conditioned relation transformer. This matters because...
Main concern
RelationVGGT advances feed-forward 3D relational reasoning, achieving an average mIoU of 0. 382 and mAcc of 0.
Community signal
0
0 up · 0 down
Sign in to vote with arrows
AI Review AI reviewed
Plain-language introduction

RelationVGGT tackles 3D spatial relation segmentation: given multi-view images, a reference subject mask, and a text relation (e.g., "resting on"), it segments the target object across unposed views without per-scene optimization. The core idea is to replace expensive volumetric relation search with per-pixel relation prediction by fusing semantic DINOv2 features with geometry-aware Pi3 tokens through a subject-conditioned relation transformer. This matters because it moves holistic scene understanding beyond isolated object recognition toward reasoning about how objects are spatially arranged, a capability critical for embodied agents and spatial QA.

Critical review
Verdict
Bottom line

RelationVGGT advances feed-forward 3D relational reasoning, achieving an average mIoU of 0.382 and mAcc of 0.549 across three small benchmarks, substantially exceeding RelationField while running in milliseconds rather than hours. However, the evaluation covers only 119 relations across 14 scenes, and the training annotations are noisy, which tempers the strength of the conclusions despite the solid architectural design.

“Our method achieves the highest average mIoU of 0.382 and mAcc of 0.549, outperforming the strongest baseline, RelationField, by substantial margins in both mIoU and mAcc.”
RelationVGGT paper · Table 1 / Section 4.1
“On an NVIDIA L40S, our method requires 26 ms for inference in the timing setup used in our evaluation, whereas RelationField requires 288 s for a relation query and more than 3 hours of per-scene optimization.”
RelationVGGT paper · Table 9 / Appendix B.2
What holds up

The reformulation of volumetric relation search as per-pixel prediction is well motivated, and the architecture’s fusion of 2D semantics with 3D geometry priors is validated by ablations: dropping either stream degrades performance, and the proposed alternating cross- and self-attention outperforms simpler variants. Qualitative results also show encouraging cross-view consistency under large viewpoint changes.

“Replacing our multi-query sigmoid focal loss with a single-label sigmoid focal loss leads to a notable performance drop, confirming that spatial relations are inherently many-to-one.”
RelationVGGT paper · Section 4.3 / Table 3
“despite not employing any explicit 3D representation such as radiance fields or 3D Gaussian splatting, our predictions remain visually consistent across viewpoints with substantial changes in camera pose.”
RelationVGGT paper · Section 4.2
Main concerns

Primary concerns are the tiny evaluation scale and the noisy automated supervision. The entire benchmark comprises only 119 relations (40 ScanNet++, 31 LERF, 48 Replica), and the auto-generated training labels start from 36.4% precision before filtering, reaching only 67.2% afterward with substantial correct proposals discarded; about a third of retained training relations are still estimated to be wrong.

Absolute performance remains modest, especially on the cluttered LERF split where mIoU is just 0.254, and the method’s reliance on an accurately specified subject mask means automatic grounding pipelines (e.g., GroundingDINO + SAM2) incur meaningful degradation. Generalization beyond indoor ScanNet++ is also unexplored.

“Filtering increases proposal precision from 36.4% to 67.2% and removes 92.0% of proposals judged incorrect. The retained set remains noisy and intentionally sacrifices coverage for reliability.”
RelationVGGT paper · Table 8 / Appendix A.2.3
“For ScanNet++, we use the 26 samples proposed by RelationField and add 14 newly annotated samples. For LERF and Replica, we annotate 31 relations from 3 scenes and 48 relations from 8 scenes, respectively.”
RelationVGGT paper · Section 4, Benchmarks
Evidence and comparison

The quantitative trends support the claim that feed-forward inference can outperform per-scene optimization, but several comparisons are mismatched. Video foundation models are evaluated on frame sequences rather than true multi-view geometry, and referring-segmentation baselines receive text-only queries, making them harder comparisons; the authors acknowledge these are not matched-input ablations. Ablations are further limited to the small ScanNet++ split of 40 queries, leaving open how robust the design choices are at scale.

“UniPixel achieves competitive mIoU on the small-baseline setting, but performance generally degrades as the baseline widens, since larger viewpoint changes break the temporal continuity assumptions underlying video representations. In contrast, our method maintains stable performance across all baseline ranges.”
RelationVGGT paper · Table 2 / Section 4.1
“This comparison is not a matched-input ablation, since the methods also differ in query form, pretraining data, and test-scene optimization; nevertheless, the results highlight the practical advantage of separating subject grounding from relation-conditioned target localization.”
RelationVGGT paper · Appendix C.1
Reproducibility

Training hyperparameters are reported in reasonable detail—200 epochs on 4 H200 GPUs, AdamW at $1\times 10^{-4}$, ViT-S transformer configuration, and the exact VLM/LLM prompts are provided—but the authors note that code and data will be released later, so independent reproduction is currently blocked. Some filtering thresholds in the annotation pipeline are described qualitatively (e.g., bounding-box overlap and centroid distance) without exact values, which would complicate replication of the training set.

“We will provide open-source codes.”
RelationVGGT paper · NeurIPS Paper Checklist, Q4
“Training is performed for 200 epochs on 4 NVIDIA H200 GPUs with a per-GPU batch size of 7. We use AdamW with a learning rate of $1\times 10^{-4}$ and cosine learning-rate decay.”
RelationVGGT paper · Section 4, Implementation details
Abstract

Recent advances in 3D reconstruction have progressed from per-scene optimization to feed-forward inference, and semantic scene understanding has followed suit -- yet existing methods remain confined to object-centric perception, neglecting spatial relations between objects. We formulate 3D spatial relation segmentation in a feed-forward, pose-free multi-view setting: given a visually specified subject and a relational text query, the model segments the target across views without receiving its category name. To this end, we propose RelationVGGT, a novel feed-forward framework that integrates semantic features from a visual foundation model with geometry-aware representations from a 3D geometry foundation model and leverages a relation transformer for subject-conditioned, cross-view relation prediction -- requiring neither per-scene optimization nor known camera poses. We additionally provide a fully automated annotation pipeline built on ScanNet++ with VLMs and LLMs, enabling scalable training data generation for this new task.

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.