Already Shelled

[SEIZMICdesign]

Never run into this before, but not sure I've tried this exact process before either.

So this was an imported body from SolidWorks. It was shelled, but to make it easier to join to a new body I created in Fusion, I deleted the shell. I then joined it to the new Fusion-created body, and tried to re-shell. That's when I got this error. Anyone know how to get around this?

I checked the other threads on this and decided to add this one since I know A) it's not currently already shelled, B) I don't have some ridiculous geometry that can't be shelled because C) It was just shelled earlier - I know this because I just deleted the shell! So slightly different situation from the others.

Honestly it's not the biggest deal (this time) but in the future I can see it becoming an issue possibly. 

No, I cannot upload/share CAD due to confidentiality issues.

UPDATE: NOT LAREADY SHELLED:

[jhackney1972]

Please attach your model so the forum users can troubleshoot it.  Without seeing your model, I would guess it is not solid inside so the shell command sees multiple faces and determines it is not solid.

[SEIZMICdesign]

please read my post.

[jhackney1972]

Without the ability to see the model, my original guess as to the issue stands.

[SEIZMICdesign]

see update.

[TheCADWhisperer]

---

@SEIZMICdesign wrote:

It was shelled, but to make it easier to join to a new body I created in Fusion, I deleted the shell. I then joined it to the new Fusion-created body...

---

Show Timeline image of these steps...

[SEIZMICdesign]

It was an imported SolidWorks model, and I did not turn on the timeline. So, unfortunately, no history.

[jeff_strater]

I know you cannot share the entire design for confidentiality reasons, but can you export just this one body?  Turn off everything in the design (all other components, and other bodies in this component), export, choose "SMT" as the output type (this is a geometry format that Fusion's modeling kernel uses), and export.  You should get a result that is just that one single body (no component data, no other bodies, etc).  Try loading that on your computer to make sure it just contains that single body, then share it.

If that is still too confidential, you can email it to me personally at jeff.strater@autodesk.com, and I can assure you that no one but the development and QA teams will look at it.

Thanks.

[SEIZMICdesign]

good point. 

[jeff_strater]

thank you.  I can reproduce it on this body.  Very strange.  Three possibilities here:

1. the error message is wrong/misleading - some bad logic is telling you lies, and the problem is really something else
2. some remnant of the original shell is still around (maybe some attributes we use to record features on the body) and that is tricking the shell command into thinking the body is already shelled
3. just some bug in shell...

We'll investigate further.  Thanks for sharing this body.

[jeff_strater]

using a Split Body as a "divide an conquer" tool, I narrowed the problem down to this end of the body:

at first, I thought it was the grooves on top:

but, I removed those and still have problems with that end of the body.  More investigation is needed.  I'm suspecting the small faces in the fillet, but am not certain of that yet.

[jeff_strater · Accepted solution]

aha!  I found it!  And I was kinda right about that small fillet face - it was not the problem, but it was nearby.  Somehow there is a small circular void in there.  Not sure where it came from, and I only found it by accident.  But, if you get rid of it, the shell works.  So, the error message was actually correct (kind of) here.  It did detect another "shell" in the model, albeit a very tiny one.  

[JamieGilchrist · Accepted solution]

Nice one @jeff_strater .

using the section view or splitting a body is a great tool for trouble shooting .  I often forget, but this case reminded me that sometimes a wireframe view can reveal the problem too when you're trying to investigate. 

 

[SEIZMICdesign]

holy crap! I won't forget that trick! thanks everyone!