Toolpath Invalidated when reopening a project

[tmostad]

After I save a valid design when in the manufacturing tab then close F360 and launch it then open the the project, two ops show the error in the pictures; the same two and only those two, happens every time. I just checked and it also happens when I close and reopen the project without shutting down F360.

[Anonymous]

Does it happen if you lock operation before saving file?, usually if I have similar case, regenerating operation solves it.

[jeff.pek]

Are you able to share the model so we can take a look?

Thanks,

  Jeff

[tmostad]

Here it is.

[Anonymous]

If I protect all operations, save file and reopen it, nothing is lost, all setups simulate as they should.

If I then unprotect all operations, they all turn red, hit "Ctrl + G" and it all generates without any errors, I don't see anything unfamiliar here.

[SendItCNC]

   > ...I don't see anything unfamiliar here.

I think what is unfamiliar is that without protecting (or unprotecting) tool paths, some become invalidated after a save/reopen, or even just tabbing to a different design and back. IIRC that is a recent behavior change.

[Anonymous]

Well, maybe "unfamiliar to ME" is a better choice, I got used to protecting files before saving them because I want all settings to be undisturbed when I reopen file at later time.

These frequent updates and hotfixes tend to fix one thing and mess up another so if I protect files I have fewer instances of things going nutz and recovering.

There was once a posts claiming file is not really protected but it seems to be isolated case.

I still practise locking my car even though it doesn't really stop someone from breaking in.

[tmostad]

I have never seen it in any documentation that toolpaths may be invalidated upon leaving and re-entering a project so I believe this is an unintended behavior (a.k.a. bug). I'll wait to see what Autodesk says.

[Anonymous]

---

@tmostad wrote:

I have never seen it in any documentation that toolpaths may be invalidated upon leaving and re-entering a project so I believe this is an unintended behavior (a.k.a. bug). I'll wait to see what Autodesk says.

---

Bugs, known and unknown, are unlikely to be advertised or even acknowledged in documentation, Fusion is a moving target and you get new challenge with every update, not always for better.

All I am saying is, protecting file offers some security against unwanted behavior.

[tmostad]

Not to be argumentative but bugs are often documented in Release Notes. In fact I have seen them exposed by Autodesk in their release notes at times. Bugs aren't something anyone would tout but any reputable company would not purposely hide something as inconsequential as this bug. As you said, protecting the setups prevents the problem from occurring and is a reasonable workaround. I suspect it is an honest error and Autodesk will fix it.

[jeff.pek]

Thank you for sharing the model. I think I'm seeing the same thing you are with these 2 particular operations. Looks like one or 2 particular edges are being considered as having changed since prior regeneration. We'll create a ticket and look into it. Thanks for the report and Happy New Year!

Jeff

[Anonymous]

Yes, bugs are talked about and being fixed but no one wants to emphasize bad side of product.

"Make anything" is more appealing then "We have so many bugs, we wonder why so many people like Fusion"

Fine line is criteria by which certain behavior is labeled as bug and sometimes it's a matter of perception, not protecting file is an open invitation for problems in scenario where software is being updated as often as Fusion is.

Why not do what you can to prevent problems ?, it's easier than calling it a bug and waiting for fix to come by.

[tmostad]

Sure, a "belt and suspenders" approach is never a bad thing but if Fusion thinks edges have changed when they haven't then that is a bug. The end.

[Anonymous]

"Beauty (bug) may be in the eye of beholder" and I am not disputing how you perceive it. I was only pointing out that if I protect file before saving it, I don't generate any odd behavior, call it "workaround" or bug, it seems to help keep beans from spilling while AD is working on better lid..