VoT
Yugay 2025 · Paper
One-line summary — Visual Odometry with Transformers (retitled FVO, “Fast Visual Odometry with Transformers”): formulates monocular VO as direct relative pose regression with a high-capacity time–space Transformer plus confidence-weighted aggregation, replacing hybrid network + bundle-adjustment pipelines entirely.
Problem
Hybrid pipelines that combine deep networks with classical optimization dominate visual odometry: neural predictions plus bundle adjustment yield highly accurate trajectories. But these hybrids fall short of pure end-to-end approaches in speed and capability — they rely on massive, frozen, pre-trained 3D backbones that were trained scale-ambiguous, so the pipeline “essentially inherits this limitation and, by design, fails to estimate absolute scale”; and their slow optimization and post-processing steps bottleneck inference speed. Bundle-adjustment-based methods also typically assume known camera calibration. FVO asks: what if we drop the post-processing altogether?
Method & architecture
Pipeline: overlapping windows of frames → frozen encoder → time–space Transformer decoder → per-pair relative poses + confidences → confidence-weighted trajectory fusion. No bundle adjustment, no camera intrinsics, no test-time optimization.
- Encoder: a frozen 300M-parameter CroCo ViT trained within the DUSt3R framework. Each image is split into patches (, ), giving features with sinusoidal positional encodings.
- Time–space decoder: blocks (200M parameters), each applying multi-head temporal attention (same spatial location across frames), then spatial attention (within each frame), then an MLP — a factorized alternative to full attention (163 vs 380 GFLOPs). Learnable camera embeddings are concatenated, , and participate only in the spatial attention (injecting them into temporal attention degrades accuracy).
- Pose head: for each consecutive pair , a single linear projection of the camera embedding outputs a 14-dim vector: raw rotation matrix , translation , and confidences . The rotation is projected onto the manifold via the orthogonal Procrustes problem, solved by SVD:
- Uncertainty-aware loss: geodesic rotation error and L1 translation error are combined heteroscedastically,
so confidence is learned self-supervised from pose labels alone — no depth or correspondence supervision. Translations are de-normalized with training-set statistics, giving metric trajectories.
- Confidence-aware inference: the video is split into overlapping windows , so each relative pose is predicted times. Confidences become normalized weights ; rotations are fused via the weighted Fréchet mean on , , translations by weighted average, and the trajectory by composition .
- Training: 8 input views at 224×224, AdamW, 250 epochs, 5 days on 12 H100 GPUs; trained on ARKitScenes, ScanNet, 7-Scenes, TartanAir, and KITTI.
Results
Evaluated with unaligned and aligned ATE (RMSE, meters) — unaligned matters because real deployments have no ground truth to align against:
- FVO: ARKit 0.54 / 0.26, ScanNet 0.34 / 0.16, KITTI 50.31 / 8.47, TUM (zero-shot for all methods) 0.47 / 0.19 — best or second-best across the board.
- Baselines: MASt3R-SLAM-VO 0.60 / 0.28 (ARKit), 0.99 / 0.22 (ScanNet), fails on KITTI; DPVO 5.48 / 0.49 (ARKit), 194.55 / 9.74 (KITTI) — accurate when aligned but poor at absolute scale; VGGT 2.94 / 2.26 (ARKit); CUT3R 2.42 / 0.67 (ARKit); large 3D models drift badly over long sequences.
- Speed: almost 2× faster than the fastest baseline on an RTX 3090 (VGGT run with only its camera head for fairness).
- Ablations: FVO’s heteroscedastic confidence gives 1.04 ATE vs 1.33 with DUSt3R-style per-pixel confidence and 1.21 with none; SO(3) projection beats quaternion (1.19), 6D (1.12), and Plücker-ray (1.17) rotation representations; the CroCoV2-DUSt3R backbone (1.04) far outperforms DINOv2-VGGT (1.31). ATE decreases consistently with more training data and more decoder layers.
Why it matters for SLAM
VoT/FVO is part of the broader migration of geometric estimation onto Transformer architectures — the same trend that produced LoFTR for matching and VGGT for full multi-view geometry. Its value for a SLAM learner is as a clean case study of the end-to-end extreme of the design space: what you gain by deleting the optimizer (speed, metric scale, no calibration) and what you give up (the interpretable geometric backbone, robustness in dynamic scenes). Note the naming: the arXiv work first appeared as “VoT” and was later retitled FVO.
Related
- DROID-SLAM — CNN + optimization learned SLAM baseline
- DPVO — sparse patch-based learned VO baseline
- VGGT — full feed-forward Transformer geometry in the same trend
- LoFTR — Transformer-based detector-free matching
- TartanVO — earlier generalizable learned VO that kept the geometry-style outputs