- Rating
- 3
- Confidence
- 2
- Informativeness
- 3
- Presentation
- 1
- Soundness
- 3
Read review
Paper summary
NavTTT introduces episode-specific nonlinear fast-weight memory into vision-language navigation policies and it chooses visual patches based on the navigation context and diversity within each frame, and then it combines them with spatial and task information to update separate memory modules at 6 decoder layers. Besides, it achieves success rates of 66.7% and 63.6% on the unseen validation sets of R2R-CE and RxR-CE, and it achieves SPL scores of 59.4% and 52.7% on them too. The authors also conduct ablation studies on the memory design and update strategies under a separate LoRA setting, which I think helps clarify the role of the memory mechanism. But, the real-world results are less convincing, with only 11 successful navigation trials out of 40, suggesting that there is still considerable room for improvement in practical deployment.
Critical strengths
In my opinion, I think this paper addresses an important problem in vision-language navigation. I think using fast-weight memory to preserve useful visual information is an interesting idea, and the overall design makes sense. Besides, the experimental results are also good, with improvements on both unseen validation sets.
1.The memory design is well motivated. The paper focuses on how to preserve useful visual information from earlier observations when those frames are no longer available in the current context. I think updating memory during navigation and retrieving it later is a reasonable way to solve this problem. This makes the proposed method an effective way to handle long-term visual information in VLN.
2.The experimental results are so good. NavTTT has good performs on on both unseen validation benchmarks and the ablation results are also helpful. I think these results support the effectiveness of the proposed memory mechanism, but I think the gains still need to be verified under the main training setting.
Critical weaknesses
The main concern is whether the gains come from APM itself and whether the added hierarchy is worth its cost.
1.The main comparison is not under the same conditions. NavTTT uses a 8B backbone and additional DAgger data, while the no-memory results come from a different LoRA setting. And Table 1 appears to show that NavTTT uses panoramic input, but Sec. 3.1 describes a different input setting. I think the authors should clarify this. I would like to know how much of the performance improvement comes from APM.
2.The paper does not compare the six independent memory modules with simpler designs, such as shared memory or memory at fewer layers. It also does not report memory update latency or performance across different route lengths. Therefore, I think the benefits of the hierarchical memory design and its efficiency in long-horizon navigation have not been fully evaluated.
Questions for authors
I have a few questions about the experimental settings and ablation studies. I think the answers would help me better understand the contribution of the proposed method and could affect my overall assessment.
1.Table 1 seems to indicate that NavTTT uses both panoramic and single-RGB inputs, but Sec. 3.1 only mentions an egocentric RGB image. Could the authors clarify which input setting is actually used?
2.I want to know how much of the performance improvement comes from APM. Can authors provide to me more experimental results about the ablation experiments,such as experimental results without APM and with a static APM, while keeping all other settings the same as the main model?
3.Why does the method use six independent memory modules? I would also like to see separate ablation studies on navigation relevance scoring and within-frame diversity.
3 comments
Reply to Reviewer EDps
[W2] Performance by Route Length
We group episodes by tertiles of cumulative reference trajectory length, using the same groups for all variants within each benchmark. The cutoffs are about 7.8 and 10.0 m on R2R-CE and 9.5 and 17.7 m on RxR-CE.
Table F. Navigation by reference route length
| Dataset | Group | Episodes | Full NavTTT | No APM | Static APM | Direct LaCT |
|---|---|---|---|---|---|---|
| R2R-CE | Short | 615 | 74.96 / 65.89 | 71.54 / 63.69 | 74.47 / 64.39 | 73.66 / 63.15 |
| R2R-CE | Medium | 612 | 71.08 / 63.32 | 67.65 / 60.14 | 71.57 / 62.08 | 68.63 / 61.49 |
| R2R-CE | Long | 612 | 53.92 / 48.84 | 47.88 / 45.74 | 43.95 / 43.89 | 47.55 / 44.53 |
| RxR-CE | Short | 1,224 | 79.33 / 70.34 | 77.78 / 70.53 | 78.43 / 70.81 | 78.84 / 69.44 |
| RxR-CE | Medium | 1,224 | 64.95 / 51.25 | 63.89 / 55.60 | 61.52 / 52.58 | 62.09 / 53.71 |
| RxR-CE | Long | 1,221 | 46.44 / 36.47 | 38.82 / 32.43 | 43.98 / 34.21 | 46.03 / 37.91 |
*Entries are SR / SPL (%) for Qwen3-VL-8B.
Full NavTTT’s SR gain over no APM is largest on long routes in both benchmarks. On long R2R-CE routes, it improves SR and SPL over static APM by 9.97 and 4.95 points, respectively. This group accounts for all 61 net additional successes over static APM. On RxR-CE, the SR gains over static APM are 3.43 points on medium routes and 2.46 points on long routes.
NavTTT brings instruction-conditioned writing, spatial encoding, and retrieval at multiple decoder depths to fast-weight memory for navigation. It stores relevant, diverse visual cues with their spatial and task context, giving the decoder access to accumulated history during later decisions. Under matched training, NavTTT achieves higher SR and lower NE than both the no-APM baseline and direct LaCT on both benchmarks with each tested backbone. With Qwen3-VL-8B, its SR gains over no APM are largest on long routes in both benchmarks.
Reply to Reviewer EDps
Dear Reviewer EDps,
Thank you for your careful review. Your comments helped us clarify the input setting and test APM under the main training protocol. In our response, we explain the single-camera RGB and relative-pose inputs, report matched comparisons with no APM and static APM, and examine how memory layout, token selection, and online updates affect navigation across route lengths.
If you have had a chance to review our response, could you let us know whether any concerns remain? A brief reply before the discussion closes would give us time to address any remaining questions promptly.
Best regards,
The authors
Reply to Reviewer EDps
We sincerely thank the reviewer for your careful reading and positive assessment of our motivation and results. To address your presentation feedback, we have thoroughly polished the manuscript to ensure complete clarity and consistency.
[W1 & Q1] Observation Inputs
Thank you for raising this point. NavTTT uses a single forward-facing egocentric RGB camera for all visual observations. Each decision uses the current image and up to seven earlier frames sampled from that same camera, along with episode-relative planar position and heading. In the NavTTT row of Table 1, the two checkmarks align with S.RGB (single RGB stream) and Odo. (relative pose). The Pano. entry is blank because the evaluation uses a non-panoramic view. We will make this explicit in the table caption.
[W1 & Q2] APM Under the Main Training Protocol
We trained the no-APM baseline, direct LaCT adaptation, and full NavTTT under the main joint-training protocol. Within each backbone, we matched initialization, observation inputs, training data including DAgger, and optimization budget. Static APM uses the full checkpoint with its learned initial fast state held fixed at evaluation.
On R2R-CE with Qwen3-VL-8B, full NavTTT improves SR and SPL over the no-APM baseline by 4.3 and 2.9 percentage points. Oracle success rises from 68.7% to 73.1%, indicating that more trajectories reach the goal neighborhood. With the checkpoint held fixed, online updates increase successful episodes from 1,165 to 1,226 out of 1,839, a gain of 3.32 SR points, and improve SPL by 2.6 points. Full NavTTT also improves both metrics over static APM in the other three settings.
Table A. Controlled memory ablations on Val-Unseen
[W2 & Q3] Memory Layout and Token Selection
We place APM branches at the ends of equal segments of the 36-layer decoder. The one-, three-, and six-branch layouts use zero-based indices {35}, {11, 23, 35}, and {5, 11, 17, 23, 29, 35}, respectively. The shared layout ties corresponding fast states across the same six layers. All layouts use matched training and writing settings with online updates enabled.
At equal fast-state storage, six shared branches improve SR and SPL by 0.6 percentage points each over the last-layer branch. We chose six independent branches for their highest observed SR (66.7%), with comparable SPL and 2.19 ms higher latency per decision than six shared branches.
Table B. Memory configurations on R2R-CE Val-Unseen
At a fixed write budget, relevance and diversity alone improve SR over random selection by 1.3 and 0.7 points on R2R-CE and 2.2 and 1.3 points on RxR-CE, respectively. Combining them yields the highest SR and SPL on both benchmarks.
Table C. Visual token selection on Val-Unseen
[W2] Inference Cost
We profiled all variants on one RTX 5090 D v2 using the same 128 R2R-CE Val-Unseen inputs, batch size 1, and four generated tokens per decision. Writing takes 14.28 ms per decision. Full NavTTT’s total decision latency is 13.13 ms (4.12%) higher than that of the profiled static configuration.
Table E. Inference cost on fixed R2R-CE inputs