Skip to main content
D
DS_1058966410-Marble
10-Marble
November 20, 2025
Solved

Identifying quilts faster in import doctor

  • November 20, 2025
  • 3 replies
  • 464 views

Hi,
I have a question on working with imported features.
The model I have contains surfaces / quilts which have been imported.
I need to edit the model, for which i need to get into import doctor environment to make the changes.
so, 
1. I would like to have the quilts highlighted in the model tree as i pick it in the graphic window, currently this doesn't happen. is there a config to change this behavior?

DS_10589664_0-1763602737531.png

2. Is there an easy way to perform surface operations to get rid of multiple unwanted quilts (like using Revolve or extrude cuts). Currently, I could only identify the below option, but this gets rid of only one quilt at a time.

DS_10589664_1-1763603079512.png


Thanks.



Best answer by kdirth

If you change the selection filter to surfaces, you can use a window selection in IDD. 

 

You can also select a surface, then RMB and select "Select parent node" to get the entire quilt (most likely a part).

3 replies

D
Deepakjohsh13-Aquamarine
13-Aquamarine
November 20, 2025

For Q2,
You could use "Remove" option.
This will allow you to control select the surfaces you want to remove all at once.
Tip: Check the "Keep open" option if your soul goal is to only delete quilts and not patch them

Deepakjohsh_0-1763605242328.png

 

    tbraxton
    22-Sapphire II
    tbraxton22-Sapphire II
    22-Sapphire II
    November 20, 2025

    Q1: When in IDD mode quilts are not an option for selection, only surfaces. You can test this by trying the pick from list option with a surface of a quilt selected, you will not see quilt in the list.

    Selection filter in IDD mode (no quilt option):

    tbraxton_0-1763606933535.png

    When you select the surfaces in the graphics window they will highlight in the tree. Expand the quilts and the constituent surfaces will appear in the tree.

     

    Find quilt in model tree from selection in graphics window.

    tbraxton_1-1763607024222.png

     

    Q2.

    A better option than the use if flexible modeling remove is the following. Delete the quilts in IDD mode by selecting the surfaces and then press the delete key or delete option in the context sensitive pop-up menu from RMB.

      D
      DS_1058966410-MarbleAuthor
      10-Marble
      November 21, 2025

      @Deepakjohsh & @tbraxton Thanks, yes Remove does prove to be useful. 
      but still i need to pick the surfaces individually in order to remove them.
      is there any method such that i can remove a bunch of surfaces all at once without having to select them individually?
      Screenshot below might explain what i am looking for.
      I am looking to remove everything inside the bounding box in one go, all of them are surfaces.

      DS_10589664_0-1763708396207.png

      @tbraxton 
      IDD doesn't navigate to the selected surface in the model tree, expanding the quilts and identifying the surface is cumbersome because i have a huge list of quilts groups.

      is it possible to configure this to something similar to the response we get in creo modelling environments preselection highlighting?

      DS_10589664_1-1763708792843.png

      Thanks

      kdirth
      21-Topaz I
      kdirth21-Topaz IAnswer
      21-Topaz I
      November 21, 2025

      If you change the selection filter to surfaces, you can use a window selection in IDD. 

       

      You can also select a surface, then RMB and select "Select parent node" to get the entire quilt (most likely a part).

      There is always more to learn.
        tbraxton
        22-Sapphire II
        tbraxton22-Sapphire II
        22-Sapphire II
        November 21, 2025

        Just to clarify the suggestion from @kdirth . I don't think that you will be able to box select multiple surfaces and use RMB to select parent node. The parsing of the nodes only works in the context of having a single unique surface selected. If I am mistaken about this, feel free to correct this post.

        Terms & ConditionsCookie settingsAccessibility statement