After July 2021 update, model is recomputed wrong, some move commands weren't recomputed.

[kg398]

After the latest update, some of my designs have been broken. The first warnings/errors in the timeline come after some move commands were supposed to have happened, but don't appear to have, leading to a cascade of errors. Since these moves were designed a long time ago, were very sensitive and also not currently reported in the timeline with warnings or errors, it is not possible for me to go back and recreate the now missing moves.

Older versions of the file and branches of it that I work on in parallel are similarly broken, since everything gets recomputed after this update. I heard there is no way to roll back to the previous version of fusion 360 which would be temporary solution. Are there any other ways I can restore or recover the designs?

Thanks,

Kieran

[HughesTooling]

---

@kg398 wrote:

Are there any other ways I can restore or recover the designs?

Thanks,

Kieran

---

No. The trouble is the errors were already there and at some point you may have made an edit that would have caused a recompute anyway. Compute All is not needed 99.99% of the time but probably should be run occasionally so something like this doesn't happen. If you have a workflow that causes these errors I'm sure Autodesk would like to know.

One bit of advice if\when you try fixing these warnings. Start with the first error in the timeline and fix it, when fixed run Compute All again before going to the next error. Sometimes fixing one error will fix later errors or cause more. I made the mistake of fixing all errors in a design, ran Compute All again and it broke a lot of the features I thought I'd fixed.

Mark 

[TrippyLighting]

---

@HughesTooling wrote:

---

..

Compute All is not needed 99.99% of the time

...

---

That is only true for experienced user such as the two of us for example.

I've seen several users who's workflows did not follow recommended practices and those designs are pretty much lost and have to be re-done from scratch.

@kg398 did your design(s) include meshes by any chance ?

[kg398]

Is there a way to stop compute all? I haven't had any issues like this before, only since updating is it forcing compute all when opening.
I am almost certainly not following best practices with my workflow, especially towards the beginning.

There are a couple meshes in the design, though not much is derived from them until later and it seems the issue is something earlier in the history.

[TrippyLighting]

---

@kg398 wrote:
Is there a way to stop compute all? 

---

No, this happened automatically as part of the update and upon opening certain designs. The new update made significant changes to the mesh workspace, which required updates to the data structures of designs that included meshes. 

One of the best practices, particularly for beginners is to run a compute all regularly and fix any warnings and error immediately. That would have been sufficient to prevent these disasters.

If you don't want to do that, then turn off the timeline. Without a timeline there is no compute all.

[kg398]

I may have found the source of the error. It looks like an issue with some of the cut/paste operations when moving some bodies into a component, where any translations of the bodies got reset somehow. All I did was suppress and unsuppress the cut/paste and the bodies were copied in the correct 3d location. The frustrating thing is now checking the whole timeline in case this issue is anywhere else, especially as these do not show up as warnings or errors themselves, the errors only come later.

[kg398]

I may have found the solution. Seems like a bug with one of the older cut/paste operations when moving components between bodies, any previous translation on the bodies was lost. Suppressing/unsuppressing the feature seems to have fixed it and the bodies are now copied without losing their translations.
Definitely seems like a bug to me. I'm sure it's bad practice modifying bodies then moving them into components (a practice I have since outgrown, thankfully otherwise I might have had to go through the rest of the timeline fixing these issues), though the issue and solution are not intuitive, especially as the particular offending cut/paste operation gives no warning or error.

[jeff_strater]

@kg398 - can you share this model with us?  We'd like to investigate this source of compute failure.  Thanks.

[awilliamwright]

There have to be hundreds or thousands of users that have had their projects destroyed by this. Autodesk cannot point the finger at all of us for not using "best practices," and say it is our fault that hours of our work are destroyed by an update that is both involuntary and impossible to undo. There needs to be a workaround provided.

There must be a way of opening the files, without the compute-all that destroys them, and then doing a history removal and then re-save. That should be the bare minimum service provided, especially since there was no warning given that so much of our work would be ruined. This is unprecedented, unprofessional complacency, otherwise.

[TrippyLighting]

I don’t see where Autodesk have done that. It would indeed have been nice or even necessary to have a mechanism to undo the automatic “compute all”, but that’s not what transpired.

Based on posts here on the forum, and the Fusion 360 Facebook group I believe that this did not affect too many users.

[awilliamwright]

Then, not just despite of, but because of my finding innovative and powerful ways to use Fusion, I have been humiliated. Meaning, I was a fool to spend the last five years learning how to use the software to do things most people did not believe it could.

I am going to have to find something else to do my work in. This is not the place for me.

[TrippyLighting]

Just to be clear, as an Autodesk Expert Elite I don't work for Autodesk. I am a customer just like you.

I merely pointed out the root case for this, no blame!

I completely agree that there should be a mechanism to delay, or roll back an update for exactly the reasons presented in this thread. I don't know a single Fusion 360 EE who would not agree with that, and we quite often discuss the need for that on the Autodesk Expert Elite Slack channel. It isn't an easy to implement thing and as such it simply has not happened yet.

I would also encourage you to look for alternative solutions. Putting all your eggs in one basket is never a good thing and that is particularly true if your workflows are different from what most people do with Fusion 360. Naturally those areas receive more attention.

You'll find that many things work similarly in other CAD tools and the knowledge you've gained is not lost.