Bug "New version of this design is available" with modified 3d package in electronics library

[bastian.jaeger]

Hi,

yet another anoying bug in Fusion360:
I created a 3d pavkage to some library devices in Fusion 360. Unfortunately the foolish me thought I could open the 3d package from outside the library and modify it.

Now when I open the 3d package from the lib, I get a warning "New version of this design is available" next to the component:

But there is no way to tell this program "yes, there is a new version, you are right, please use this!".

Is here someone who can tell me how this can be done or is Fusion not grown up in its versioning implementation to handle this?

[bastian.jaeger]

Anyone can solve this?

[bastian.jaeger]

Any admin reading this? Is this at least an acknowledged bug? 
Or it there maybe even a way to solve it?

[motorvategarage]

I have the EXACT same issue:  "New version of this design is available" and no idea how to update.
I have spent hours on this trying everything to figure it out.... nothing.
Maybe this will bump it to the top.

[vaclav.pieter]

The same issue

[sbatra.work]

Its June 2021 and I keep facing this issue. Didn't they fix it yet???

EDIT----
Just found the solution as I was typing out my frustration. Just click on File->Save as latest.

[offer_eagleauto]

I'm not convinced "save as latest" does fix it.

I too created a 3d package, then opened it from the fusion360 design browser (i.e. outside eagle) and edited it. The changes aren't reflected in the Eagle library. If I open it from the electronics library it knows there's a later version, but how do I select that later version?

"Save as latest" appears to jump over the later version and just make the latest version the same as the one in the electronics library.

Surely if the versioning inside eagle libraries and fusion360 are different then it should prevent you from changing it, or at least warn. 

I'd really appreciate a response from someone from Autodesk like @edwin.robledo as either I'm doing something wrong or this seems like a bug that shouldn't be too hard for Autodesk to fix.

[jorge_garcia]

Hi @offer_eagleauto,

I hope you're doing well. The save as Latest is really meant to be used if you have a messed up library and you can restore a previous version.

Now be careful when you edit a managed library in Fusion 360, when you save it will be copied to Fusion Team and it will be separate but linked to the managed library. It's important to manage those interactions carefully. See this series of videos here:
https://www.youtube.com/watch?v=xNIEXCimRSg

Let me know if there's anything else I can do for you.

Best Regards,

[offer_eagleauto]

Firstly thanks @jorge_garcia  for your response and the links to the excellent videos, they're really clear on the expected way of using the libraries. While watching I also saw an associated road map video that gave me confidence that Autodesk were working in the background to make things easier between Eagle and Fusion360.

I'm still not sure if it's supposed to be possible to edit packages outside of the eagle library manager. It appears the fusion environment that's opened for editing a package  via "package -> edit" in the eagle library manager, appears differently (e.g. it has the PACKAGE 3D ribbon menu) to if the 3D model is opened directly from the 'Data Panel' (i.e. that does not have the PACKAGE 3D ribbon menu). If edits are made when the design is opened from the Data Panel there doesn't seem to be any way to update the eagle library reference to the updates.

For anyone else reading it, the way I sorted it in our case was to 'Save As' the design opened from the Data Panel as another design, and then opened the package for editing from the eagle library manager, deleted the contents and then used  'Insert into current design' to insert the 'saved as' copy of the design.

Now we can make changes to the 'saved as' file and then go into the library manager and 'update references' to have them sync into the library.

It doesn't seem intuitive having a level of indirection, but at least we got there. I still feels like there should be a warning if you open a file used as a package in a library outside of the library if it's not going to sync.