3D adaptive clearing crash

[jimmy.haddersPKDBD]

Hi, so i've used fusion now for a good while as my main CAM program here at work, and all the time it has delivered really good toolpaths. but i think i've found a bug where it instead of lifting above material it crashes right through it, the only way to get around this atm seems to be to add a lift height so that the tool passes above the workpiece before going into the next cut.

This has never been needed before and fusion doesn't tell me that it is a crash either.

[LibertyMachine]

While it does indeed appear to be an issue and definitely in need of reporting, there is another solution to making it NOT do that. By actually selecting a contour for machining, I found that the toolpath came out as expected:

[jimmy.haddersPKDBD]

That seems like a probable workaround for the moment.  But it bugs me that a function that i kind of started to rely on as really reliable bugs out and doesn't warn or anything.

Anyhow, thanks for the workaround 🙂 I'll hang around to see if it'll get fixed and change to accept as solution then 🙂

[LibertyMachine]

Please take a moment to fill out a bug report. With the screencast and forum post already made up, it won't take but a moment of your time and it will assure that this issue is seen by those that matter 

http://forums.autodesk.com/t5/design-validate-document/how-to-report-bugs-amp-issues/td-p/5722215

[jimmy.haddersPKDBD]

I've sent an email to the applied address with a link to this post now. hopefully it'll get resolved quite soon.

[LibertyMachine]

"Quite soon" is a relative term in the software world. If something is downright broken, it (often) gets looked at quickly. If workarounds exist, they tend to get kicked off for a bit while more pressing matters are attended too.

[jimmy.haddersPKDBD]

I've got a cam support ticket and it'll be looked on in the future. I'm not sure if i should accept this as a solution but at least the issue will be handled in the future after more pressing problems/bugs, just as you sais 😉

Anywho, at least there's the workaround you demonstrated for the meantime.