Computed Failed - Failed to Boolean Objects - Fixing timeline errors

[Anonymous]

Title says most of it.. Basically I have this model I am working on for a iPhone Docking System (Free) and I went back in the timeline to change the phone size from a XS Max to a XS , ended up with a bunch of timeline errors when it recomputed changes (in unaffected areas of model).

Been stuck on this for a few days now.. I cannot get it to accept the combine operations, and I can't even seem to extrude from this object or anything as you can see from the screen-cast. 

Would greatly appreciate some input. Thanks in advance

[TrippyLighting]

Please share your model.

[Anonymous]

Here ya go

[TrippyLighting]

Your way of mixing a body oriented workflow with a opponent oriented workflow is pretty chaotic.

You are moving bodes when you should be moving components, for example.

So here is a link to the documentation that explains the difference between a body and a componet a a refresher.

Here's a link to Fusion 360 R.U.L.E #1 that explains how to properly work with components.

[Anonymous]

Point taken I knew the whole workflow was a little chaotic. however considering the documentation says if I convert to a component I loose the timeline ("When you convert the bodies to components later, you lose your

timeline operations."). I don't think that will let me get out of this issue right now.. 

Also doesn't make sense that a couple move and simple extrusions cause that body that I eventually intersect to error out.. It's nothing crazy to me.. Seems like a f360 bug.. 

[TrippyLighting]

The intersect error is a modeling kernel error so a layer der than just Fusion 360. The same error would likely happen in Autodesk Inventor as well.

So unless you pride yourself in the fact that your crude modeling methods have unearthed a potential weakness, the only way forward is to adapt proper modeling methods. The hack & slash design method you are employing sooner or later is going to bring more than one CAD system to it's knees.

Something that might help at this easterly stage of prototype / shape development might be to work without a timeline altogether. That way you only have to deal with one error message.

[Anonymous]

I accept that I need to change my mythology. Will take that under advisement but as of right here and right now. I have a complete model that all I am trying to do is make a simple change for a different size phone, this is/was already completed, and I do not wish to loose all my work by direct modeling or converting to a component right now.

There has to be a way out of this without loosing all my work

[TrippyLighting]

I would save the file under a different name and then in that file delete the timeline. All your geometry and sketches will still be there. What you loose is the associativity between them. But, really, you've not made much use of the parametric design features anyway, so you;'re not really loosing much anyway,

As long as you still have the sketches any geometry that you've created from them can still be re-created.

[Anonymous]

Ultimately I'm not willing to recreate this whole model. that's insane.. this is hours of work.. and even per your rule #1 . I'm building a single component here and the references I'm using externally are all in their own components already, so I fail to see how I would even do this that way.. 
It was much easier for me to design this plug profile in a separate component and test print it before I incorporated it into the over all design. I guess the intersect is a little bit unorthodox but its still a feature of f360 none-the-less.  Even doing the holes from a sketch profile is a pain in the butt cause then I have to go back in and measure for every single extrude that I've already done. 

[TrippyLighting]

OK.

[mavigogun]

---

@Anonymous wrote:

I have a complete model that all I am trying to do is make a simple change for a different size phone, this is/was already completed, and I do not wish to loose all my work by direct modeling or converting to a component right now.

A ball of string tied into knots is a simple thing; transforming that mess into a hammock ain't simple- mater-o-fact, cutting the string may be the best option. Extracting your building blocks to contrive a new tool/machine that can be parametricly adapted might not be easy; depending on what you want or the approach, it may not be possible with the tools on hand. Reaching beyond capacity is good- it's how we push ourselves to grow.  A willingness to push is requisite. But so is an understanding that what is possible ain't the same thing as what is reasonable- and that requires an appreciation of the limitation of our tools and ourselves.  All said from a place of painful personal learning, sympathy.

There has to be a way out of this without loosing all my work

Well, you may not like it. For sure, preserve stable versions of the file for reference; in the Data Panel, you'll find your saved version history access via V on the bottom right hand side of the design thumbnail- so you can mine your own work history for resources. Of course, if there are many versions, and if saved states and design elements are not labelled and organized with clear logic, that task will be a bitch. Extract and isolate what doesn't need to be confronted parametrically, or in a single document.

Maybe this ain't you, but most folks don't seem to appreciate that designing a successful parametric model is an acquired skill dependent on intimacy and fluency with a great number of tools, and experience. It might be realistic to ask work created while still developing to perform as you want- but not while imposing some arbitrary value of what is reasonable effort for the task. I might spend 90% of my time on a new problem discovering what doesn't work- I don't do that just for the transient goal- success informs my future intuition, apprehension of the possible, likely, and what might be a hot ugly mess destined to eat precious time.