acceptodds
Under review as a conference paper at ICLR 2027

Scope3D: Training-Free 3D Editing with Stage-Aware Control

Abstract

Generating and editing 3D assets is essential for digital content creation. Yet translating user intent into precise modifications while preserving unrelated geometry and appearance remains challenging. We present a training-free framework that interprets editing instructions and selects appropriate generative operations within a structured 3D model. An instruction-conditioned agent determines the spatial scope and representation requirements of each edit, guiding the choice of generative stages and preservation constraints. When local preservation is needed, the framework estimates an edit mask from the source and edited images and maps it to the source 3D representation through the generator's native cross-attention. The resulting spatial associations guide source-reference-constrained sampling, preserving designated content while allowing edited geometry to extend beyond the original occupied space. We examine the framework across geometry and appearance editing tasks, evaluating region localization, edit fulfillment, and preservation of source content.

Primary area:
generative models
Keywords:
3D asset editing, training-free editing, attention-guided localization, image-guided 3D editing, structured 3D representations

Reviews

Among:
Shape:
1234this paper, Bottom 10%
Figure 1. Mean review rating of the reviewed papers at ICLR 2027. This paper averages 1.67 over 3 reviews, above 10% of the others.
Reviewer_CGerOpenReview ↗
Rating
2
Confidence
2
Informativeness
2
Presentation
2
Soundness
2
Read review
Paper summary

Scope3D proposes a training-free framework for instruction-guided 3D asset editing built on a frozen TRELLIS model. An external instruction-conditioned agent (Gemini-2.5-Flash) maps each request to a two-bit route (g, ℓ): whether spatial support must change (structure vs. detail/appearance) and whether local preservation is required (local vs. global), yielding four routes (Table 1). Local routes estimate a 2D edit/keep partition from the source and edited images, map it into source occupancy through aggregated source-conditioned cross-attention (Eqs. 3–7), and apply noise-matched source-replacement constraints in the corresponding generation stage; global routes apply FlowEdit at the structure or feature latent level. Structural edits reuse source cross-attention for the first 15 of the 25 sampling steps and hard-correct the decoded occupancy (Eqs. 9–10); detail/appearance edits keep source occupancy and replace source features at retained coordinates (Eq. 11). The paper compares against Nano3D, VoxHammer, and VecSet-Edit on 16 curated requests (eight local ones) using CLIP-T, CLIP-I, DINO-I, and Dir-Con for whole-asset alignment, and CD, HD95, PSNR, SSIM, and LPIPS on local preservation, reporting the best mean CLIP-T, CLIP-I, DINO-I, CD, PSNR, SSIM, and LPIPS in Tables 2–3.

Critical strengths

Well-motivated route decomposition. Separating structural support changes from detail/appearance changes, and local preservation from global editing, maps naturally onto TRELLIS's two-stage structured latent representation; the four-route summary (Table 1) is easy to follow.

Reasonably complete engineering integration. The framework reuses established training-free controls (Prompt-to-Prompt attention reuse, RePaint-style noise-matched replacement, FlowEdit) at the appropriate representation level, and the appendix documents the 12-view render protocol, bootstrap intervals, color-space handling, camera conventions, and mask erosion rules.

Some explicit honesty about limitations. The appendix acknowledges that CLIP features miss localized/counting/spatial errors, that appearance metrics mix geometric displacement with material error, and that no independent 3D ground truth exists. This self-awareness is appreciated, although the main text under-weights these caveats.

Critical weaknesses

W1. The contribution is an orchestration of existing components; no standalone technical contribution is isolated

Almost every element of the method is a known training-free mechanism reused off the shelf: the two-bit route decision is outsourced to a closed-source commercial VLM; the local mask is source cross-attention pooled over steps, layers, and heads with foreground/background distance partitioning and a quantile threshold; preservation is RePaint-style noise-matched latent replacement; global editing is FlowEdit; the structure/appearance split is inherited from TRELLIS's occupancy/feature stages. The paper introduces neither a new representation, objective, sampling operator, nor theoretical analysis.

The three stated contributions are weak under scrutiny. Contribution (1) is a routing table that maps request type to existing TRELLIS stages; contribution (2) is the Prompt-to-Prompt/RePaint family of spatial controls migrated to voxel-stage cross-attention, with foreground/background ratios as the minor twist; contribution (3) is a comparative study, which is evidence rather than a method. The paper does not provide an ablation showing that the stage-aware routing, the foreground/background fusion, or the complement-based editable volume beats a simpler combination of the same components on the same backbone.

The gap to the closest concurrent systems is not delineated. VoxHammer combines edited-image guidance with a specified 3D region and restores source features outside it; Nano3D merges occupancy differences and latent features; VecSet-Edit already uses attention in a native LRM to select editable tokens; 3DMorph estimates bounds from image differences and camera information; VS3D intervenes in velocity space; 3D-LATTE applies attention control to native Gaussians; EditFlow3D applies trajectory-preserving guidance. The manuscript should state precisely which of these mechanisms Scope3D adopts, which it changes, and which ablation proves the change matters, rather than listing them in §2.2 without quantitative comparison to the bulk of them.

W2. The routing agent — a core system component — is never evaluated

The first decision of the pipeline is Gemini-2.5-Flash returning (g, ℓ), yet §5.1 states explicitly that "the comparisons evaluate the 3D editing backend with fixed route assignments and image-space regions, rather than frontend prediction accuracy." Routing accuracy, agreement with manually annotated routes, and failure cases of the agent are therefore completely absent from the experiments. A misrouted request (global change judged local, or material change judged structural) enters the wrong pipeline with the wrong preservation constraints, and the paper reports neither how often this happens nor any downstream fallback, route verification, or recovery mechanism.

The agent's specification is missing from the method: the exact prompt, the source/target image and instruction payload, temperature, output schema, tie-breaking for ambiguous requests (e.g., a color change that also deforms a shape), and a comparison against alternative routers (a different VLM, a rule/text classifier, or the human-oracle routing used in the backend experiments) are all undisclosed. Because the router is a closed, versioned third-party API, results will drift across model updates and cannot be reproduced from the manuscript.

This matters beyond a missing ablation: if the backend is evaluated only under oracle routes, the reported numbers describe the idealized four-route pipeline, not the end-to-end system a user receives when the agent routes freely. The headline training-free 3D editor has no measured end-to-end instruction-routing error rate.

W3. Evaluation is too small, self-referential, and metric-mismatched to support the claimed advantages

Sample size and generality. The whole study covers 16 hand-curated requests (four per route, nominally) and eight local requests, on assets and target images created by the authors. Appendix C itself states that the paired bootstrap intervals "describe variability within this curated set, not independent-test generalization." There is no public 3D-editing benchmark split, no held-out set, and no evaluation on previously published source assets or reference requests; reviewers cannot reproduce the comparison from named, shared data.

Bootstrap intervals overlap for the headline wins. In Table 4, CLIP-T intervals are [0.347, 0.368] for Scope3D vs. [0.336, 0.373] for VoxHammer and [0.346, 0.365] for VecSet-Edit; DINO-I is [0.682, 0.769] vs. [0.696, 0.753] for VecSet-Edit; CLIP-I intervals similarly overlap. Under these intervals the claim of "highest mean CLIP-T, CLIP-I, and DINO-I" is not a statistically supported lead over the closest competitors. Dir-Con is in fact led by VoxHammer (0.5987 vs. 0.5776), which the text notes but the abstract-level framing obscures.

W4. Localization is shown only qualitatively; its core design choices lack ablation, and the occlusion assumption is not validated

Figure 6 presents eight qualitative partitions against 3DMorph, Nano3D, and VecSet-Edit, but no segmentation quality (IoU/Jaccard, boundary F1, edit/keep recall) is computed against any annotated 3D mask.

W5. The method is not closed-loop: notation conflicts, unspecified schedules, and missing efficiency/reproducibility reporting

Route-to-table mapping is implicit. §4.1 gives two bits (g, ℓ) but never lists the four combinations and their Table 1 routes explicitly; the special cases in which the two bits conflict with the available stages are not discussed.

Questions for authors
  1. Router evaluation. Report agent routing accuracy against human-annotated routes over the 16 cases and a larger held-out set; publish the exact prompt, schema, temperature, and model version; compare against at least one alternative router and oracle routing; show end-to-end results (not backend-only) and list every misrouted case with its failure outcome.
  2. Statistical comparison. On a larger public split, report mean ± variance over repeated sampling and paired significance tests against Nano3D, VoxHammer, and VecSet-Edit; state explicitly which CLIP/DINO differences remain significant after the Table 4 bootstrap intervals are widened across cases and seeds.
  3. Independent preservation ground truth. Annotate edit/keep 3D masks for the local cases and report region-wise CD, HD95, IoU, and boundary metrics using those masks; decouple geometry error from appearance error; explain the Nano3D lower HD95 result and the per-case distribution behind Table 3.
  4. Localization ablation. Add IoU/boundary-F1 against reference masks; ablate aggregation selection T, α, buffer, foreground-only vs. background-only vs. fused scores, q, and equal vs. learned fusion weights; provide ranking-quality metrics before thresholding.
  5. Backbone and baseline fairness. Run all methods on the same source assets and target images; report whether comparing a TRELLIS-based method against a TripoSG-based method should be separated by backbone control experiments; add quantitative comparisons for 3DMorph, VS3D, 3D-LATTE, and EditFlow3D, or justify their exclusion.
  6. Occlusion analysis. Construct or select cases with occluded paired parts (both-side wheels, back-side handle, hidden components) and report localization and edit-fulfillment failure rates; state when the 2D-attention-to-3D mapping provably cannot identify the hidden extent.
  7. Method closure. Provide the explicit (g, ℓ) → route truth table; reconcile the two definitions of F; define all state symbols; bind CFG scales, replacement steps, and release schedules to Eqs. 9–11; describe boundary smoothing between retained and newly generated features.
  8. Cost and reproducibility. Report latency, FLOPs, memory, and API calls per edit versus each baseline; name the image editor; commit to releasing code, assets, target images, oracle routes, masks, prompts, and render scripts; document TRELLIS checkpoint and seeds.
Reviewer_wDqvOpenReview ↗
Rating
1
Confidence
3
Informativeness
2
Presentation
1
Soundness
3
Read review
Paper summary

This manuscript proposes a method for trainin-free local 3D editing. They use Trellis as their backbone and given an edited image of the 3D asset, they guide Trellis to perform that edit. Their main contribution lies in how they find which regions to edit and which regions to preserve. For that they use the cross-attention between 3D cells to the edited image patches. For the editing part depending on the type of edit, whether it is structural or appearance editing, they decide to edit stage 1 or 2 of Trellis generation. The editing itself is a mix of FlowEdit, Prompt-2-Prompt and replacing noised source content in places they want to preserve.

Critical strengths
  • Results are nice

  • The algorithm for separating edit and preserve regions is simple and smart

  • The training-free nature is useful

Critical weaknesses
  • The paper is very poorly written. There are a lot of undefined mathematical variables that are rarely used, a lot of unnecessary equations, and very vague and confusing sentencing, phrases and explanations. Plus, Figures 2 and 3 don't effectively convey the proposed method. Examples of undefined terms include B in line 245, U in line 271, and K3 in line 280.

  • 16 examples are too few to really assess the performance and robustness of the method compared to recent SOTA. There are established benchmarks in both VoxHammer and Nano3D which the paper compares to, with 100+ examples.

  • There are no ablation studies and experiments demonstrating the usefulness of the design choices

Overall, given the current state of presentation and incomplete experiments, I would not recommend acceptance.

Questions for authors

See above

Reviewer_bJLqOpenReview ↗
Rating
2
Confidence
2
Informativeness
2
Presentation
3
Soundness
2
Read review
Paper summary

Scope3D is a training-free 3D editing framework built on frozen TRELLIS models. An agent selects local or global editing, and whether to change structure or only detail and appearance. For local edits, foreground and background cross-attention map image changes to a 3D edit/keep partition. The method protects the keep region while allowing new geometry in originally empty space within the generation domain. It compares with three editing methods on 16 requests. These experiments use fixed routes and image regions, so they mainly test the 3D backend rather than the automatic frontend (Table 1, Sec. 4.2–4.3 and 5.1).

Critical strengths
  1. The local editing formulation is practical. Protecting the keep region instead of defining the full future edit volume allows new parts to extend beyond the source part. This reduces the need to guess the shape and size of new geometry beforehand. The paper also clearly states that restoring binary occupancy does not guarantee an identical final surface (Sec. 4.3, Eqs. 8–10).

  2. The backend results are promising. Figure 5 covers all four routes. Scope3D has the best mean CD, PSNR, SSIM and LPIPS on the eight local requests, though Nano3D has better HD95. This suggests useful preservation behavior on these examples, even if broader testing is still needed (Table 3).

Critical weaknesses
  1. Important parts of the framework seem not directly tested. Section 5.1 fixes both routes and image regions, so we do not know how frontend mistakes affect the complete system. There are also no ablations for foreground/background fusion, normalization, coverage selection or the local sampling components. This makes it hard to judge the benefit of the proposed choices. The coverage rule uses visible image area, while the paper itself notes that hidden parts may need a different 3D extent (Appendix A).

  2. The evaluation is too limited to establish reliable editing beyond these examples. There are only 16 curated requests, including eight local ones. All preservation scores use Scope3D's predicted keep region. If an intended keep part is wrongly marked as editable, damage there can be missed by this test. Figure 6 provides visual comparisons, not independent 3D labels (Appendix B). Table 4 reports bootstrap intervals, which is useful, but paired method-difference intervals are still needed to interpret the small whole-asset gains. Overlapping per-method intervals alone do not settle this.

Questions for authors
  1. How were the fixed routes and image regions obtained? Please provide the routing prompt and mask-estimation settings. What changes when the system uses its own predicted frontend, in route accuracy and final edit/preservation results?

  2. Can you compare foreground-only localization with the combined score, and test normalization, coverage sensitivity and the main local sampling constraints? Please clarify which cases use the keep buffer. Results involving hidden or thin parts would help assess the coverage rule.

  3. Can you evaluate localization and preservation with independently annotated edit/keep regions, and report paired differences against the closest baselines? This would help separate actual preservation gains from region-selection effects.

From OpenReview, CC BY 4.0. Authors as signed there; shown unedited.

Related papers

Loading the map…

Discussion (0)

Sign in to comment.