Here's a neat bug in 04: parent-child

Discussion in 'SolidWorks' started by Nick E., Nov 17, 2003.

  1. Nick E.

    Nick E. Guest

    I have a part created totally in '04, with 3 or 4 configs.

    Now, in config1, my parent-child tree for FeatureA is COMPLETELY DIFFERENT
    than what shows up in config2.

    Basically, I can't complete my part now until they fix this shit.

    --nick e.

    p.s. reading other posts, it appears that my fears have come true. SP0.0
    ended up being pretty good thanks to all the beta testing. Now with the
    release of SP's certified <sic> by SW quality <sic> control, we're getting
    the shaft again.
     
    Nick E., Nov 17, 2003
    #1
  2. Nick E.

    kellnerp Guest

    Can you explain how you got to this point?
     
    kellnerp, Nov 17, 2003
    #2
  3. Nick E.

    Todd Guest

    A little explanation, or an example would help.

    With the description you gave, I could easily say "so, thats very easy to
    do" but I am assuming you know SolidWorks better than that so I would like
    to see the exact issue so I know what to look out for...

    --Todd
     
    Todd, Nov 17, 2003
    #3
  4. Nick E.

    Nick E. Guest

    I have a casting which creates three similar, finished parts. Basically,
    only the thickness changes. Each is ground to near finished size, machined,
    then ground to finish size after heat treat.

    Some features are reusable. Some are not. Those that are I am trying to have
    unsuppressed in all three finished-part configs. Problem is, some features
    are erroneously listing the wrong features as parents. And it depends on
    which config you are in when you check the parent-child relationships.
    ConfigA shows everything fine. But when you switch to ConfigB, it lists
    different features as parents.

    The neat thing is that I now have an unsuppressed feature as the child of a
    suppressed feature. Only in one config tho. Neat, huh? That suppressed
    feature isn't listed as a parent at all in a different config.

    This worked just fine in SW2001+.

    Todd, if changing parent-child relationships between configs is easy to do,
    please post step-by-step instructions.

    And btw, var knows, and it's been sent to SW. And they actually have a
    similar problem from someone else too!! That file was sent along with mine!

    QA rears it's ugly head again.

    --nick e.
     
    Nick E., Nov 17, 2003
    #4
  5. I would be interested in seeing this part - would you send it to me? I'm
    trying to visualize what's going on and would like to study the feature tree
    to better understand the situation. Thanks.

    WT
     
    Wayne Tiffany, Nov 17, 2003
    #5
  6. Nick E.

    Todd Guest

    Nick,

    An instance where you could have a parent-child relationship in one config
    but not another would be:

    1. Create an extrusion
    2. Create another extrusion "up to surface" and select a surface off
    extrusion 1
    3. create a configuration where extrusion 2 is blind

    So one configuration is "up to surface" and the other is "blind"

    Extrusion 2 now has 2 different sets of parent/child relationships between
    the configs.

    Make sense?

    I am sure there are more similar examples but thats the first that comes to
    mind.

    --Todd
     
    Todd, Nov 17, 2003
    #6
  7. Nick E.

    Nick E. Guest

    hmmmmm....think so.....maybe.......but not quite what my problem is.

    problem is that the parent-child configs are wrong. there is no apparent
    reason for the problem i'm seeing. like I said, var confirmed, too. So it's
    not me. :)

    --nick e.
     
    Nick E., Nov 18, 2003
    #7
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.