Crashing with Goto command.

[meganine]

Hi all,

I've got an interesting problem.

I finished designing the rough version of a part the other day. Today, I went back and started to add rounds, chamfers, drafts, etc.

Not all of the features could be added to the end of the feature list, so I used the Goto command a couple of times to place the features in the right place.

My problem is this: when I try to resume the last feature (i.e. right-click on it in the feature list and select Goto), SE crashes.

I've tried everything: restarting SE, rebooting windows, opening a copy of the file, opening the file on a different machine, opening through a different environment of SE (i.e. Draft instead of Part). I've even tried deleting the feature's parents further up the feature list.

No luck. Everytime I try to resume the feature, SE crashes.

Has anyone else run into this? Is there any way to delete the offending feature without resuming it first? SE just buzzes at me when I try.

Thanks in advance,
Chris

BTW: I'm running V11 SP4.

 

[jwillison]

Hmmm, off the top of my head I would say the problem probably has top do with invalidating a connecting point or plane when you insert a feature with the goto command (such as round, which changes the adjoiniung surfaces). When you try to return to the last feature something has been lost that was being used to create subsequent features. Try clicking on the first feature and recomputing after inserting the fillet (chamfer, whatever) and see if that helps. The other option would be to use goto to step through the festures one at a time after inserting the new one to see which is the problem.

If nothing else works then how about suppressing the feature before adding the new feature? Then try unsupressing it after.

Hope this helps.

 

[littlef8]

You may have something wrong with the file prior to adding features. Unless I'm not fully understanding the problem, you should not have to "go to" to add any rounds, chamfers, ....

Is Solid Edge crashing, or locking up.

 

[meganine]

Since most of my designs end up as plastic parts, almost every face requires a draft and every edge requires a round.

When in the concept stage of a design, usually I don't want to worry about the drafts, rounds, and chamfers. I'm focused on solving the problem at hand. Adding the drafts, rounds, and chamfers during the concept stage would slow up the process way too much.

Once everything is working, I start to add these features. However, some of the drafts, rounds, and chamfers don't work well if they are added to the feature tree at the wrong time.

Here's an example from the SE Help files (titled 'Treatment Features', there's pictures near the bottom under 'Things to Consider with Rounds and Draft Angles'):

--------------------------------------------------------

If you are adding both rounds and draft angles to a model, there are a couple of things you need to consider before deciding on the order in which you add these features. If the rounds are added first, the rounded faces no longer have a constant radius and are conical.

If you add the rounds after the draft is applied, the radius value will remain constant.

The manufacturing process used to produce the actual part may be the factor that determines when the rounds are added.

--------------------------------------------------------

I'm sure others users have discovered that creating a series of rounds that overlap each other needs to be done in a certain order or the desired result cannot be achieved. The same holds true for any other feature. Obviously, you can't cut a solid if you haven't yet created the solid.

Hindsight is 20/20--it's easy to know the correct order once the model is completed. But during design, the order of every single feature cannot be predicted. Therefore, you need Goto to create the correct order.

jwillison: Invalidating a connecting point, plane, etc. should result in a grey arrow or a red exclamation mark.

littlef8: Crashing, locking up, whatever it's called. It brings up the lame window that informs you that SE is shutting down and to check the error log.

On a more positive note, I did solve my problem. Since I keep every major revision, I loaded the previous one and modified it until it matched the current one, including the offending feature. So far there haven't been any problems, but it was a very slow workaround (about 90 minutes).

This isn't the first time I've run into this, so I'd like to know why it happens. That way, I may be able to avoid it.

Thanks again,
Chris