Sweep fails after changing underlying reference coil angle; ctrl-B sometimes fixes it, but causes lost body error on dependent operations

cdelguercio
Participant

Sweep fails after changing underlying reference coil angle; ctrl-B sometimes fixes it, but causes lost body error on dependent operations

cdelguercio
Participant
Participant

I have a Sweep that follows a Path + Guide Rail that in turn come from a reference triangle Coil. The profile for the Sweep is constrained to the bottom end of the Path helix. The reference triangle Coil is defined by a User Parameter for the pitch, which is defined as "2 * pi * inner_radius * tan(theta)" where "theta" is another User Parameter in degrees. In the provided .f3d if I change theta from 1.1 to 1.2 and back again, the Sweep operation will fail. Ctrl-B will sometimes fix it, but since a New Body is made with a different name (BodyX), this causes the simple Cut operation that I do next to fail and give a "the target body is lost" error.

 

My two questions are:

 

1) What is causing the sweep to fail for certain values of theta; it doesn't seems like the coil geometry is interfering with itself, even at these tiny angles.

2) Is there a way to force the Sweep to not make a New Body that clobbers all future references to the Sweep object?

0 Likes
Reply
Accepted solutions (1)
368 Views
6 Replies
Replies (6)

jeff_strater
Community Manager
Community Manager
Accepted solution

The sweep issue definitely seems to be a bug.  I think what is happening is that the Path Distance and Guide Rail distance is getting lost.  What I see is that any change will cause these parameters to be lost.  There is nothing about 1.1 degrees that causes this.  If you edit the feature when Theta is 1.1, and set these two values to 1, the sweep succeeds, but changing to 1.2 will cause a failure as well.  I was unable to get Compute All to ever fix it.

 

OK:

Screen Shot 2022-05-11 at 7.59.40 PM.png

 

after any change of Theta:

Screen Shot 2022-05-11 at 7.59.59 PM.png

 

[edit] - I created bug FUS-104611 for this


Jeff Strater
Engineering Director
0 Likes

cdelguercio
Participant
Participant

Thanks Jeff! I'll be sure to follow up when the next release comes out!

0 Likes

cdelguercio
Participant
Participant

I still have this issue in the May 2022 release (2.0.13158). Is there an estimate on when this will be worked on?

0 Likes

jeff_strater
Community Manager
Community Manager

Correct.  That bug has not been addressed in this update.  We do not have an estimate on a timeline for an expected fix at this time.


Jeff Strater
Engineering Director
0 Likes

cdelguercio
Participant
Participant

I still have this issue in August 2022 build 2.0.13881. Any updates?

0 Likes

cdelguercio
Participant
Participant

I still have this issue in October 2022 build 2.0.14567. Any updates?

0 Likes