Split Body "unhandled intersecting tool data"

[LaleveeJT]

I'm modeling a door frame and I'm trying to split the body to show how it will be constructed with butt joints. I'm having trouble splitting the body using faces of the body. I do similar operations often with shelled features and recently I've been running into this error more often. The split will fail and give me an "unhandled intersecting tool data" error (see attached). As far as I can tell my selected planes aren't close to intersecting with each other. I've also tried the same operation using one body surface at a time with the same result. I know there are similar forum posts with this error but they all seem like complex splits, while mine are two very well defined and simple parallel splitting planes. 

I can get around this error by making construction planes and using them to make the split, but that's three extra steps for something that should only be one. I could also add this split in with my sketch geometry but that also introduces more unnecessary steps to my workflow (multiple extrudes to ensure separate bodies (separate bodies are necessary to show correct construction in drawings and correct orientation of wood grain in renders)). While these solutions work I believe my initial workflow should have worked the first time around.  

I've attached a model and relevant screenshots. 

[g-andresen]

Hi,

---

@LaleveeJT wrote:

I can get around this error by making construction planes and using them to make the split, 

---

This is the first solution!

günther

[LaleveeJT]

While it is a solution am I wrong to assume splitting with the body faces is the easiest way to do this?

Interestingly enough I was able to get this to work on another file going off a shell command, not an extrusion with offset sketch geometry. I would assume since these two bodies are essentially the same they would behave essentially the same, but that doesn't seem to be the case. 

[jeff_strater]

you are correct, @LaleveeJT - this should work with a planar face.  Oddly, this has been reported in another thread: split-body-quot-unhandled-intersecting-tool-data-quot and we are investigating.  Will add your case to that bug.

[LaleveeJT]

Thanks Jeff! Could you send the link to the other case again, the one in your post links back to my post. 

[g-andresen]

Hi Jeff,

The reason for the described behavior are the previously created cuts with planes perpendicular to this faces.

Screencast

günther

[jeff_strater]

sorry - juggling too many tabs with very similar titles.  This is the other thread:  split-body-unhandled-intersecting-tool-data 

@g-andresen - I understand what you are saying, but it seems to me that if the operation succeeds with a workplane, but not by directly selecting the planar face on which that workplane is based, that we should investigate this as a bug.

[LaleveeJT]

Any updates on this bug? I'm still running into it frequently. 

[sunil.v.b]

Hi @LaleveeJT We have fixed this issue and should be available in next update of Fusion

Thanks

Sunil

Fusion development team

[g-andresen]

Hi Sunil,

nice to hear

günther

[LaleveeJT]

I am experiencing this issue again, did this fix ever go through? 

[sunil.v.b]

@LaleveeJT Is it with the same 'Window Door v1.f3d' design attached in the 1st post or is it happening with a different design? Could you please share the data and steps?

PS: I tried with 'Window Door v1.f3d' and the split body worked ok for me. images attached.

Thanks

Sunil

[HarrisonClassic]

Jeff not sure whether this will help, experienced this today.

I had a body that was made from the combine with two other bodies - all joins.

I tried to split this body using the face of another body that totally covers it, even tried without the extending tool, no join, always came up with error suggesting no intersecting data.

Tried a construction plane of the face to try and split the body in the same place, same error.

I was able to split the same body in another place using a construction plane, and it worked - just can't do it in the place I want it!

David