- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes a framework for monocular drone navigation that supports point-goal, image-goal, and goal-free settings at a scale of 6x6-30x30 meters in both indoor and outdoor environments. It uses a 3DGS-based simulation platform and jointly trained forward/inverse latent dynamics objectives to learn implicit world representations, while discarding the prediction modules during deployment for efficient action generation. Zero-shot real-world experiments were conducted on a DJI Tello with inference running on an external RTX 3090 GPU at approximately 7 Hz and flight speeds limited to 1 m/s.
Critical strengths
-
The paper proposes a pipeline that leverages 3DGS to reconstruct real-world scenes as training environments, avoiding the need for costly and time-consuming real-world drone deployment. The authors also collect a large-scale dataset consisting of 94 scenes, 94K trajectories, and 32.5M rendered frames, which is a valuable contribution.
-
The paper demonstrates zero-shot transfer to a physical drone empirically without any policy fine-tuning.
Critical weaknesses
-
The paper lists “A policy deployed without the predictor” as its third contribution. While this is a desirable property for real-time UAV deployment, the underlying idea is not entirely new. Prior works such as FutureNav and Fast-WAM have explored training-time world-model supervision without requiring future prediction during inference. In particular, FutureNav also combines forward and inverse dynamics objectives to improve a shared navigation representation while maintaining efficient direct action generation. I acknowledge that FutureNav's discrete action space is not directly applicable to drone control, and adapting this framework to UAV navigation is a meaningful contribution. However, predictor-free deployment alone seems insufficient to establish a major methodological contribution.
-
The paper lists “A world model driven by the intended motion” as its second contribution. The proposed forward and inverse dynamics objectives are reasonable, and I appreciate the authors' shortcut analysis in the Appendix and their efforts to mitigate this issue. However, given the similarities to prior work such as FutureNav, the paper could better clarify what is methodologically distinct about the proposed formulation.
Questions for authors
-
Clarification of the simulation platform and dataset contributions. The proposed platform integrates real-world scene capture, 3DGS reconstruction, mesh/SDF-based collision geometry, and physics simulation to generate navigation demonstrations. Could the authors clarify which aspects of this pipeline represent the main technical contributions beyond integrating existing components? In particular, are there any UAV-specific adaptations to the standard 3DGS reconstruction pipeline, such as improvements in aerial viewpoint handling, geometric consistency, or rendering quality? It would also be helpful to understand how the collected dataset differs from existing aerial navigation datasets in terms of scene diversity, trajectory coverage, and visual/geometric quality.
-
The zero-shot transfer results are encouraging, especially given the differences between reconstructed simulation environments and physical UAV deployment. Could the authors elaborate on which factors they believe are most important for achieving successful transfer despite differences in visual appearance, obstacle geometry, and flight dynamics? Were there any notable failure cases or systematic challenges during real-world deployment? Additionally, could the authors clarify whether any calibration, dynamics matching, or other sim-to-real adaptation was performed beyond the described training protocol?
6 comments
Thank you again for your constructive feedback. We would appreciate it if you could review our rebuttal and, if our responses have addressed your concerns, consider updating your rating. We would be happy to provide further clarification if needed.
Remaining Concerns Regarding the Contributions of (1) the Simulation Platform and (2) Predictor-Free Deployment
Thank you for the rebuttal. I appreciate the solid technical work and the additional experimental results.
I have two remaining concerns regarding the core contributions:
-
3DGS-based simulation platform. The platform could be a valuable engineering and dataset contribution. However, without a systematic comparison with existing UAV simulation or reconstruction-based training platforms, its contribution has not been sufficiently established. Besides, could the authors clarify whether the platform and dataset will be publicly released or made accessible to the research community?
-
Positioning of predictor-free deployment. While the technical motivation is reasonable, I feel that the Introduction somewhat overstates the novelty of predictor-free deployment. Given that similar ideas have been explored in prior work, I would encourage the authors to position it primarily as a practical efficiency advantage rather than a standalone methodological contribution.
Thank you for recognizing the platform and zero-shot flight experiments. Manuscript revisions are highlighted in blue.
W1. Predictor-free deployment. FutureNav [1] and Fast-WAM [2] also avoid future prediction at inference. Fast-WAM retains its video DiT to encode observations for an action expert, while FutureNav retains VGGT spatial fusion. SKYTOPIA removes the auxiliary V-JEPA 2 encoder and both dynamics heads, deploying only the vision-language backbone and flow-matching action head. This saves 59.4% of full-model FLOPs. Table 2 shows improved navigation without increasing deployed policy capacity.
W2. Coupled forward and inverse prediction. FutureNav recovers actions from observed-state features, their difference, and context. Our inverse head instead takes the current state and predicted next state to recover continuous commands. Its gradients pass through the prediction into the forward head and the backbone's action tokens. Forward prediction must therefore both match the observed future and preserve the executed motion.
Our shortcut probe motivates dropping the preceding state with 30% probability so action recovery must use the predicted next state. The forward loss anchors that prediction to the observation, while the inverse loss preserves command information. Objective ablations and geometric probes support this formulation.
We added FutureNav and WorldVLN [3] with matched data, goal guidance, and evaluation. Both use seven-step continuous controls, and FutureNav retains its dynamics losses. SKYTOPIA achieves higher SR/SPL in all three modes (Table 1), with 34.9% fewer FLOPs and 38.6% lower latency per query than adapted FutureNav. It also performs better across route lengths and visual perturbations (Figs. 10–11).
Q1. Platform and dataset contributions. The platform contribution is converting captured scenes into interactive flight tasks with a shared metric basis. Standard 3DGS optimization fits appearance to posed RGB images. LiDAR supplies metric geometry, and the reconstructed mesh supplies a 10 cm SDF. Planning, rendering, clearance-dependent velocity commands, and collision decisions thus refer to the same scene geometry.
When a policy leaves the expert path, the simulator renders its actual camera pose and checks collisions at its new position. This turns the reconstruction into a flight-training environment with feedback beyond recorded routes.
UAV-Flow pairs real pilot trajectories with atomic instructions for fine-grained flight [4]. IndoorUAV builds language-guided trajectories in Habitat indoor scenes [5]. Our collection spans 18 indoor, 48 urban outdoor, and 28 vegetation scenes across 75,657 m², covering rooms, corridors, streets, and woodland within one control interface.
We collect 1,000 routes per scene, yielding 94K trajectories and 32.5M frames. Samples pair RGB images, physical states, and continuous velocity commands, with speed adapted to clearance and curvature. This coverage supports learning visual-motion dynamics and obstacle avoidance under point-goal, image-goal, and goal-free inputs. Appearance and collision geometry come from the same real capture, linking rendering to planning and evaluation.
Q2. Transfer, calibration, and failures. Diverse real-scene reconstructions expose the policy to varied appearance and layouts. The geometric probes and perturbation tests support learning scene structure and motion through dynamics supervision. Simulation and deployment share body-frame velocity and yaw-rate commands, with physical stabilization handled by the drone controller.
Policy weights remain fixed in real flights. Deployment includes velocity-to-command calibration, deadband compensation, coordinate conversion, and inference-delay handling. Translation and yaw are scaled together to preserve their ratio when reducing speed. Training uses ideal velocity tracking.
The main observed failure was overshooting near the goal: the drone failed to see the target and adjust yaw in time, passed the destination, and left the test area. Failures also occurred in dense clutter.
References.
[1] Zhang et al. (2026). FutureNav: Unified World-Action Modeling for Vision-and-Language Navigation. arXiv:2606.30367.
[2] Yuan et al. (2026). Fast-WAM: Do World Action Models Need Test-time Future Imagination? arXiv:2603.16666.
[3] Zhao et al. (2026). WorldVLN: Autoregressive World Action Model for Aerial Vision-Language Navigation. arXiv:2605.15964.
[4] Wang et al. (2026). UAV-Flow Colosseo: A Real-World Benchmark for Flying-on-a-Word UAV Imitation Learning. arXiv:2505.15725.
[5] Liu et al. (2026). IndoorUAV: Benchmarking Vision-Language UAV Navigation in Continuous Indoor Environments. arXiv:2512.19024.