Derived Part dependent on workplane not updating automatically

Derived Part dependent on workplane not updating automatically

Anonymous
Not applicable
881 Views
8 Replies
Message 1 of 9

Derived Part dependent on workplane not updating automatically

Anonymous
Not applicable

Attached is a simple example where a skeleton sketch defines the position of a workplane ("Middle Plane Locator Sketch" in the Skeleton part). When the point that defines the position of the plane changes the derived "HorizontalFrame..." part does not update. If the "Edit Derived Part" option is selected the drawing immediately updates, but if the dialog is cancel it reverts, but the update happens if the dialog is exited with "Okay" (without making any changes).

 

I have seen a similar post where the issue was explained by not having a parameter exported, but in this case the dependency is on the position of a plane which clearly is changing. I added an exported parameter (not in the attachment) that is driven by a dimension connected to the plane, and this has no effect on the plane.

 

This is a sinister problem in that a small change to the plane height could well go unnoticed in derived parts, and to require a manual derive edit is hardly a solution.

 

I am using Release 2018.2, build 227

 

To reproduce the problem -- open the skeleton, edit the middle plane locator sketch, view from the front, and change the lower dimension (d114) by adding 24 in there by shifting the plane up significantly.

0 Likes
882 Views
8 Replies
Replies (8)
Message 2 of 9

johnsonshiue
Community Manager
Community Manager

Hi! This is a very good catch! The change in workplane should propagate to the derive part. This is a bug. I will work with the project team to understand the behavior better and see how we can fix it.

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
Message 3 of 9

chayman
Enthusiast
Enthusiast

Has there been a repair for this bug?

I am having the same issues at the moment.

0 Likes
Message 4 of 9

cencinaNB2ET
Advocate
Advocate

It seems its happening now with my parts as well.

I create derived parts from assemblies and then connect/make planes to the derived part automatically.

the planes are not present anymore in the derived model.

 

 

 

0 Likes
Message 5 of 9

johnsonshiue
Community Manager
Community Manager

Hi! The behavior does not sound right to me. The only logical explanation is that the derive source geometry is gone and the derived geometry is indeed broken with the source geometry. Could you share an example so we can take a look?

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 6 of 9

cencinaNB2ET
Advocate
Advocate

I figured out why this was happening...

 

I cant rebuild planes in the parent assembly

 

so once its derived you cant update the planes ( delete, place) as this data will be lost in all derived parts.

 

please screencast to confirm...

 

 

 

 

0 Likes
Message 7 of 9

johnsonshiue
Community Manager
Community Manager

Hi! Many thanks for recording the video! But, I have to say I don't quite follow what you did. What do you mean by rebuilding those workplanes? If your code delete the existing workplanes in the source assembly and recreate them, the derived workplanes will be gone. Is this what you are seeing? If yes, this is how Derive works. You can reproduce the behavior manually without using iLogic rules. Even if you name the new workplane (source) the same as the one before, the internal object ID will be different.

Many thanks!

 

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 8 of 9

cencinaNB2ET
Advocate
Advocate

Exactly The object ID then is different... OK that was my question.

 

Then I meant recreate them by deleting and then placing them again.

 

So what was the Bug then referring to?

 

 

0 Likes
Message 9 of 9

johnsonshiue
Community Manager
Community Manager

Hi! Originally, I thought you were talking about change in the same source geometry not propagating to derived geometry. If it was the case, it would be a bug.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer