- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
TRON combines an editable Gaussian scene with a neural renderer. After a change to the scene, a ray tracer produces a PBR image and an irradiance image. The neural renderer uses both to improve the final appearance. The paper trains this model on synthetic and real data, evaluates relighting quality and speed, and shows examples of lighting, material, and object edits.
Critical strengths
Combining Gaussian ray tracing with neural rendering is useful. The scene can be edited directly, and the irradiance input gives the neural renderer information about shadows.
The examples show clear improvements in long shadows and fine shadow details. The ablations of training stages and rendering inputs also help explain the method.
Critical weaknesses
Table 2 only evaluates the phase-1 model. The final model is used in the visual results, but its errors on this benchmark are not reported.
The reported 1.6 FPS is for single-frame rendering, while the final videos use offline processing of five frames. The cost of this mode is unclear.
The real-scene evaluation mainly measures visual quality. It does not directly show how accurately the output follows the requested lighting and material changes.
Questions for authors
Could you report Table 2 results for the final model, including errors in shadow regions?
What are the FPS and latency of the five-frame mode at the same resolution and on the same GPU?
Could you add a controlled test showing how well the output follows changes in light direction or material roughness?
2 comments
Thank you for your rich additional experiments for my comment and the other reviewers comment, which has illuminates most of my concerns. The clarification of my question 1 is plausible. Aditionally, the experiment comparing [1]hu and makes sense to me and explains to some extent why TRON get such good performance. Also, I am convinced by the speed now cause 7-15fps is a decent rate while the former one is a bit doudbful.
As considered by above reasons, I raise my score to 3 while conserving my confidence.
Q1. Could you report Table 2 results for the final model, including errors in shadow regions?
Thank you. We've come up with a way to compare shadows and highlights through estimated irradiance (Fig. 7, Tb. 3).
We did not add the RGB PSNR of the final model as it is not informative: after the domain shift occurs, the renderer tunes to realism at the expense of rendering exact synthetic objects (Figure 13). This is mentioned directly in the paper, line 421: "we deliberately measure the neural renderer immediately post phase 1, as afterwards we adapt it to the real domain (§4.2), which is our target setting".
Q2. What are the FPS and latency of the five-frame mode at the same resolution and on the same GPU?
Our paper presents an unoptimized neural renderer variant, which directly benefits from speed up techniques from the community. On an A6000, for example, with a drop-in replacement of an efficient VAE [1] and DLSS denoiser [2] (allows us to lower the shadow ray sample count), our neural renderer can process 5-frame chunks at 4.76 FPS (0.47 FPS reported in the paper), and 463ms first-frame latency (3.18s reported in the paper). Interactive mode runs at 7 FPS and 140ms first frame latency. Performance of both modes is doubled on L40S GPU with fp8 support.
Nothing needs to be retrained, and we happily included these speedups in our final revision, noting these are not our main contribution (Table 9 and Appendix G).
Note that the single step nature of our method makes it amenable to such optimizations, as for our unoptimized implementation 85% of the latency is spent on the VAE. Our pipeline processes each 5-frame chunk with a single forward pass, whereas the bidirectional generative baselines (DiffusionRenderer, UniRelight) process the entire video at once, using multiple denoising steps, making the DiT a bottleneck, rather than the VAE.
[1] TAEHV: Tiny AutoEncoder for Hunyuan Video, Boer Bohan 2025
[2] DLSS 4: Transforming Real-Time Graphics with AI, NVIDIA 2025
Q3. Could you add a controlled test showing how well the output follows changes in light direction or material roughness?
We added 2 qualitative figures showing a sweep of the light direction, and material editing. See Fig. 8 and Fig. 9.
Changes due to comments: