- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes Pace3D for 3D editing. Pace3D first embeds the current 3D object into 3D occupancy, which is labelled as "source". It also use image editing model (didn't tell the specific model used?) and image-to-3D model (TRELLIS-image-large) to get a proxy target occupancy. Then during the sparse structure editing, it continually judges how well is the editing path aligned with the pesudo GT path obtained from the source occupancy latent to the proxy target occupancy latent. If the structure editing falls behind, it will reset the sampling timestep. Such resets can happen multiple times (but less than or equal to 6 times). Overall, Pace3D use longer latency (than Nano3D) as trade-off for more accurate 3D editing results.
Critical strengths
-
Figure 3 clearly shows the motivation of Pace3D: the edited structure can fall behind a GT editing path. I also think checking the structure rather than only checking the timestep is reasonable.
-
Table 2 shows that the editing alignment is improved over related baselines.
-
Table 6's equal-wall-clock comparison with Nano3D shows that the performance gains not 100% comes from longer computation time.
-
Table 4's comparison with "Fixed" shows the benefit of Pace3D's timestep resetting operation.
Critical weaknesses
-
The paper measures unfinished structure for baselines, but not for Pace3D. Section 5.1 counts the unfinished addisions and deletions for baselines, but same comparison after Pace3D is applied is missing. Table 3 and table 4 report the similarity of embeddings, which can not be interpreted as the quality of structure editing. The paper's claim is that baselines finish earlier then ready, while Pace3D makes sure finishing when ready via rewind. But these erperiments is not strong enough to support such claim. Also, the changes outside the editing parts should also be measured, other wise a method may finished with "over-edited" structures, including some changes that we do not want.
-
Eval3DEdit has a total of 100 cases, but in table 8 (the proxy vs GT comparison), only 12 cases were used, making the relibility of the proxy unjustified. Also in paper's main experiments on Eval3DEdit. The authors did not make it clear that those experiments are conducted on all 100 cases or a selected subset from it.
-
In table 3, the controller makes the PC-PC worse, from 0.7604 to 0.7383, though PC-Txt improves, making me more concerned about whether Pace3D has "over-editing" issues.
-
In table 4, which is an important ablation, the paper does not make it clear how random and fixed variants are implemented.
Questions for authors
please see the weaknesses above
5 comments
Rebuttal by Authors [2/4]
3. Assessment of Overall Edit Completion
Across all 100 Eval3DEdit cases, Pace3D achieves a VLM-assessed overall edit completion rate of 71%, compared with 59% for Nano3D† and AnchorFlow. This evaluation includes both structural and appearance edits.
We use gpt-6-sol as the judge. Each case is presented with the editing instruction, source and target images, and six pairs of source and edited renderings from matching cameras spaced 60° apart. The judge identifies the requested change before returning a yes/no decision. A case is counted as complete only when all requested changes are fulfilled. For structural edits, added parts must appear as recognizable geometry at the intended locations, and parts requested for removal must be absent from the provided views. Recoloring alone does not count as completing a structural edit.
Each output is judged once, with uncertain cases reviewed manually. Method names are hidden, and all methods use the same prompt and rendering settings. Completion is assessed separately from visual quality. The full prompt is provided in Appendix H of the revised manuscript.
Table R2. VLM-assessed overall edit completion on all 100 Eval3DEdit cases.
| Method | Overall edit completion (%) ↑ |
|---|---|
| Edit360 | 8 |
| EditP23 | 30 |
| AnchorFlow | 59 |
| 3DEditFormer | 55 |
| PartFlow | 38 |
| Nano3D | 39 |
| Nano3D† | 59 |
| Pace3D (Ours) | 71 |
† denotes the SS-NFE-matched Nano3D variant in Table 2.
These judgments use evidence from the rendered views and complement the direct geometric evaluation on paired cases.
4. Evaluation of Over-Editing
Pace3D reduces both extra additions and incorrect deletions on the 12 paired cases (Table R3). On all 100 Eval3DEdit cases, its VLM-assessed over-editing rate is 13%, compared with 24% for Nano3D† (Table R4).
For the paired evaluation, we voxelize the final meshes on a common grid after aligning the source, target, and edited meshes in position, orientation, and scale. Extra additions count occupied output voxels where both the source and target are empty. Incorrect deletions count voxels occupied in both the source and target but missing from the output. Each count is divided by the source’s occupied voxel count. Table R3 reports the mean percentages over the 12 cases.
Table R3. Over-editing on the 12 paired cases, measured from voxelized final meshes.
| Method | Extra additions (%) ↓ | Incorrect deletions (%) ↓ |
|---|---|---|
| Baseline (FlowEditing only) | 53.9 | 30.7 |
| Pace3D (Ours) | 28.1 | 15.9 |
For the benchmark-wide assessment, we use gpt-6-sol with the same cases, generated outputs, and rendered views as in Table R2. The judge identifies the requested edit and checks for major unrequested structural changes, including unintended removal or duplication of parts, collapsed geometry, and extra structures or fragments. Each output is judged once, and uncertain cases are reviewed manually. Method names are hidden, and all methods use the same prompt and rendering settings.
Table R4. VLM-assessed over-editing on all 100 Eval3DEdit cases.
| Method | Over-editing rate (%) ↓ |
|---|---|
| Edit360 | 85 |
| EditP23 | 58 |
| AnchorFlow | 55 |
| 3DEditFormer | 23 |
| PartFlow | 18 |
| Nano3D | 21 |
| Nano3D† | 24 |
| Pace3D (Ours) | 13 |
† denotes the SS-NFE-matched Nano3D variant in Table 2.
Under this evaluation protocol, Pace3D achieves the highest overall edit completion rate and the lowest judged over-editing rate among the compared methods.
Rebuttal by Authors [3/4]
[W2] Clarification of Data Sources
The main comparison in Table 2 uses all 100 Eval3DEdit cases. Each case provides a source 3D asset and a target image, but no paired target 3D ground truth. Table 7 also uses these 100 cases and compares using the proxy directly as the final sparse structure with using it as a progress reference in Pace3D.
The 12 paired cases in Sec. 5.1 and Appendix D.4 were prepared separately and are not a subset of Eval3DEdit. We used existing 3D generation and editing models to prepare candidate source–target pairs, followed by manual adjustment and screening. As described in Appendix C (“Data and case selection”), we retained cases with clear, spatially coherent structural changes and well-aligned source–target geometry, excluding minor, fragmented, or ambiguous changes.
These paired references support the structural-progress diagnostic in Sec. 5.1 and the proxy analyses in Tables 8–9. Table 8 compares editing results under proxy and oracle control. Table 9 evaluates phase error, progress ordering, and agreement with the oracle’s reset decisions, reporting a mean phase error of 0.133, an AUC of 0.857, and an F1 score of 0.592. These diagnostics assess the proxy on the 12 curated cases; they do not establish phase-estimation accuracy across the full benchmark.
[W3] Interpreting the PC-PC Drop and Mitigating Over-Editing
Using the controller alone can indeed cause over-editing. Rewinding retains the current latent and extends the sampling horizon, so unintended changes can accumulate along with the requested structural edits (Secs. 4.1–4.2). In Table 3, DINO-src decreases from 0.7957 to 0.7877 and PC-PC from 0.7604 to 0.7383, even though target alignment improves. Table R1 additionally shows lower Missing Structure but lower IoU with the controller alone.
PC-PC measures similarity to the source point cloud, so a correct structural edit can also lower this score. A PC-PC decrease alone therefore does not establish over-editing. The paired geometric measurements provide additional evidence about the changes relative to the intended target.
Source Alignment applies a weak pull toward the source latent at each SS step, attenuating accumulated deviations while allowing changes reinforced by the target condition to persist (Sec. 4.2 and Appendix A.4). Adding it raises DINO-src to 0.7914 and PC-PC to 0.7815, while also improving PC-Txt and MV-Img. The IoU recovery in Table R1 is consistent with this complementary role.
Cross-Condition Consensus then preserves local features during SLat generation by comparing source- and target-conditioned predictions at the same noisy state and aggregating their disagreement across steps (Sec. 4.3). It favors source features at shared locations with low disagreement, while new voxels and locations with stronger disagreement remain target-driven.
For reference, we reproduce the component ablation from Table 3 of the submitted paper below.
| Variant | DINO-src ↑ | PC-PC ↑ | PC-Txt ↑ | MV-Img ↑ |
|---|---|---|---|---|
| Baseline | 0.7957 | 0.7604 | 0.2409 | 0.7071 |
| + Controller | 0.7877 | 0.7383 | 0.2532 | 0.7218 |
| + Src. Align. | 0.7914 | 0.7815 | 0.2537 | 0.7229 |
| + CCC (full Pace3D) | 0.8009 | 0.7997 | 0.2566 | 0.7291 |
The full model improves both source fidelity and target alignment over the baseline in Table 3. Table R3 further shows fewer extra additions and incorrect deletions in regions that should remain unchanged.
Rebuttal by Authors [1/4]
Thank you for the constructive feedback. We have added geometric measurements and VLM assessments of edit completion and unintended changes to regions that should be preserved.
Image Editing Model Used in Eval3DEdit
The target images in Eval3DEdit were generated using Nano Banana, as described in Appendix B.1, Step 4 of AnchorFlow (Zhou et al., 2026). We use the target images provided by the benchmark without modification for the image-conditioned comparisons. These images provide the target condition for editing. We will clarify this distinction in the revised paper.
[W1] Evaluation of Structural Completion and Over-Editing
Embedding similarity does not directly measure structural completion. Our additional geometric evaluation shows that Pace3D reduces both missing structure and unintended changes. On the 12 paired cases, Missing Structure decreases from 0.418 to 0.350 at 643 (Table R1), while extra additions decrease from 53.9% to 28.1% and incorrect deletions from 30.7% to 15.9% (Table R3).
1. Results on the 12 Paired Cases
Table R1 reports the cumulative component ablation on the 12 paired cases used in Sec. 5.1. Alongside the metrics from Table 2, we evaluate Missing Structure (Appendix C, Eq. 48) and voxel IoU against the paired target. Both geometric metrics are computed from voxelized final meshes at 643 and 2563. Before voxelization, the source, target, and edited meshes share the same position, orientation, and scale. All methods use the same spatial extent and voxel grid at each resolution.
Table R1. Results on the 12 paired cases. Components are added cumulatively; the final row is the full Pace3D model.
Compared with the baseline, full Pace3D reduces Missing Structure by 16.3% at 643 and 39.6% at 2563, with IoU gains of 0.164 and 0.185, respectively. These comparisons are made within each voxel resolution.
The controller alone reduces Missing Structure but also lowers IoU, from 0.649 to 0.603 at 643 and from 0.595 to 0.527 at 2563. Adding Source Alignment raises IoU to 0.813 and 0.776 while further reducing Missing Structure. This is consistent with Sec. 4.2: additional sampling gives unfinished edits more opportunity to complete, but also allows unintended changes to accumulate. Source Alignment complements the controller by limiting this geometric leakage.
2. Interpretation of the Metrics in Tables 3–4
Eval3DEdit does not provide paired target 3D ground truth, so we use embedding-based metrics to assess source fidelity and target alignment across the benchmark. PC-PC compares the source and edited point clouds in Uni3D space, while PC-Img and PC-Txt measure alignment with the target image and text. DINO-src and DINO-tgt compare rendered outputs with source and target images using DINOv2; MV-Img and MV-Txt measure multi-view alignment using CLIP (Appendix B.2). By measuring visual and semantic agreement with the target image and text, the target-alignment metrics provide indirect evidence of whether the requested edit has been realized. They do not directly quantify missing geometry or changes to regions that should be preserved, so we complement them with the paired geometric measurements in Tables R1 and R3.