- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes RelShape, which generates realistic articulated 3D objects with movable structures while emphasizing structural control and editing. The paper achieves this goal by developing a variation-first coding agent based on DeepSeek-V4.1-Flash, that generates intermediary programs to construct the specified objects part by part, and uses a visual critic to revise the generated output. The agent refines the output for up to two rounds, stopping early if it satisfies all specified control requirements and passes the rule-based checks, which makes the program can establish articulation relationships consistent with the instructions and produce a preliminary visual appearance. The paper then refines the details and materials of the preliminary geometry using a materialization procedure and the TRELLIS.2 generator. Experiments show that RelShape achieves the best performance among program-synthesis methods, attains reconstruction quality comparable to that of pretrained models such as TRELLIS.2 and Hunyuan3D 2.1, and outperforms other program-synthesis methods in controllability tests.
Critical strengths
- This paper proposes a practical algorithm for constructing and refining a 3D model generation program, while checking geometric residuals, visual similarity, and changes in control settings. This gives the method the potential to reconstruct many real-world articulated objects with complex interaction logic and conditional constraints on part movement. It also demonstrates superior performance in structural control compared with other methods.
- The proposed algorithm also appears to be extensible, as it is not tied to a specific agent or visual critic. As foundation models become more capable, the algorithm can be expected to handle more complex and diverse modeling tasks and produce more realistic results.
Critical weaknesses
- The emphasis on variation is mostly on structural control, but the specific range of motion along each control axis is not explored in depth. Within the authors’ algorithmic framework, controllable relations could support more dimensions, including not only the number, positions, or types of parts, but also how far they can open or close, interaction directions (e.g., for buttons or sliding switches), and occlusion conditions. These aspects are particularly important for detailed modeling of certain objects, such as capturing the interaction logic of buttons, levers, and knobs on a toaster. If these goals were achieved, my confidence in the method’s extensibility would increase substantially.
- The paper does not test the algorithm’s extensibility, for example by using different foundation models to assess its robustness to the choice of foundation model and substantiate its independent contribution. Given that foundation models are becoming increasingly capable, with some already able to perform 3D reconstruction independently, I believe that such tests of the algorithm’s extensibility are still necessary.
Questions for authors
- As mentioned in W1, in the examples shown in Figures 1 and 5, the range of variation along each control axis does not appear to be determined by the input. Are these ranges determined by the agent and then checked, or are they set empirically at a later stage?
- Figure 9 shows a toaster model generated by RelShape, as well as models of other intricate objects, such as a washing machine and a watch. Are the buttons, knobs, and other small components on these models interactive? If so, could the authors provide GIFs demonstrating their ranges of motion?
- As mentioned in the previous point, Figure 9 provides only static images, but motion is central to articulated objects. Could the authors provide GIFs of these examples to demonstrate their ranges of motion?
- Could the authors test the algorithm with other foundation models, particularly those capable of performing modeling tasks independently, to isolate the performance gains attributable to the algorithm? This would be very helpful for assessing its extensibility.
2 comments
Response to Reviewer W748 (2/2)
[W1, Q2, Q3] Buttons, levers, and knobs
As generated, the toaster's lever slides. Following your suggestion, four new instruction-guided edits make the buttons and the dial knob interactive on the Figure 9 toaster, washing machine, and watch, with the system unchanged. These edits use the instruction-guided editing of the original submission (Section 4.3 and Figure 5, page 9). Each request names the parts that should be pressable or rotatable and gives no range. The agent gives each part its own control, declares the range of that control, and checks it by execution.
For the dimensions you list in W1, the table below gives the interaction direction of each part, how far it moves, and the limit that neighboring parts place on it:
| Object and part | Interaction direction | How far it moves | Limit from neighboring parts |
|---|---|---|---|
| Toaster, lever (as generated) | slides along its track | 0.15 to 0.85 of the track | the grip stays over the track and clear of the button row |
| Toaster, four buttons | each presses in along its own axis | 0 to 3 mm | a fully pressed button stays 3 mm proud of the panel |
| Washing machine, dial knob | turns about its own axis | -180° to 180° | none, it turns a full circle |
| Washing machine, five buttons | each presses into the panel along its guide bore | 0 to 6 mm | the front panel skin is 8 mm thick, and a 2 mm margin is kept |
| Watch, three buttons | each presses into the case along its own axis | 0 to 0.5 mm | the button neck is 0.6 mm long, and a 0.1 mm clearance is kept |
All settings executed over these ranges pass the rule-based checks. In each setting of the four edits, the pressed or turned part moves and every other part stays in place. On the toaster of your example, the lever slides and each of the four buttons presses independently.
The supplementary webpage's "Pressable buttons and a rotatable dial through edits" section shows GIFs of these motions for the toaster, washing machine, and watch of Figure 9. The sliding lever is in the "Control sweeps" section.
[W2, Q4] Other foundation models
Following your suggestion, we ran RelShape with a second foundation model, GPT-6.1 Sol. The method runs unchanged, and on the same model it leads aDSL by 31.3 points with DeepSeek and by 56.2 points with Sol. aDSL is one of the program-based methods of Table 2 that run on the same LLM as our agent. Each row below therefore holds the foundation model fixed and changes only the method.
| Foundation model | RelShape | aDSL | Lead |
|---|---|---|---|
| DeepSeek-V4.1-Flash (Table 2 of the original submission, page 8) | 71.9 | 40.6 | 31.3 |
| GPT-6.1 Sol (new, Appendix F.5, page 26) | 60.4 | 4.2 | 56.2 |
The table reports Success on the 16 objects of Table 2 under the same held-out protocol. In the new run, every stage of our agent uses Sol, including the visual critic. With Sol, RelShape's programs expose a control for 75.0% of the held-out goals, against 93.8% with DeepSeek. On the settings with a control, RelShape succeeds on 80.6% with Sol, against 76.7% with DeepSeek (Appendix F.5).
The ablations of Table 3 of the original submission (page 9) isolate the performance gains attributable to the algorithm. They keep the foundation model and remove one step of the algorithm. Success falls from 71.9 to 45.8 without variation planning and to 51.0 without variant feedback.
For models capable of performing 3D generation independently, Table 1 of the original submission (page 7) compares our assets with those of TRELLIS.2 and Hunyuan3D 2.1. These generators output an asset without a program. Our assets answer more structural questions on text and achieve the highest Elo of all methods on images.
Response to Reviewer W748 (1/2)
We sincerely thank you for your positive assessment of our work. We are encouraged that you find our algorithm practical, with its checks of geometric residuals, visual similarity, and changes in control settings. We are also glad that you recognize its superior performance in structural control. We value your observation that the algorithm appears to be extensible, as it is not tied to a specific agent or visual critic. Your suggestions point to two tests of this extensibility, and we ran new experiments for both. For W1, we swept controls over their full declared ranges and made the buttons and the dial knob of the Figure 9 objects interactive through edits. For W2, we ran the method with a second foundation model. The GIFs you asked for are on the anonymous supplementary webpage.
[W1, Q1] Range of variation along each control axis
The ranges are determined by the agent and then checked by execution, and none is set empirically at a later stage. As you rightly point out, the input does not determine the range of a control. It depicts the object at one setting, which gives each control its default value. Before construction, our agent declares each control with the range that the object's function allows (Section 3.2, page 5). For the watch of Figure 9, its declaration sets the strap hole count from 3 to 9 so that the whole row of holes stays inside the rib band of the strap. It sets the bezel ridge count from 12 to 72 because the gaps between the teeth would close near 96. The agent then executes each control at non-default values and keeps only the controls whose declared effects hold.
To explore these ranges in depth, we ran new sweeps. For one control in each of 8 generated programs of Table 1, we executed the unchanged program over the full range that the agent declared. All 60 settings pass the rule-based checks.
The supplementary webpage's "Control sweeps" section shows a GIF of each sweep.