Browse State-of-the-Art › 3D Object Editing

3D Object Editing

3 papers with code · 1 benchmark · 1 dataset archive 2025-07-28

Computer VisionKnowledge BaseMethodologyMiscellaneousMusicPlaying GamesTime Series

3D Object Editing involves modifying the geometry and topology of a 3D object based on a provided text prompt or image input. The task aims to generate a mesh representation of the edited 3D object as output.

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
LLFF (1 row) CE3D Chat-Edit-3D: Interactive 3D Scene Editing via Text Prompts code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

1 dataset whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 8 · with a code link: 3 · where Syntology ran a sample: 1 (1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (1 of 8 tagged: 1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 8 of 8, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.

  • 23 Aug 2024 1 repository listed
    TL;DR Perform 3D object editing selectively by disentangling it from the background scene.
  • 9 Jul 2024 1 repository listed
    Recent work on image content manipulation based on vision-language pre-training models has been effectively extended to text-driven 3D scene editing.
  • Our method takes oriented 2D images of a 3D object as input and learns a grid-based volumetric representation of it.
  • Manipulating Vehicle 3D Shapes through Latent Space Editing
    31 Oct 2024 0 repositories listed
    Although 3D object editing has the potential to significantly influence various industries, recent research in 3D generation and editing has primarily focused on converting text and images into 3D models, often…
  • DragGaussian: Enabling Drag-style Manipulation on 3D Gaussian Representation
    9 May 2024 0 repositories listed
    User-friendly 3D object editing is a challenging task that has attracted significant attention recently.
  • GSEdit: Efficient Text-Guided Editing of 3D Objects via Gaussian Splatting
    8 Mar 2024 0 repositories listed
    We present GSEdit, a pipeline for text-guided 3D object editing based on Gaussian Splatting models.
  • Directional Texture Editing for 3D Models
    26 Sep 2023 0 repositories listed
    Texture editing is a crucial task in 3D modeling that allows users to automatically manipulate the surface materials of 3D models.
  • Unsupervised Multi-View Object Segmentation Using Radiance Field Propagation
    2 Oct 2022 0 repositories listed
    We present radiance field propagation (RFP), a novel approach to segmenting objects in 3D during reconstruction given only unlabeled multi-view images of a scene.

Syntology lines on 1 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections