VGGT-SLAM 2.0
Maggio 2026 · Paper
One-line summary — The successor to VGGT-SLAM: a keyframe-level factor graph that removes 15-DoF drift and planar degeneracy, training-free loop-closure verification read out of VGGT’s attention layers, and real-time operation onboard a Jetson Thor.
Problem
VGGT-SLAM solved the uncalibrated submap-alignment problem by optimizing 15-DoF homographies on SL(4), but that solution carries its own costs: the high-dimensional alignment introduces rapid drift between loop closures that can severely warp the scene, and solving for the full homography is degenerate in planar scenes (a camera facing a wall or floor), causing divergence. Its factor graph also only estimated per-submap homographies, so keyframe-level rotation/translation errors from VGGT were handled sub-optimally, and image retrieval for loop closure trusted an external network (SALAD) without any verification. VGGT-SLAM 2.0 redesigns the backend to remove these failure modes while still respecting the reconstruction ambiguity of VGGT under unknown intrinsics — and makes the whole system run online on a robot.
Method & architecture
- Setup: each submap comes from one VGGT pass over keyframes, giving calibrations , poses , depths , and confidences ; points are back-projected per camera frame as using and . Consecutive submaps share one overlapping frame. The general alignment object is the full homography with 15 DoF: 3 translation , 3 rotation , 1 scale , 5 affine (calibration ), 3 projective ().
- New factor graph — keyframes as nodes: every keyframe is an node. Intra edges connect keyframes inside a submap and carry only components, taken directly from VGGT’s poses: — projective distortion is consistent within a submap, and these edges let optimization correct VGGT’s own pose drift. Inter edges connect the two estimates of an overlapping frame and carry only calibration and scale: enforcing that both submaps’ estimates of the same physical camera agree in pose and calibration (even if VGGT’s calibration guess is wrong, it must be identical). This restriction to SL(4) subgroups removes the 15-DoF drift and the planar degeneracy. The scale is the median ratio of corresponding 3D point distances after warping the two point clouds to a common calibration — the only place raw VGGT points are used.
- Loop-closure verification from VGGT’s attention, for free: layer 22 of VGGT exhibits a “spotlight” attention pattern between corresponding regions of two images (absent in layers 21/23, present even on textureless walls). A match score is computed as where , are query/key tokens (head-averaged) of the retrieved and query image. SALAD candidates are only accepted when passes a threshold, which allows relaxing the SALAD threshold (0.80 → 0.95) to harvest more loop closures while rejecting false positives. Loop closures are handled as two-frame mini-submaps passed to VGGT, connected by an inter edge.
- Global optimization and map recovery: the graph is optimized on the SL(4) manifold with GTSAM (the SL(4) solver has been upstreamed into GTSAM). Projection matrices are recovered as and decomposed into global poses; global points follow from applying .
Results
Constant parameters across all experiments (50 px min disparity, 25% confidence threshold, SALAD 0.95, 0.85).
- TUM RGB-D (uncalibrated, submaps of 32): best average ATE RMSE of 0.041 m — about 23% lower than VGGT-SLAM SL(4) (0.053 m) and 22% lower than ViSTA-SLAM (0.052 m); MASt3R-SLAM* 0.060 m. On the planar
floorscene: 0.102 m vs VGGT-SLAM’s 0.141 m. - Loop-closure verification: on the Clio datasets, verification raises accepted loop closures from 2 → 5 (Cubicle) and 0 → 9 (Apartment), and turns a diverging Office run (false positives from lookalike desk cubicles) into 4 correct closures with zero false positives. On LaMAR HGE, Recall@1 improves for SALAD 88.45 → 90.13 and NetVLAD 85.92 → 89.08.
- Runtime: about 8.4 FPS with 16-frame submaps on an RTX 3090 (6.3 FPS with open-set CLIP embeddings); per-submap time is dominated by VGGT inference (1248 ms). On the same machine, MASt3R-SLAM runs 7.2 FPS and VGGT-SLAM 6.9 FPS. Running fully onboard a Jetson Thor on a Jackal ground robot with a RealSense D455: 3.5 FPS with 4-frame submaps, live.
- Open-set object detection: Perception Encoder CLIP embeddings per keyframe + SAM 3 segmentation give 3D oriented bounding boxes from text queries in about 0.36 s per query (RTX 3090).
- Scale: reconstructs a 4,200-square-foot barn (34 submaps) and a KITTI driving sequence (44 submaps) on which VGGT-SLAM diverges — both larger than the biggest scene in the original paper (22 submaps).
Why it matters for SLAM
The first wave of foundation-model SLAM systems (MASt3R-SLAM, VGGT-SLAM) proved the concept but ran offline or below sensor rate. VGGT-SLAM 2.0 closes the remaining gap — dense feed-forward reconstruction that runs online on embedded robot hardware — which is the actual requirement for robotics and AR. Its attention-layer analysis is also a notable pattern: extracting loop-closure verification from a frozen foundation model without any training hints at how much latent SLAM machinery these models already contain. Because nothing is trained, faster or better VGGT variants can be dropped in directly.
Related
- VGGT-SLAM — the original system this version supersedes
- VGGT — the underlying feed-forward geometry model
- MASt3R-SLAM — contemporary foundation-model SLAM
- DROID-SLAM — earlier learned SLAM baseline in this lineage
- Visual Place Recognition (VPR) — the retrieval problem VGGT’s attention verifies for free
- Clio — the task-driven scene-graph datasets used for loop-closure evaluation