Remove Body Error Causing Downstream Errors and Numbering of Split Bodies

Remove Body Error Causing Downstream Errors and Numbering of Split Bodies

T-SquareXY
Enthusiast Enthusiast
1,306 Views
13 Replies
Message 1 of 14

Remove Body Error Causing Downstream Errors and Numbering of Split Bodies

T-SquareXY
Enthusiast
Enthusiast

I have read that it is better to Remove a Body instead of Deleting it because Remove will prevent any downstream errors from occurring. Well, apparently this statement is not completely accurate because a Remove Body has caused downstream errors in a design I’m working on. These Bodies were not Removed earlier in the Timeline but were the last thing done. One of the annoying things about this error is the time it took for Fusion 360 to report them. There was no error when I performed the Remove. Also, I run a Compute All at least twice each time I work on the design. I run a Compute All just after opening the design and again before saving it. And I normally work on the design at least 2 separate times every day. But this Remove Body Lost Reference Error did not display at any of the Compute All’s I ran until 3-days after I Removed the Bodies. 

 

So here are the details. I was adding the Safety Railing to finally complete the design of a new deck for my home. I designed an assembly of a 6-foot-long piece of railing, which is the length the manufacturer sells, in a separate external design. Now all of the spans between railing posts in my Deck Design are less than 6-feet with 4 different span lengths. So, I inserted the first external railing assembly design into my new deck design and broke the link so the length could be edited. I aligned the railing between the first 2 posts with equal space between the balusters and posts at each end. Then I used the Split Body Command to trim off the excess railing using the inner faces of the posts as the Splitting Tool. Of course, the Split Body Tool renumbered the resulting bodies the way it wanted to but the body I wanted to keep was no longer Body 1. At any rate, I then Removed the unwanted bodies with no errors or warnings. Lastly, I aligned the center of the railing with the center of the posts & repeated this process for the remaining different length spans and used Rectangular Pattern where I could for those spans that were equal. As I stated earlier, I did not receive any error messages when I ran Compute All before saving and closing the design. But when running Compute All before saving the design 3-days later, I received the Remove Body Lost Reference to Body 1 Missing Error pictured below with several occurrences with additional warnings and errors on Sketches and Rectangular Pattern Features downstream. It even broke previous sketches that were fully constrained and locked. Though these sketches are no longer locked, they are not generating any warnings or errors, so I decided not to worry about those until this problem is resolved.

 

This Remove Body Error is a bit perplexing because you can’t edit the Remove Body Feature. You can only Suppress or Delete it to restore the Removed Body and, both of these actions caused additional errors downstream. In my humble and novice opinion, I believe that the problem lies in the way the Split Body Command renumbers the bodies. But again, there is no way to control the way Split Body re-orders & numbers those bodies. I found a response towards the end of this Solved: Split Body naming and remove body with changed history - Autodesk Community - Fusion 360 forum thread that explains how Split Body numbers the split body. He even provides a way to control the numbering using a Surface Patch as the splitting tool. But that part sort of lost me since I rarely do any surface modeling. And I wasn’t sure this would even work or how many additional errors this would create at this time so, I tried something different instead.

 

I didn’t think that this would fix the errors, but I rolled the History Marker back to the first Error occurrence, deleted the Remove Body 1 feature before the error then deleted the Remove Body 2 Error. I received an immediate warning that these actions caused addition errors downstream but, I soldered on by simply Removing the bodies in the Browser again but in a different order, saving Body 1 as the last to be Removed. Then I advanced the History Marker to the next Sketch Projection Lost Warning and fixed it. I repeated this process for each Remove Error and Warning downstream until all appeared clean. I advanced the History Marker to the End and ran a Compute All. Surprisingly, no errors or warnings were returned. So, I saved the design and went to bed with my fingers crossed. But, about 3 or 4 Compute All’s later, the errors were back. The only difference being the number of the Removed body in error but still showing Body 1 as the Lost Reference.

 

As a bit of additional information, the externally referenced railing assembly with a broken link is in a Rigid Group. I didn’t think this mattered but as a test while attempting to repair these Remove Errors, I Suppressed the Rigid Group before performing my fix then Un-suppressed the Rigid Group when I finished. I did this for some of the occurrences of the Remove error but did not do it for all the occurrences and it didn’t seem to matter, the results were the same for both methods. Lastly, I can try to attach a copy of my design if necessary but, I must give you fair warning, this is a complex design with a huge Browser and Timeline.

 

So, in summary, I have 3 burning questions I would like answered.

  1. What is the proper way to repair these Remove Body Reference Failure Errors?
  2. Is there a way to specify and control how the bodies get ranked and numbered by the Split Body Command? I would like this answered even if it has no bearing on this error.
  3. Why does it take so long for Fusion 360 to recognize and report this error?

Thanks, and Merry Christmas to All

Lenny

 

Remove Body Error.png

0 Likes
Accepted solutions (1)
1,307 Views
13 Replies
Replies (13)
Message 2 of 14

g-andresen
Consultant
Consultant

Hi,

Answering the questions makes no sense without looking at the file.

File > export > save as f3d on local drive  > attach it to the next post.

 

 

günther

0 Likes
Message 3 of 14

davebYYPCU
Consultant
Consultant

Compute All, reads the timeline from left to right, just as you built it.

 

For a lost body 1, means now - body 1 is not available to remove.  

How would you edit that feature?  What were you doing at the time it shows up?

How to fix it - delete the red icon.

 

We would have to “read” your timeline to understand the error/s.  However, when these errors arrive, other than immediately on Open, use Undo to fix them.

 

Are you saying there is, or was not, a further 3 days of work done to the file?

The errors arrive when file is Opened?  That is very rare.

 

Soldiering on is creating a nightmare.  Fix errors from left to right, some will update from that first error fixed.

 

If the file is too big to attach, use a Zip utility to compress it.

File Export, Zip if required, and then attach to a new message.

 

Why does the naming regime matter, when, you label the articles would be after the Remove, No?

 

Fusion works as expected, if you Split Body 1, you have 2 bodies, the Browser keeps Body 1, and the new Body is labelled (next number) (17 if there are 16) at the time.  If you label your work (Rule No. 2), Fusion adds a body in the list with that name and reference number appended.  

 

Again unless you are opening the file - dormant for 3 days - then it is just a Compute All when opened, and the file is being read from left to right.

 

Might help.....

 

0 Likes
Message 4 of 14

etfrench
Mentor
Mentor

I would roll the timeline back to the beginning, then step through each feature one at a time verifying each is correct.

ETFrench

EESignature

0 Likes
Message 5 of 14

T-SquareXY
Enthusiast
Enthusiast

Hi and thanks to everyone who responded. Sorry it took so long for me to respond but I decided to take a break from this design until the Autodesk Pros returned from vacation. I hope you all had a safe and happy holidays.

Lenny

0 Likes
Message 6 of 14

T-SquareXY
Enthusiast
Enthusiast

@davebYYPCU

I think if you carefully read my initial post, instead of speed reading it, you may find the answers to most of your questions, and incorrect conclusions, are already there. I will respond, however, to your comment about Rule #2 because I can see how my attached image could have misled you into thinking that I don’t follow Rule #2. I rename all of my Components, Sketches and even most of my work geometry. But I normally do not rename most of my Bodies as the name of the parent component is usually sufficient.

Lenny

0 Likes
Message 7 of 14

TrippyLighting
Consultant
Consultant

Please share the design in .f3d or .f3z format.


EESignature

0 Likes
Message 8 of 14

davebYYPCU
Consultant
Consultant

I refer you to the picture you supplied, (all other things being normal,)

Put the Timeline marker at the left side of the red icon.

 

Are there any other file errors left of this marker?  If so fix them first.

As the red icon says I can’t do that,

delete the red icon without moving the marker, deleting that icon will clean it off the Timeline and have no other effect in the file.

Move to the yellow sketch icon, review and fix the warning.

 

No you didn’t answer my questions, nor attach the file for Autodesk.

 

Might help.....

 

 

0 Likes
Message 9 of 14

T-SquareXY
Enthusiast
Enthusiast
Accepted solution

Hello Everyone,

I just wanted to let you all know that I have resolved all of these errors in my timeline and inform anyone who is interested of what I found. But first, I would like to know if anyone else is having any trouble understanding my original post. I know it is lengthy and I apologize for that. But I wanted to be as accurate as possible in my description and this topic took more than a couple of short sentences to achieve an acceptable level of accuracy. I also know that a long post like this can cause many people to quickly skim over, or entirely skip over some sections.

 

Anyway, I had fixed all of the first round of errors as described in my original post. The screen pop image attached to that post is of that first round of errors. The image shows the first (leftmost) error in the timeline and its associated sketch warning. There were at least 3 more similar patterns of errors and warnings downstream in the timeline. When these errors returned again later, I assumed they were the same errors (referencing the same bodies) that had returned because I did not use the proper method to fix them the first time. Then I started thinking about the delay Compute All took in reporting these errors the first time and wondered if this second round of errors were actually the same errors which had come back or, if they were a separate new batch of errors (referencing different bodies) which were also simply delayed a bit longer in being reported by Compute All. So, I decided to dig a little deeper.

 

The first thing I did was to copy and paste the errors in the Compute All report for this second round of errors into a Word document so I could better document the steps that follow. Unfortunately, I did not do this for the first batch of errors so I’m still not sure whether this 2nd batch of errors are the same errors which came back or if they are an entirely new batch of the same error type just reported with a longer delay. But the first thing I noticed from the pasted Compute All report was that the order of the errors listed in Compute All report was different from their order in the Timeline. The first error listed in the Compute All report was actually the second error in the Timeline.

 

The next thing I noticed was the 3 errors reported in this second round did not have any sketch warnings associated with them in the Timeline as the first round did. Only 3 errors appeared in the Timeline. So, I assume, and maybe incorrectly, that the method I used to correct the first batch of errors (as described in my original post) was correct to some degree and had a positive effect on this second round of errors. Now I proceeded to correct this second round of errors using 2 different approaches.

 

In my first approach I deleted the 1st (leftmost) error from the Timeline without rolling the History Marker back to this 1st error. In other words, I left the History Marker at the rightmost end of the Timeline when I deleted the 1st (leftmost) error. I noticed that when you delete an error in the Timeline with the History Maker at the end, Fusion 360 automatically rolls the History Marker back to the error being deleted for a brief second or two during deletion then the History Marker is automatically returned to the end of the timeline when the deletion is complete and begins a Quick Compute. After this error deletion and Quick Compute completed, I received a Warning message saying, “Deletion cause downstream feature failures”. The Warning pointed to the already present 3rd downstream error in the Timeline. No additional errors or warnings were presented so, I decided to Undo this Delete action and try my 2nd approach.

 

My 2nd approach uses the recommended method of rolling the History Marker back to the error or warning being repaired before effecting those repairs. So, I Undid the previous Delete action, rolled the History Marker back to the 1st error and deleted it from the Timeline. This time when the deletion and Quick Compute completed, I not only received the same Warning message displayed in my 1st approach, but I also received no less than 35 additional Warning messages referencing Holes which had been created well before the error that had just been deleted. These yellow Hole Warnings remained in the Timeline after I rolled the History Marker back to end of the Timeline. I then ran a Compute All with the History Marker rolled all the way back to the right end of the timeline. This Compute All showed only the 2 original remaining errors and the Hole Warnings disappeared from the timeline. Now I know that these 35 additional warnings were of no real consequence in this case, but it can be very alarming to a novice trying to wrestle with Timeline errors. So, with this particular error, at least, it appeared to me that it is better to delete the error from the timeline without rolling the History Marker back to the error, leave the History Marker at the end of the timeline.

 

Continuing with the 1st approach, I deleted the 2nd error in the timeline with the History Marker at the end. I received the same “Warning: Deletion cause downstream feature failures” message that I received when I deleted the 1st error. I received no error or warning messages when I deleted the 3rd and final error. I also noticed that after deleting 1 of these errors, my guess it was the 1st error in the timeline, the body referenced for the 3rd error became segmented in the design window with a small segment extending beyond its trimmed boundary. Carefully selecting and removing the correct split body in the Browser corrected this problem. I then ran a Compute All and received no error or warning messages. I then performed the final modification to my design which finally completes this design. I ran a final Compute All before saving this design 1 last time with a clean Timeline.

 

I’m still not sure if this was the proper (or Fusion 360 recommended) way of fixing this error. And I will never know if these errors could reappear in the future because I will not be making any further changes to this design.

 

I intend on leaving this thread open until I receive a response from an Autodesk Professional addressing all 3 of my original questions. I suspect that the Autodesk Team is probably overwhelmed trying to catch back up after their holiday vacation so, there is no hurry for a Pro to respond. Please respond at your convenience. And no offense is intended to anyone else here but, I believe that only an Autodesk Pro, with his insider’s knowledge, can accurately answer these questions.

Thanks Again

Lenny

0 Likes
Message 10 of 14

davebYYPCU
Consultant
Consultant

I believe that only an Autodesk Pro, with his insider’s knowledge, can accurately answer these questions.

 

Thanks for your confidence in the actual responders.  You won’t get rid of me that easily.

I am not a speed reader.

 

You have no understanding of the actual difference a red or yellow icon means.  

In my reading of your explanation, you decided to delete bad icons, disregard my accurate statement.

 

As if Fusion could talk - 

Red icons - I cant do this.  (I said - Delete for only that red icon)

Yellow icons - it used to work but you changed something, I am able to remember how it was, but you need to change it back.  Deleting this may / will cause downstream errors.

( I said - Review and fix the yellow icons)

 

Sorry for my willingness to help.  

 

 

 

 

Message 11 of 14

TrippyLighting
Consultant
Consultant

You still haven't supplied a model.

Often in a properly developed model, bugs are the nature of unexpected behavior. However, it is impossible to assess whether this is a workflow issue or a bug without having access to the model.

 

My guess is that this is a workflow issue as I've not come across this behavior in my own work.

I've examined thousands of Fusion 360 designs of other users on this forum.

 

But, again, without a model that is difficult to assess.


EESignature

Message 12 of 14

laughingcreek
Mentor
Mentor

An approach to avoiding the original described behaviour-instead of SPLITTING a body and REMOVING the unwanted bodies,  whenever possible EXTRUDE CUT the bodies to be removed instead.

 

Message 13 of 14

T-SquareXY
Enthusiast
Enthusiast

I have read many of your posts and know you are very knowledgeable. I have no doubts about your capabilities, and I understand what you are saying. You have basically said that you can't tell why it took Fusion 360 so long to report these errors without seeing the design. The problem is most likely something that I did. I can appreciate that & you may be correct. The fact is, I don't even know if I now have a version of this design that was saved with these errors. I typically don't save design versions with errors. I would have to go back into my version history to try & find one. Plus, this design is 120MB in size. And to be honest, I have now completed this design with no errors & would just like to finally put this one to bed. I really do appreciate your willingness to help & honestly did not intend to offend or show any disrespect towards you or anyone else. 

Message 14 of 14

T-SquareXY
Enthusiast
Enthusiast

That is good advice. I will keep this in mind for future designs. 

Thank You

Lenny

0 Likes