Announcements
Autodesk Community will be read-only between April 26 and April 27 as we complete essential maintenance. We will remove this banner once completed. Thanks for your understanding

Crash: Clicking on Fillet created for an Solidworks import

kalmdown
Participant

Crash: Clicking on Fillet created for an Solidworks import

kalmdown
Participant
Participant

1) Import file.

2) Create a 0.5 fillet along deep wavy edge

3) Try to select Fillet.

- Issue - F360 stops responding and browser BG turns black.

- Expected - can select Fillet to delete.

 

Similar crash

1) Import Model

2) Select vertical edge

3) Fillet to 3.0mm

4) Select front/deep wavy edge

5) Fillet to .5mm

- Issue - F360 stops responding.

- Expected - Can apply fillet. 

Screenshot 2022-06-07 184502.png

0 Likes
Reply
406 Views
8 Replies
Replies (8)

kalmdown
Participant
Participant

Also tried filleting in one operation.

 

This shows the browser bar turning black...

Screenshot 2022-06-07 185418.png

0 Likes

sanjana.shankar.goli
Autodesk Support
Autodesk Support

Hi @kalmdown 

 

I'm attaching a screencast of the workflow you suggested to fillet the model successfully. Also, please check if your graphics driver is updated as that could be causing the issue.

 


Sanjana Goli
Software QA Engineer
Fusion 360 Webinars | Tips and Best Practices | Troubleshooting
0 Likes

hamid.sh.
Advisor
Advisor

Maybe it's because of non-smooth curvature (Display Detail Control is at High, I've temporarily split the body to have higher density of curvature comb). Not sure this is an artifact of export/import or it was originally made like this.

 

curvature.png

 

When I fillet a recreated (not very exact) model it works ok:

 

fillet.png

 

Hamid
1 Like

kalmdown
Participant
Participant
When you say "non-exact", does that mean you did something to my model or recreated it?

Is there a way to fix curvature issues like this in F360 or does it require a dif app?
0 Likes

hamid.sh.
Advisor
Advisor

By "non exact" I mean I took your model only as a visual reference for recreating the model. I do not know the design intent. If you see the file I posted you notice that what I've done does not exactly match your model. Now if your design intent is just something of this wavy appearance then what I did is fine. But if you have some other requirement for this model, e.g. the surface following a specific mathematical curve or the model being mated to another part then my model has no further use than showing fillet works if curvature isn't wiggly.

 

I don't think fixing curvature of the current imported model is possible in Fusion. But the question is rather how did it end up like this. Does the original program in which you created it have curvature analysis tools? If so, investigating it there might help determining whether it's a modeling problem or something that happened in export/import.

Hamid
0 Likes

kalmdown
Participant
Participant

Updated my graphics driver to the latest: NVIDIA Studio Driver 512.96, released 05/23/22.

Fusion still crashes with black browser panel. 

0 Likes

jeff_strater
Community Manager
Community Manager

joining this thread late.  A couple of questions, triggered by a few things you said ("black browser", "selecting the fillet")

  1. Does Fusion actually crash?  That is, do you get a crash dialog report?  The "black browser" leads me to wonder whether Fusion is just very busy (a UI glitch makes the browser background not get rendered correctly when the application is busy for a long time).  Do you end the process/force quit?
  2. When you say "select the fillet", do you mean select the fillet face in the graphics area?
  3. Do you have "default measure" turned on?
    Screen Shot 2022-06-12 at 3.55.45 PM.png

If so, disable that preference.  What I suspect is happening is:  When this is on, Fusion "measure" the selection.  In the case of a face, that measurement is surface area.  For complex faces, this can take a long time.  My guess is that if you let this run long enough, it would select that face OK.  So, give that a try and let us know.

 


Jeff Strater
Engineering Director
1 Like

kalmdown
Participant
Participant

You may be correct but even with it turned off it did not come back for over 5m. And clicking on anything sets it off for another 5m and there is no feedback that suggests it is not crashed.

0 Likes