Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

boundary fill gives no warning when it fails (no yellow icon in timeline)

boundary fill gives no warning when it fails (no yellow icon in timeline)

derProtoTyp
Enthusiast Enthusiast
2,125 Views
6 Replies
Message 1 of 7

boundary fill gives no warning when it fails (no yellow icon in timeline)

derProtoTyp
Enthusiast
Enthusiast

I´m twaking a somewhat complex shape that is generated via several surfaces and a boundary fill command. unfortunately when I tweak the sketches that generate the curves and move a point too far, the boundary fill stops to update. that is expected. but it does not give a warning (yellow icon in the timeline). several times this made me move arround points, wondering why nothing is updating.

 

 

0 Likes
Accepted solutions (3)
2,126 Views
6 Replies
Replies (6)
Message 2 of 7

James.Youmatz
Autodesk Support
Autodesk Support

Hi @derProtoTyp,

 

Taking a bit of a stab here - if you do a Compute All from the Modify menu (which recomputes the timeline) after a boundary fill failure do you see it generate warnings/failures? I'm not sure if dragging sketch elements forces a full compute of the timeline which would probably generate the error. If not, then certainly something strange is going on as it should populate some warning.

 

Thanks,

You found a post helpful? Then feel free to give likes to these posts!
Your question got successfully answered? Then just click on the 'Mark as solution' button.


James Youmatz
General Adoption Manager | Informed Design

0 Likes
Message 3 of 7

derProtoTyp
Enthusiast
Enthusiast

hi @James.Youmatz 
thank you for looking into this issue - maybe that was not very obvious in the screencast but I triggered the compute all command twice without any warnings. ...did it via the s key search menu... (s com... arrow down enter) but just in caste that would make any difference I just tried via the modify menu as you suggested. same behaviour. can you reproduce this behavior on your computer? I could only test on two windows machines (both win10).
all the best

B

0 Likes
Message 4 of 7

jeff_strater
Community Manager
Community Manager

I can reproduce the behavior with dragging sketch curves so that the surfaces no longer overlap, and the Boundary Fill fails silently, and can acknowledge that it is a bug. 

 

One thing I would like to point out, however, is that this situation: 

Screen Shot 2019-09-12 at 11.44.32 AM.pngScreen Shot 2019-09-12 at 11.44.32 AM.png

when you have deleted all the sketch curves, causing the extrudes to fail, but the Boundary Fill does not fail, is not a bug.  The Extrudes have all failed in a warning state, but Fusion still has the cached outcome of those Extrudes, which is why the Boundary Fill succeeds.

 

[edit] bug is FUS-54232


Jeff Strater
Engineering Director
Message 5 of 7

derProtoTyp
Enthusiast
Enthusiast
Accepted solution

Hi @jeff_strater,
thank you for your reply!
Absolutely! My deleting of the curves in the screencast was confusing. Its the expected and correct bahavior that these subsequent features still exist because of the cashed geometry.

 

If anyone has the same issue/workflow:

One workaround for me right now is to add a small surface (tube for instance) that allows for a second cell to be generated in the Boundary Fill but not select that small cell. So instead of my main cell failing silently the Boundary Fill "jumps" to this second possible cell, at the moment I move the curves too far - which makes it very obvious.

 

0 Likes
Message 6 of 7

derProtoTyp
Enthusiast
Enthusiast
Accepted solution

and one final side note to my workaround: when my small "helper" cell is inside the main cell and I have to select it also to get my desired shape, Boundary Fill fails as expected (with warning and yellow icon in the timeline) when curves get moved too far. So aparrently the bug only occures when there is only one cell? Maybe that helps...
Kind regards

Bernhardr

0 Likes
Message 7 of 7

jeff_strater
Community Manager
Community Manager
Accepted solution

thanks for the info, @derProtoTyp - you may be correct, that this is a problem only when there is one cell.  Nice debugging!


Jeff Strater
Engineering Director
0 Likes